[2.0] Verify production website deployment and release cutover

Start with .github/workflows/release.yml, where deploy-site and publish-editors only run on the rc ref, and with site/utils/public-env.js, where a main build lacks an explicit production origin. Read #467, #473 and #479 for the linked gates. Done means every unchecked release gate in the issue is verified or documented, with no deployment changed.

Parent: #467

Scope and acceptance

Verify exact source/build delivery, stable versus RC domains, live redirects/routes/assets/HTTP/cache/search, canonical/portable-doc origins and a reversible cutover. Account identifiers, hooks, credentials and previous private deployment identifiers stay outside this issue.

Candidate: 9efee4d32. Publication and deployment remain on hold. These records distinguish source/assembled-artifact evidence from public-registry and deployed-product evidence.

Implemented

• Stable and RC delivery have explicit canonical origins. A no-op semantic release cannot borrow another version and trigger delivery.
• Site delivery uses the actual completed release version and exact source revision, verifies the static output, checks the target Pages project/production branch/domain, and uploads that output. It no longer uses a moving-branch deploy hook.
• Validation retains the exact build and checks all local destinations, redirect chains/cycles, canonical/sitemap/portable-doc origins, browser interactions and no-JavaScript reading behavior. Static redirect validation is not live edge verification.
• Cutover runbook covers legacy/RC/stable routing, retained URLs, evidence and rollback. The private account worksheet and actual rollback identifiers still require completion/confirmation.

Acceptance status

• Define stable site/editor triggers and explicit production canonical origin.
• Pass all final build/contract/browser checks and retain that exact output.
• Stage the exact output and verify live routes/redirects/assets/search and origins.
• Complete the domain-cutover/rollback record, including private previous deployment identifiers.
• Perform post-deployment verification after an explicitly authorized release.

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.

Private preparation progress — 2026-11-05

The existing stable/v1 recovery deployment and a bounded recovery-URL rendering check, current stable/RC/v1 DNS targets and proxy/TTL, zone cache settings, empty Page Rules/Cache Rules inventories, the existing RC homepage redirect and relevant Worker route are recorded privately. No account identifiers or raw platform settings are posted here. No DNS/cache/rule/hosting change or deployment occurred. The full prior artifact digest, intended stable 2.0 target, scoped deployment configuration and responsible release/rollback operators still require completion before authorized cutover.