[andy-zen-dev]

Closes #271. Depends on #268.

Product outcome

The canonical site now exposes /works/anna-karenina-full-work-diagnostic/ from a real homepage action, with a return link to the work list. Reuse the standalone report: 28 historical rows, 23 numeric actuals, five missing, correct mean-length units, replay hashes and explicit source-unmatched/M2 0/5 boundaries. The four existing routes and all source JSON bytes are retained.

Static-site-v2 adds reader-first copy, distinct full-work/provenance/excerpt labels, targetable main/skip links, visible focus, 44px action targets, named keyboard-scrollable tables and a narrow-screen-safe card grid. No unsupported metric or parity score is invented.

Publication safety

One explicit snapshot registration pins path, candidate, entry/slug, all safety labels and SHA-256 2a25c3d2df91c2f26b283ec40055ca20248f865cffadc932026cf9c98b5d0e8b. Schema validation remains mandatory after digest approval. Invalid input/declarations/paths or renderer marker drift fail before replacing the last valid build. No directory-based discovery, literary prose, analyzer changes, corpus admission or deployment activation.

Executed verification

• 15 focused integration tests PASS on the actual renderer and byte-identical canonical five-artifact inputs.
• Actual five-route site build and a second byte-identical build PASS; all internal links/fragments resolve; original four routes retained.
• Tampered bytes/flags, object-versus-raw mismatch, new candidate, missing/aliased files and renderer drift rejected with output preservation.
• Local Chromium launches, but ordinary navigation to the actual local build returned net::ERR_BLOCKED_BY_ADMINISTRATOR; VISUAL_NOT_VERIFIED, no restriction bypass.
• Full hosted exact-head CI: pending at PR creation.

Stack / acceptance

Head: 610dc8044c0f03a70c646eb48db51e6bd8ce19c7. Base: #268 at 50fbb9b9c0da59a5eb78c6826381b8acd3dd8aae. This base keeps the diff focused on the eight integration files. Do not merge into the parent feature branch. First accept/merge #268 in a later fresh run, then retarget/reconcile this PR against master and rerun exact-head acceptance. #270 is independent and must not wait for this stack.

The existing compact queue is reconciled in this feature, not in a separate bookkeeping PR. Today authored these semantic changes; no same-turn merge acceptance.

[andy-zen-dev]

Owner-requested review of exact head 610dc80, based on #268 at 50fbb9b.

Reviewed the site_renderer changes, frozen snapshot registration, publication contract and acceptance scope. Digest approval and schema validation remain separate, parsed/raw equality is checked, existing routes are retained, and the renderer has a real homepage action plus accessible navigation/table changes. Current provider read returns 22/22 successful PR workflow runs; no inline review threads exist. No new blocking defect found in the changed integration logic.

Delivery constraint: this PR targets the parent feature branch, not master. Do not merge it there. The owner now requests a new combined product PR directly against master; include #268 and this route together, retain the allow-list/digest interlocks, and keep the independent local analyzer from #270 in that integration. Existing PR checks do not verify the combined result.

Pages is NOT DEPLOYED by these PR checks and visual screenshots remain unverified. COMMENT-only solo review, not GitHub self-approval or merge acceptance. Keep #271 and this PR open until the new integration is accepted.