Repository navigation
docs: state mode behaviour on every rule page (Phase D-13) - #543
Conversation
Every rule page (en + ja) now carries a `## Mode differences` section — source analysis (the CLI, the dashboard's static baseline) vs rendered analysis (the Vite plugin's build pass, a visited dashboard route) — written once per rule family from the provider truth table in docs/superpowers/specs/2026-08-19-rule-page-mode-pass.md. Inline mode claims move into the section; "Static (CLI) analysis" on pages the plugin build also runs is corrected; a11y/doctype names the surfaces that do report it; the --route section of the CLI guide says which rule families it skips. packages/cli/test/docs-links.test.ts fails the build on a page without the section. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…cp-image, json-ld, inventory rules) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Important Review skippedToo many files! This PR contains 195 files, which is 95 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (195)
You can disable this status message by setting the 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 |
Summary
Phase D-13 of the v1 roadmap — every rule page says how it behaves per analysis input.
## Mode differences/## モードによる違いsection: source analysis (the CLI, the dashboard's static baseline) vs rendered analysis (the Vite plugin's build pass, a visited dashboard route). One fixed paragraph per rule family, derived from the provider truth table indocs/superpowers/specs/2026-08-19-rule-page-mode-pass.md; tailored paragraphs where a rule diverges (charset/viewport, the length and uniqueness pairs, html-lang, sitemap-in-robots, lcp-image, json-ld, the source-inventory Architecture rules); the seven pages that already had the section are relabelled to the same vocabulary.heavy-import,namespace-import, five Correctness pages),a11y/doctype's "CLI only" (the dashboard baseline reports it),json-ld-validity's unqualified "not checked".guides/(setup)/cli.md### --route(en + ja) states which rule families the flag skips, that the uniqueness pair compares only the matched routes, and that project rules still run.packages/core/src/rule.ts/head.ts.packages/cli/test/docs-links.test.tsfails the build on a rule page without the section (##heading, en + ja).Merge after #542 — the dashboard-live-layer statements ("leaves this rule to the static baseline") describe the behaviour that PR introduces.
Verify
pnpm build && pnpm typecheck && pnpm lint && pnpm -r test && pnpm --filter docs run translate:check— all green; 115 en pages stamped.🤖 Generated with Claude Code