CLAIM-BOUNDARY-VISIBLE-SURFACE-MATRIX-01: add visible boundary matrix

[fermatmind]

What changed

• Added read-only visible claim-boundary matrix across the 12 six-test hub routes.
• Recorded page-level boundary evidence, route-level concerns, and repair planning prompts.
• Added a scan manifest with method, route list, summary, and non-mutation scope guard.

Why

• After first-screen and FAQ parity readbacks, the train needs claim-boundary evidence before any repair planning or content changes.

Validation

• python3 -m json.tool backend/docs/seo/daily-runs/2026-07-06/claim-boundary-visible-surface-matrix-01/scan_manifest.json >/dev/null
• git diff --check
• git diff --cached --check

Deferred items

• No public copy, FAQ, JSON-LD, CMS, frontend, sitemap, llms, metadata, canonical, noindex, production import, or deployment changes.
• Any answer-block/FAQ/claim repair split requires separate exact authorization.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.