spec-site

scripts/render_specs.py walks openspec/specs/**/spec.md and reads nothing else, on the Python standard library alone. scripts/build_site.py is the one command; the workflow runs it and nothing else. docs/evidence/spec-site-build.txt records both. The existing accepted ledger test excludes in-flight change identifiers from index and capability pages. docs/evidence/spec-site-work-board/README.md records the focused work-board tests and the published page at revision 95595a8e.

the landing page's <h1> is the count itself, emitted before any capability is named. Tests against the built site assert that the count's position in the HTML precedes every capability name and every section heading, and that the number printed matches what the spec tree actually contains rather than what the page claims. Status is carried as a colour on every requirement and as one proportional bar summarising the whole tree, in both light and dark.

cited files are rendered into the site as pages of their own, and listed on the landing page under "Evidence on file". A test walks every built page and asserts that every link resolves to a file that exists. Another asserts that a cited path has a page. docs/rtsmart-boot-log.txt reaches the site with the two NUL bytes a serial capture left in it shown rather than removed.

docs/evidence/spec-site-build.txt records a run over a staged tree in which three requirements declare neither a marker nor a citation: the command names each one and exits non-zero, and the page it wrote carries them under "Build defects". Unit tests assert that the classifier raises on a requirement carrying neither rather than returning grounded, and that a marker quoted in a code span is not read as a marker — a bug the first real build produced, which reported two grounded requirements as unverified.

docs/evidence/spec-site-build.txt records the date, the machine, the Python, Node and Astro versions, and the measured build. The budgets in scripts/build_site.py are set well above it, with the headroom stated and the reason for it. A test forces a breach and asserts the failure names the measured value and the budget.

observed from a machine that is not the build host, over one push. Before: https://knewter.github.io/tdisplay-k230/ served "generated 2026-09-21 02:55 UTC" and "1 of 11 requirements is unverified". Commit e70934a was pushed to main at 2026-09-22 00:21 UTC. Fifty-odd seconds later the same URL served "generated 2026-09-22 00:21 UTC", "1 of 18 requirements is unverified" and six capability pages, with nothing else done by anyone. Recorded in docs/evidence/spec-site-build.txt, which also records that the previous day's failing builds were not published — the URL served the last good build across five pushes while the tree was in a state the build rejects — as an inference from what the URL served rather than from the CI logs, which were not read.

docs/evidence/spec-site-work-board/README.md records the host layout and link checks and the published four-lane page at revision 95595a8e.* The documentation site SHALL provide a touch-readable work board with planned, in-progress, verification/review, and shipped/archived lanes. Each work item SHALL show its task progress, next concrete action or evidence gate, dependencies, and links to committed proposal, accepted spec, or evidence where available. Where source code has landed but physical proof remains, the two states SHALL be distinct. A checked task count alone SHALL NOT imply shipment, deployment, or physical verification.

docs/evidence/spec-site-work-board/README.md records the committed generator tests, exact build, published revision and link observations.* The work board SHALL be generated from committed repository state at an identified revision and build time. Any status that cannot be derived from proposal, task, archive, or evidence files SHALL come from a reviewed committed override with a rationale and source link. Missing or inconsistent overrides and broken links SHALL fail the build. The page SHALL describe itself as a dated snapshot, not live task or agent telemetry, and SHALL exclude private workstation paths, addresses, credentials, and uncommitted work.

docs/evidence/spec-site-work-board/README.md records the bounded source and Markdown tests, browser interaction checks, and successful Pages deployment of the whole-card detail at revision a8b3c747.* The work board SHALL make each entire card a single keyboard-accessible control that opens its committed proposal, design, tasks and delta specification inside the dashboard, with readable headings, tables, code and links rather than raw source text. The detail SHALL identify the same status, task progress and snapshot revision as the card. Published evidence links SHALL remain on the site where a local evidence page exists, and pinned external source links SHALL be secondary. The reader SHALL be able to close the detail with touch, keyboard Escape or browser Back and return focus to the selected card; a direct detail URL SHALL reopen the item. The detail SHALL use only committed content from the displayed snapshot, without a live GitHub fetch.