Wiki removal review

Content and live-site cutover verified on 2026-09-27. All 26 inventoried Wiki entries have maintained destinations on the complete site. Actual HTTP checks passed all 20 distinct routes and checked their development-version identity. The repository Wiki remains disabled, both retired workflow registrations are disabled_manually, and neither has an active writer run.

The complete site was published from 69a7b30dd89b298254a16b049180bbd9082ecdec through push CI 36285745230, attempt 1, and protected publisher 36287023135, attempt 1. The immutable site artifact is 10920985707, digest sha256:13cbc99efb2e26e5302209f03b76f31b47c9595e2effa70969ed158804852727; the deployed tree digest is sha256:446a84536f367bb04290b4fd062e1a7201fa005a230e05edd7a837e485efb748. The original publication, live-browser, build/theme/ example/version/discovery receipts and final Wiki observations are retained in documentation-validation-36287023135.zip, 13,532 bytes, SHA-256 ecfbb7f76aec1bb41c10bade136b2f8b3445512bc29e5644a22ca1175abd1834. Its public bytes were independently verified. This supplemental archive is separate from the native publisher's attested assets.

PR #507 removed the old publisher source before this gate. The September 26 retirement observation records the disabled registrations and Wiki setting. The newer observation rechecks those facts; it does not claim they happened after the gate decision.

The maintainer's September 22 decision replaces the old archive-notice and legacy-link preservation plan. Useful material belongs in current guides; obsolete Wiki URLs, anchors and pages need not remain live. The migration inventory preserves original sources, assets and attribution.

Completed destination verification

The final public receipt records each maintained destination URL, status 200, byte count and response SHA-256. It verifies the formerly absent runtime identities and migration pages as well as every other mapped destination. The inventory's CONTRIBUTING.md authority now uses the maintained Contribute guide as its website entry point for the development-workflow and repository-map entries. The current receipt records that mapping separately; the original inventory remains unchanged. Architecture decisions use the site's /decisions/ routes. The older observations below remain historical, including their 404 results. They are not rewritten as passes or used as proof of the newer site.

Website and destination observations

The live documentation website reported source 80d7924a6e203b88c889f4b9bd3f6afb2f0fe48c in its site manifest on September 21, 2026. The reviewed route map was generated from acf9a3d0b150cb0be345497fe2f44f56ca30f1b5; its 304 pages include current and versioned documents. Those distinct source identities are not interchangeable.

Direct HTTP HEAD requests checked every distinct mapped destination. Twenty-two entry pages have live replacements. FAQ and Glossary map to the pending runtime identities page; the sidebar and footer map to the pending migration guide. Those two distinct routes returned 404 and must be published and checked before cutover. Development Workflow and Repository Map use the existing contribution learning path; that guide links to the repository contribution contract.

Inventoried Wiki entry	Content destination	HTTP status on September 21
Activation-Lifecycle	Local activation lifecycle	200
Architecture	LSF architecture overview	200
Capsule-Development	Creating a capsule	200
Contracts-and-APIs	API surface map	200
Core-Concepts	LSF architecture overview	200
Deployment-and-Routing	Embedded deployment catalog and local routing	200
Design-Governance	Architecture Decision Records	200
Development-Workflow	Operate a local node and choose a contribution	200
Execution-Cells	Execution-cell architecture	200
FAQ	Runtime identities and recovery terms	404; publication pending
Getting-Started	Standalone echo quickstart	200
Glossary	Runtime identities and recovery terms	404; publication pending
Home	Standalone echo quickstart	200
Operator-CLI	Operator CLI	200
Performance-and-Infrastructure	Phase 1 extension: measured results and Phase 2 handoff	200
Phase-0-Runbook	Phase 0 executable spike	200
Phase-0-Status	Phase 0 completion gate	200
Phase-1-Status	Phase 1 completion report	200
Repository-Map	Operate a local node and choose a contribution	200
Roadmap	Engineering roadmap	200
SDKs	API surface map	200
Security-and-Isolation	Security architecture	200
State-and-Effects	State and effect architecture	200
Testing-and-Benchmarks	Benchmark evidence retention	200
_Footer	Wiki migration and publication continuity	404; publication pending
_Sidebar	Wiki migration and publication continuity	404; publication pending

Final administrative closure and future ownership

The accepted guide review, complete-site publication and all destination checks satisfy the content prerequisites for #345 and the collective gate. After the Phase 3 decision is merged and published, recheck the already disabled Wiki and retired writers and close #356. Do not recreate the service to repeat its removal or publish archive notices.

Future prose belongs in docs/. Website presentation, search, version handling and publication belong to website/ and its protected publisher. Git history and original receipts retain attribution. The retired Wiki writers must not resume synchronization or recreate another documentation service.

Bounded rollback

Recover the website through its protected flow using a previously published complete artifact and the exact currently live source. Do not restore Wiki publishing, move runtime tags or rewrite historical benchmark receipts.