fix(www): replace stale benchmark route/sitemap counts with durable build-truth claim (#1312) - #1313
Merged
Merged
Conversation
…uild-truth claim (#1312) The benchmark page (en+zh) asserted '30 route modules, 205 sitemap URLs', handwritten and stale since PR #1106 — the candidate build emits 146 sitemap URLs across 150 pages from 34 route files, and the false claim shipped verbatim in built HTML (verifier NO-GO F1). Adjudication per derive-from-owned-truth: the counts add no benchmark value (the page measures properties, not site scale) and cannot be derived into Markdown without new injection machinery, so the volatile numbers are removed in favor of a durable architectural property — every route prerendered, the sitemap built from routes. No numeric claim remains to silently rot; en/zh parity and locale availability stay under the existing www:check-truth and content-graph gates, and the content-graph fingerprints are regenerated.
Deploying openelement with
|
| Latest commit: |
bb767f8
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6d8a9e86.lessjs.pages.dev |
| Branch Preview URL: | https://fix-1312-benchmark-durable-c.lessjs.pages.dev |
Contributor
|
APIError: Insufficient Balance |
Root deno fmt re-pads markdown tables to cell width; my edited cells changed the column widths. Content-graph fingerprints regenerated to match the formatted sources.
Contributor
|
APIError: Insufficient Balance |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Verifier NO-GO finding F1 (Beta.2 closure,
docs/evidence/2026-09-04-v044-beta2-closure-verification.md):www/content/architecture/benchmark.md:11andbenchmark.zh.md:11claimed "30 route modules, 205 sitemap URLs". The claim was handwritten, stale since PR #1106, and shipped verbatim in built en+zh HTML — a fresh build at candidate aa3dd70 emits 146 sitemap URLs / 150 pages from 34 route files. No gate covered it.Closes #1312. Part of #1155. Stage #1288.
Owner
www content truth (
www/content/architecture/), gated bywww:check-truth/content-graph:check.Before
| SSG build (www) | 30 route modules, 205 sitemap URLs |(en) /30 个路由模块，205 条 sitemap URL(zh) — both false at candidate; verified RED:grep -c '<loc>' www/dist/sitemap.xml= 146;grep '205 sitemap URLs' www/dist/architecture/benchmark/index.htmlmatched (stale claim shipped in built output, both locales).After
| SSG build (www) | Every route prerendered; sitemap built from routes |(en) /每个路由都静态预渲染；sitemap 由路由生成(zh). Verified GREEN in built output: new claim present indist/architecture/benchmark/index.htmlanddist/zh/architecture/benchmark/index.html; stale strings absent (0 matches). Committed content-graph fingerprints regenerated (only the two benchmark entries changed).Chosen approach per claim (adjudication)
packages/adapter-vite/src/internal/content/sitemap/). With no volatile numbers left, there is nothing to drift; existing en/zh parity and locale gates (www:check-truth,content-graph:check) keep the two locales consistent.Why-not-second-owner
No second owner: the fix is confined to the two content files plus their committed content-graph fingerprints. No tool, gate, or CI policy change was needed —
www:check-truth,content-graph:check,www:check-current-truth, and the build-composedwww:check-artifact-truth/www:check-linksalready cover these surfaces (ci+release tiers via AutoFlow policy), so no new CI wiring was introduced.Evidence
grep -c '<loc>' www/dist/sitemap.xml→ 146; claimed 30 route modules vs 34 route files inwww/app/routes; stale claim present in built en+zh HTML.deno task content-graph:check→ passed (byte-identical regeneration)deno task www:check-truth→ passed (nav + locale availability + route locale honesty + blog language + roadmap)deno task www:check-current-truth→ passedmarkdownlint-cli2on both edited files → 0 issuesdeno task build→ exit 0 (SSG 150 pages, sitemap 146 URLs,www:check-artifact-truthpassed,www:check-linkspassed); built benchmark pages carry the new claim in both locales, stale numbers gonedeno task test→ exit 0 (full suite incl. examples)Scope
3 files:
www/content/architecture/benchmark.md,www/content/architecture/benchmark.zh.md,www/app/data/_generated-content-graph.json(fingerprint regeneration only). No general content rewrite.Risk
Low. Content-only change; the reworded claim states a build invariant (full prerender + sitemap emission) that the SSG build itself proves on every run. No gate or CI changes.