chore(docs): docs-kit 1.0.4 + rouge 5 + dependency refresh

[mhenrixon]

Summary

Picks up docs-kit 1.0.4 (rouge constraint widened to < 6, --sync MCP-route fix) and refreshes all docs-app dependencies. Follow-up to #33.

Headline: rouge is back on 5.0.0 — the 1.0.3 rollout had downgraded it to 4.7.0 via docs-kit's old < 5 cap.

Gem moves

docs-kit 1.0.3 → 1.0.4, rouge 4.7.0 → 5.0.0, puma 7.1 → 8.0.2, brakeman 7 → 8, parallel 1.27 → 2.1, phlex-reactive 0.4.7 → 0.9.1, rubocop 1.81 → 1.88, kamal 2.12, rspec-rails 8.0.4, playwright-ruby-client 1.61, faker 3.8, oj 3.17.

Node moves (bun update --latest)

tailwindcss + @tailwindcss/cli 4.1.18 → 4.3.2, daisyui 5.6.1 → 5.6.13, playwright 1.61.1 (chromium refreshed), turbo-rails 8.0.23, prettier 3.9.4, biome 2.5.2, stylelint 16 → 17 (+ config-standard 40 — bun run lint:css verified green).

Lint accompaniments (rubocop 1.88 + NewCops)

• Layout/BlockAlignment autocorrects in two component example files
• Inline RSpec/Output disable around the deliberate on-failure debug dump (autocorrect would have deleted it)
• Style/OneClassPerFile exclude for the docs-kit-generated config/initializers/phlex.rb (its two namespace modules are by design — splitting would drift from the generator template)

Dogfood check — 1.0.4's --sync fix

bin/rails g docs_kit:install --sync --skip now makes zero effective changes: both /mcp routes report identical (already drawn or scaffolded) (no re-injection), and the site-styled docs_kit_og.rake is kept, not clobbered.

Verification

• Docs suite: 8 examples, 0 failures (run twice — after deps, after lint fixes)
• RuboCop: 344 files, no offenses; bun run lint:css green under stylelint 17
• bun run build:css clean (tailwind 4.3.2 / daisyUI 5.6.13)

https://claude.ai/code/session_01FPQb6z3YwcKRMbvoJhdxnX

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 18407bdd-d381-4900-8d74-d5512c5cf246

📥 Commits

Reviewing files that changed from the base of the PR and between 46c3d1e and 430a482.

⛔ Files ignored due to path filters (2)

• docs/Gemfile.lock is excluded by !**/*.lock
• docs/bun.lock is excluded by !**/*.lock

📒 Files selected for processing (5)

• docs/.rubocop.yml
• docs/app/views/components/examples/stat/with_figure.rb
• docs/app/views/components/examples/timeline/colorful.rb
• docs/package.json
• docs/spec/system/support/capybara_setup.rb

---

_{Comment @coderabbitai help to get the list of available commands.}