[B2] Restore docs sidebar + footer chrome lost in the compiled-shell refactor (user-reported, hostile-audit/verifier miss)

[SisyphusZheng]

User-reported and independently reproduced (explore investigation, stage #1288): the official website's docs sidebar and footer are broken/missing on the live site.

Evidence

• Docs sidebar gone entirely: zero sidebar matches in www/app or built HTML; guide/docs/architecture pages have no section navigation. Meanwhile www/app/data/_generated-nav.ts still generates a full navSections tree that NOTHING consumes — dead generated truth.
• Footer is a bare unstyled strip: www/app/islands/open-layout.tsx:242-245 has only border-top+background; render emits two spans + one link; orphaned @media (max-width:900px){.app-footer{padding:0}} at :269 references removed padding.
• Root cause: 7bbef34b (compiled-shell refactor, ADR-0143, Aug 30) deleted 656 lines incl. .docs-sidebar/.nav-section and the rich 4-column footer; 7cb922a4 deleted the old shell tests instead of restoring the chrome. test(www,e2e): harden E2E selectors and cover the full public IA (#1232, B2.10) #1306's e2e hardening codified the regression (accessibility-performance.spec asserts zero footer headings).
• Why the stage missed it (process lesson): public-route e2e asserts only main-landmark+h1 per route; visual baselines screenshot with fullPage:false (page-bottom footer never captured); hostile audit checked truth-derivation, not chrome completeness.

Acceptance

• Docs/guide/architecture pages ship a real section sidebar consuming the generated navSections (or the generation is removed — no dead truth), usable on desktop and mobile.
• Footer restored to a proper site footer (nav columns or equivalent, styled, bilingual), consistent across routes.
• Coverage gap closed: e2e asserts sidebar + footer visibility/structure per layout class (semantic assertions, not pixel-only); visual baseline capture includes page bottom (fullPage or dedicated chrome snapshots). CI-gated.
• Bilingual parity; all existing gates stay green (content-graph, www:check-truth, www:check-links incl. any new nav links).

Stage #1288. Part of #1155. This re-opens the Beta.2 website acceptance bar ('public information architecture is coherent') — the publish lane holds until this lands and re-verification passes.

[SisyphusZheng]

Fix opened as PR #1318 (branch fix/1317-restore-docs-sidebar-footer, commit 2f0780b). The interrupted repair session's working tree was audited, completed, and verified: SSG build + artifact-truth + link check pass; Deno unit 20/20; Playwright chromium site-chrome/accessibility 20/20, reactivity/routing/theme/behaviors 36/36, visual baselines 16/16 (regenerated + new chrome element snapshots reproduced locally). Publish lane may resume once #1318 merges and dev goes green.

[SisyphusZheng]

PR #1318 updated (ba991cd): the CI failure exposed a real framework bug beyond the chrome restore itself. applyPendingOwnValues coerced a pre-upgrade locale: null write into the compiled default and applied it after attribute promotion, so computed chrome re-derivation at claim time saw locale='en' while the SSR DOM was rendered from the injected locale='zh' props — the [compiled-claim] item attribute drift on "href" seen on every /zh page. Fixed in facade-host.ts (restated-default initializers no longer become pending pre-upgrade sets; null pending values are skipped). Verified: element 254, app 99, www unit 69, chromium e2e 219 (incl. the public-routes zh sweep that failed in CI), build/artifact-truth/links green.

[SisyphusZheng]

Fixed by #1318, merged to dev as 005a971. Docs sidebar and four-column footer chrome restored with coverage hardening (site-chrome spec, chrome element baselines, hardened accessibility assertions); the underlying claim-time property-contract defect was fixed in facade-host as part of the same PR.