[2.0] Audit release documentation, migration and website experience

This is a release-audit tracker, not a contained task, and it is not a good first issue. Start with site/tests/tooling-examples-checks.ts lines 119-120 and site/content/guide/language-service/content.mdx line 125 to see the settings-table mismatch. Done would mean every listed gate is resolved and rechecked, which depends on the duplicate-ID work in #479 and the final registry state.

Public release and deployed browser validation — 2026-11-06

The public npm cohort and GitHub Release reconcile with the published 2.0.0 installation and migration guidance. All 15 documented default static integration recipes passed from the real public registry. The final site has 384 pages and 42,650 local links across the five-locale documentation. At css.master.co, the actual Chromium/Firefox/WebKit suite passed all 204 profiles and 15 with JavaScript disabled, including its automated accessibility checks. The real v1 → 2.0 switch preserved English and Traditional Chinese.

The remaining item is a genuine screen-reader session against the deployed site. The macOS VoiceOver/Safari operator protocol is prepared; actual assistive-technology behavior remains unverified and is deferred. Canonical browser proof SHA-256: d5c59427343fed2ea3179cedb6422b20f30d5425d883d9619fce475993a248e5.

Current verification status — 2026-11-05

441516cfe passed complete candidate CI: 161 translation resources with no problems, 43 portable export tests, 28 documentation example tests, 384 rendered routes, 204 browser profiles and 15 no-JavaScript profiles. Astro and Webpack documentation was reviewed in all five languages. Actual public registry, deployed browser/accessibility and assistive-technology checks remain open.

The older candidate records below are retained as historical evidence.

Parent: #467

Scope and acceptance

Verify installation/migration guidance, reference exports, examples, search, portable docs, translations, SEO and representative desktop/mobile, light/dark browser and accessibility behavior. Final registry and deployed checks remain required.

Candidate: 9efee4d32. Publication and deployment remain on hold. Source/assembled-artifact evidence is distinct from public registry and deployed-product evidence.

Repairs and bounded accessibility evidence

• Both authored-document mismatches are repaired: the external-style explanation follows article ownership, and the language-service test reads all 12 authored settings/defaults. The llms and documentation-example checks are required in candidate CI.
• #479’s duplicate SVG IDs are fixed. Contributor examples use current APIs/syntax and the README workflow badge is corrected.
• The original home-header CSS change has an explicitly attributed budget/contract baseline. A later navigation change from 52cde8772 changes class ordering and hydration metadata across 151 routes; review confirms all 2,287 CSS segments, CSS bytes/hashes, normalized manifests and resource order are unchanged. The new baseline records that source change, without increasing CSS budgets.
• The generated package reference’s Installation link now has a permanent visible arrow. The href and Markdown export are retained, with no styling-engine or renderer changes.
• Manual review of the prior retained immutable build exercised 14 mobile-menu keyboard cases, four link-focus cases and 80 contrast measurements (minimum 5.699:1). A separate isolated source build verified the repaired link in four viewport/theme profiles. This is bounded artifact/source evidence, not final deployment or full assistive-technology certification.
• QA record records baseline attribution and verification boundaries.

Acceptance status

• Resolve authored-document mismatches, duplicate IDs and attributed style/contract failures.
• Review representative artifact keyboard/contrast behavior and repair the identified link cue.
• Pass final exact-candidate static/doc/browser checks and retain their build digest.
• Reconcile installation/migration/release copy with final registry products and versions (#470).
• Verify accessibility and representative rendered routes on the final authorized deployment (#472), including remaining assistive-technology coverage.

Final verification — 2026-11-05 (Asia/Taipei)

Exact committed candidate: 9efee4d32, pushed to rc. Source preparation and the complete non-publishing matrix are verified. Public stable readiness remains held by the delivery acceptance items below.

• Full release-candidate CI: SUCCESS, 33/33 jobs, attempt 1. All eight native targets, Linux quality/site/E2E, Rust, full Windows/macOS graphs, editor gate and aggregate required gate passed on this exact source. No CI or failed-test retry was needed for this final candidate.
• Packed native closure: SUCCESS, 11/11 jobs, including all eight actual native consumers and the full Windows required gate. Fresh ZIP digests, exact source/run/target identities and non-target dependency integrities were independently verified.
• Independent full Windows validation: SUCCESS. CLI 112/112, installer 73/73, ten CLI/MCP repetitions, focused Next 10/10, 59/59 package tasks with zero cache hits, and 37/37 example tasks (26 cached prerequisites; all 11 example builds executed). Actual watcher traces end with exact none-only CSS, no obsolete rules or excluded grid, successful quietness/cleanup and valid controlled registration chronology. Hosted macOS 26 also passed 59/59 uncached package tasks and 37/37 example tasks on the same revision.
• All 16 VSIX archives and 16 actual host/publisher proofs passed exact-source/version/hash/native-payload validation: version 2.0.37, both publishers, 12 desktop and four official Alpine remote host proofs. Activation, completion, hover and restart passed in real installed extension hosts; native/LSP-only checks did not substitute for installation. The source gate revalidated those same VSIX bytes, not rebuilt replacements.
• Current Rust/Wasm versus JavaScript engine differential: 0 / 200,099 differences. Runtime browser E2E 672/672 and Next E2E 11/11 passed; bundle/CDN and generated-program gates passed. No failed/flaky/retry summary was observed in the E2E log.
• The clean same-source 34-archive cohort, 0.0.0-archive.20261105.7, passed fresh npm 11.19.1, Bun 1.4.4 and pnpm 12.15.0 consumers. Wrapper and native-artifact revisions are both exactly 9efe. Each locks all 34 candidate versions/integrities and installs 27 host-compatible packages. Native/Wasm, compiler/PHP, CLI, runtime/integrations, exact-cohort installer and MCP rendering/observed child-exit checks pass. npm additionally passes packed Astro/Svelte SSR/hydration, actual missing-hook rejection and Chromium startup/mutation. This is local assembled-archive evidence, not public registry evidence. Proof SHA-256: 819ddbcdfcbaf3c7e996d235073fb5f407ad6249590322dd84dbcbb9e4c51c45.
• Current site artifact: 155 pages, 16,202 links, 84 profiles (28 each Chromium/Firefox/WebKit), zero failures; LLMS 39/39, 80 CSS contracts / 2,287 exact segments, 85 public assets and the 44-CSS-asset budget passed. All 1,375 retained output files rehash to build digest 395c44f327876695e989747166a3298d79b75f26dd1aadf01357432e52f4e4ed; ZIP digest d469a9fb4034334be19da398ef59595fbad923e37751058f8b7d9e004e9f32e5 matches GitHub. Report revision is exact 9efe. sourceStatus contains only generated untracked site/.cache/, with no tracked source changes; that actual porcelain is disclosed rather than relabeled wholly clean. liveEdgeVerified=false.
• Both-publisher RC authorization passed on 9efe. Separate stable-main authorization passed on auth-only ee4d1cade, using VSCE 4.0.0 and Open VSX 1.0.2. This is existing identity evidence, not promotion of the 2.0 product to main or a public store release.
• Source defects #484–#488 are fixed and explicitly unreleased. Historical allocation failures, the 5dab stale-rule trace and f9 Windows EPERM failure remain recorded in their owning issues; historical or mixed-native evidence was not substituted for this final matrix.
• The final read-only registry inventory (2026-11-04 20:40 UTC / November 5 Asia/Taipei) still finds no 2.0.0 version among all 34 names; the same six public package metadata endpoints return 404. Public absence does not prove namespace ownership. Release and site-snapshot workflows remain disabled; no package/store publication, channel promotion, deployment or DNS/cache change occurred.

All source/native/editor validation above is complete. Actual public-registry/store correspondence, installation and legacy-listing acceptance, authorized staging/cutover/live accessibility checks, and the remaining private configuration/rollback prerequisites are still open. Publication and deployment remain held.