CSS Sprint E-4: DevX polish - stylelint guard, 282 dead stubs gone, paved-path enforcement, discoverability#384
Conversation
…ed-path guard test, discoverability - stylelint (minimal ruleset) wired as 'bun run lint:css' over the hand-maintained layer (pages/ + components/); legacy five + vendors ignored. 264 empty-block rules + 4 empty media shells deleted and 14 duplicate declarations auto-fixed - ALL byte-gated (every bundle fingerprint identical). no-duplicate-selectors demoted to warning: merging same-selector rules moves declarations across cascade positions (the C5/D1 trap) - humans decide those, not --fix. - test/unit/paved_path_guard_test.rb: every pages/*.css must have a bin/qtest mapping and an ownership-map entry - the new-page checklist is enforced, not just documented (unit suite 267 runs green). - CLAUDE.md workflow pointer + lint step in new-page.md: the paved path is discoverable from the entry-point docs. - .stylelintrc.json force-added (a broad gitignore pattern caught it). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GYRU9wGepomJo5hSuqtu7V
|
Warning Review limit reached
Next review available in: 10 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (18)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
What this is
The answer to "can you improve more?" — a fresh-eyes audit found three real gaps, all closed here.
Shipped
bun run lint:css, minimal ruleset over the hand-maintained layer; legacy five + vendors ignored). The duplicate-declaration bug class CodeRabbit caught by hand now has an automated guard.no-duplicate-selectorsdeliberately demoted to warning: merging same-selector rules moves declarations across cascade positions — the exact C5/D1 trap — so humans decide those, never--fix.test/unit/paved_path_guard_test.rbfails when apages/*.csslands without itsbin/qtestmapping or ownership-map entry (unit suite 267 runs green).new-page.md— a newcomer can now find the paved path from the entry-point docs.Deliberately not done
Verification
Full macOS system suite 65/119 zero failures, zero baseline changes; Linux
dtest-allEXIT=0; unit suite 267 green.🤖 Generated with Claude Code
https://claude.ai/code/session_01GYRU9wGepomJo5hSuqtu7V