Prune the now-dead per-page topbar/footer CSS left behind after the shared-chrome consolidation (keep .landing-external)

task-prune-dead-per-page-chrome-css

task confidence verified status done 2026-06-17 owner starlight-engineer

source log-auditor — surfaced recording DEC-0038; the FDE listed the orphaned per-page chrome selectors as a safe cleanup pass deliberately not done in the consolidation turn. CLOSED 2026-06-17 (FDE) — MOOT/RESOLVED-BY-STRIP — the DEC-0043 docs-strip deleted the landing/board/graph surfaces from @dossier/site AND their stylesheets wholesale, so the dead selectors no longer exist to prune. grep of packages/site for all 12 named selectors found 0 occurrences in active code (lone hit is POLISH-BRIEF.md, a doc); landing.css/board.css/graph.css are gone (only okf.css + bridge.css remain).

Prune the dead per-page chrome CSS after the shared-chrome consolidation

Site chrome unified into shared SiteHeader + SiteFooter + ThemeToggle components, and the docs/KB surface made fully open — DEC-0022's DOCS_ENABLED landing-only gate is removed so /knowledge ships publicly alongside the landing/board/graph moved every surface onto the shared SiteHeader / SiteFooter components (which use .site-header / .site-footer), and removed the per-page topbar/footer markup — but left the per-page chrome CSS behind. Those rules are now dead.

What is safe to delete

landing.css — .landing-topbar*, .landing-footer*, .landing-wordmark
board.css — .board-topbar*, .board-wordmark, .board-readonly, .board-footer
graph.css — .graph-topbar*, .graph-wordmark, .graph-readonly, .graph-footer

What to KEEP (the trap)

.landing-external is still used by the landing hero — do not delete it in the sweep. Grep-confirm it is referenced before touching anything nearby.

Why a task, not a fix-in-place

The FDE deliberately deferred this to a cleanup pass (the consolidation turn was about behavior, not cosmetics), and it wants a per-selector grep-confirm + a before/after render check rather than a blind delete — better owned by the Astro Starlight Engineer (the site/surface owner) than swept by the auditor. Provenance: surfaced by the log-auditor recording DEC-0038; confidence: inferred (agent-derived from the FDE's own follow-up list, not human-curated). Board globbed before filing — no open task covered this cleanup.

Closed 2026-06-17 — moot, resolved by the DEC-0043 strip

This cleanup was overtaken by events. Migrate chrome-light app surfaces to SvelteKit; docs stay on Astro/Starlight (two apps, one origin) moved the landing/board/graph surfaces to @dossier/app and stripped @dossier/site to docs-only, deleting those pages and their stylesheets (landing.css / board.css / graph.css) wholesale — so the dead per-page chrome selectors this task targeted no longer exist anywhere to prune. Verified: a grep of packages/site for all twelve named selectors returns 0 occurrences in active code (the single textual hit is in POLISH-BRIEF.md, a doc), and the styles directory now holds only okf.css + bridge.css. The .landing-external "keep" trap is also moot — its hero consumer moved to @dossier/app, and nothing references it in packages/site anymore. Net visual change: none (the surfaces were relocated, not re-styled). Closed by the Principal Forward Deployed Engineer as board hygiene while diagnosing why the board wasn't closing out backlog items.