@bettercms-ai/mcp 0.83.0 → 0.83.2

package/dist/skills/bettercms/references/site-review.md

@@ -1,74 +1,74 @@
----
-title: "Site review"
-description: "A read-only launch review: what to check per route and how to report findings without fixing them."
----
-
-# Read-only site review
-
-**Outcome.** An evidence-backed issue list, scoped to the actual project and revision, that a
-developer can reproduce and prioritise. Change no data or code during a review unless the user
-separately asks for repairs.
-
-## Establish a baseline
-
-Identify the project, source commit, import or release revision, hosting mode (`get_project`),
-public or staging URL, and expected route inventory. Then read the control plane and record when
-each report was generated:
-
-| Read | Tells you |
-|---|---|
-| `get_site_composition` | Which pages are made of sections, and which components they use; `help`: how much of the schema carries help text, and what does not. A field with no line at all, or one that only repeats its label, is a finding; a field carrying the platform's own line is not |
-| `get_binding_report` | Per route: `mode` (`declared` or `text-match`), `coverage.pending`, and `refreshReason` when there is no current report |
-| `list_seo_issues` | Native SEO problems per page |
-| `get_component_readiness` | Per component: validation and Output state |
-| `list_forms` | Which forms exist and whether each is published |
-| `get_deploy_status` | The last build and release |
-| `get_next_steps` | What the platform itself still counts as unfinished |
-
-A binding report is created only by a BetterCMS release (a content apply later updates its Layout
-rows), so a headless site may never have one; `never-generated` is missing evidence, not a clean
-result. A green control plane cannot prove a route answers:
-fetch rendered pages too, cache-busted.
-
-Sample every **route class** (static, list, collection detail, 404 or protected, locale) and
-every **component family**. Include two instances of a reused component, one variant, one nested
-slot, the global nav and footer, long and empty content, and a custom Portable Text block when
-present. Widen the sample when a failure looks systematic.
-
-## Review dimensions
-
-| Dimension | Evidence to collect |
-|---|---|
-| Structure | Page / collection / entry classification, which of the four folder systems is used for what, route and redirect integrity |
-| Reuse | Definition, default, variant and instance ownership; override isolation; global chrome; slot limits |
-| Editability | Schema, stored value, reader, prop, bound leaf or attribute, preview, published output; intended fields against verified bindings |
-| Editor UX | Field types, allowed Portable Text controls, labels, grouping, defaults, required states, repeatable-item previews |
-| Design and media | Brand tokens, font loading, logo roles, asset delivery from the project's media origin, alt / caption / crop, desktop and mobile fidelity |
-| Behaviour | Forms and their destinations, keyboard and focus, navigation, accordion / modal / consent logic, custom code |
-| Accessibility | Alt text, heading outline, form labels and consent, link text, contrast, captions: the manual checks in [accessibility.md](accessibility.md); no tool reports these |
-| Discoverability | Native SEO, canonical and noindex, structured data matching visible content, sitemap and robots, internal links |
-| Delivery | Build, cache and revalidation, live status and content, draft isolation, secrets and the server/client boundary |
-
-Use automated checks where they answer a concrete question, and manual visual or editor checks
-where automation cannot show intent. Never edit production as a test. If an edit-to-render test
-needs a write, mark it unverified in a read-only review, or get the user's authorisation for a
-safe draft test.
-
-Useful anchors while reviewing: a draft form refuses public submissions (403), so a form that
-renders but is not published cannot take a lead; a headless project is never built by BetterCMS,
-so its proof is the external host's public response; a Content sidebar folder never changes a
-URL, while renaming a URL page folder 301s its pages.
-
-## Issue format and decision
-
-For each issue record severity (blocker, high, medium, low), the route / component / field,
-expected against observed, exact reproduction, evidence (link, screenshot, report time), likely
-owner, and a specific acceptance check. Separate a verified defect from an inference or missing
-evidence. Summarise coverage as verified intended editable fields divided by discovered intended
-editable fields, with exclusions listed separately.
-
-Recommend **ready**, **ready with named exceptions**, or **not ready**. A blocker includes a
-broken public route, lost content or reference, an unbound core editorial value, a form sending
-to the wrong destination, an exposed secret, or a live state that contradicts what the user
-intended. For each, give the smallest repair path and whether it belongs to code, CMS data, a
-platform capability, or a user decision.
+---
+title: "Site review"
+description: "A read-only launch review: what to check per route and how to report findings without fixing them."
+---
+
+# Read-only site review
+
+**Outcome.** An evidence-backed issue list, scoped to the actual project and revision, that a
+developer can reproduce and prioritise. Change no data or code during a review unless the user
+separately asks for repairs.
+
+## Establish a baseline
+
+Identify the project, source commit, import or release revision, hosting mode (`get_project`),
+public or staging URL, and expected route inventory. Then read the control plane and record when
+each report was generated:
+
+| Read | Tells you |
+|---|---|
+| `get_site_composition` | Which pages are made of sections, and which components they use; `help`: how much of the schema carries help text, and what does not. A field with no line at all, or one that only repeats its label, is a finding; a field carrying the platform's own line is not |
+| `get_binding_report` | Per route: `mode` (`declared` or `text-match`), `coverage.pending`, and `refreshReason` when there is no current report |
+| `list_seo_issues` | Native SEO problems per page |
+| `get_component_readiness` | Per component: validation and Output state |
+| `list_forms` | Which forms exist and whether each is published |
+| `get_deploy_status` | The last build and release |
+| `get_next_steps` | What the platform itself still counts as unfinished |
+
+A binding report is created only by a BetterCMS release (a content apply later updates its Layout
+rows), so a headless site may never have one; `never-generated` is missing evidence, not a clean
+result. A green control plane cannot prove a route answers:
+fetch rendered pages too, cache-busted.
+
+Sample every **route class** (static, list, collection detail, 404 or protected, locale) and
+every **component family**. Include two instances of a reused component, one variant, one nested
+slot, the global nav and footer, long and empty content, and a custom Portable Text block when
+present. Widen the sample when a failure looks systematic.
+
+## Review dimensions
+
+| Dimension | Evidence to collect |
+|---|---|
+| Structure | Page / collection / entry classification, which of the four folder systems is used for what, route and redirect integrity |
+| Reuse | Definition, default, variant and instance ownership; override isolation; global chrome; slot limits |
+| Editability | Schema, stored value, reader, prop, bound leaf or attribute, preview, published output; intended fields against verified bindings |
+| Editor UX | Field types, allowed Portable Text controls, labels, grouping, defaults, required states, repeatable-item previews |
+| Design and media | Brand tokens, font loading, logo roles, asset delivery from the project's media origin, alt / caption / crop, desktop and mobile fidelity |
+| Behaviour | Forms and their destinations, keyboard and focus, navigation, accordion / modal / consent logic, custom code |
+| Accessibility | Alt text, heading outline, form labels and consent, link text, contrast, captions: the manual checks in [accessibility.md](accessibility.md); no tool reports these |
+| Discoverability | Native SEO, canonical and noindex, structured data matching visible content, sitemap and robots, internal links |
+| Delivery | Build, cache and revalidation, live status and content, draft isolation, secrets and the server/client boundary |
+
+Use automated checks where they answer a concrete question, and manual visual or editor checks
+where automation cannot show intent. Never edit production as a test. If an edit-to-render test
+needs a write, mark it unverified in a read-only review, or get the user's authorisation for a
+safe draft test.
+
+Useful anchors while reviewing: a draft form refuses public submissions (403), so a form that
+renders but is not published cannot take a lead; a headless project is never built by BetterCMS,
+so its proof is the external host's public response; a Content sidebar folder never changes a
+URL, while renaming a URL page folder 301s its pages.
+
+## Issue format and decision
+
+For each issue record severity (blocker, high, medium, low), the route / component / field,
+expected against observed, exact reproduction, evidence (link, screenshot, report time), likely
+owner, and a specific acceptance check. Separate a verified defect from an inference or missing
+evidence. Summarise coverage as verified intended editable fields divided by discovered intended
+editable fields, with exclusions listed separately.
+
+Recommend **ready**, **ready with named exceptions**, or **not ready**. A blocker includes a
+broken public route, lost content or reference, an unbound core editorial value, a form sending
+to the wrong destination, an exposed secret, or a live state that contradicts what the user
+intended. For each, give the smallest repair path and whether it belongs to code, CMS data, a
+platform capability, or a user decision.