Wiki removal review

The repository Wiki is disabled. PR #507 already removed its publisher from docs/wiki, and the remaining bootstrap and publisher registrations were disabled on September 26. The retirement observation confirms both registrations and zero active writer runs. The complete-site deployment and replacement-route checks still need their final receipt before #356 closes.

The maintainer decision of September 22 replaces the earlier plan to publish 26 archive notices and preserve legacy navigation. Useful material belongs in current guides; old Wiki URLs, anchors and obsolete pages need not remain live.

The migration inventory records source d1035a50d2fd99b076c74dd958ca4437d909f2ec, published Wiki e0cc50fe654b783f189b30a8a6f7946d66177180, all four assets and historical identities. These pinned references establish attribution without retaining an active Wiki. The route observations below are historical checks, not proof of a completed website cutover. The newer retirement observation does not change their results.

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

Execution order

1. Preserve the accepted September 26 guide review and qualify subsequent guide corrections. The maintainer delegated those updates without another approval.
2. Publish the reviewed development site through the protected exact artifact flow. Record source, successful push CI run, attempt, artifact, publisher run and live receipt. Recheck every maintained destination, including the two routes that were absent at the historical observation above.
3. Switch repository and public entry links to the tested site and remove active Wiki navigation. Obsolete page content can be retired rather than copied.
4. Complete the Phase 3 gate using the content migration, guide reviews and live website evidence. Keep the actual earlier source-removal and settings observations; do not claim that those actions happened after this decision.
5. Recheck the disabled Wiki, retired workflow registrations and maintained entry links. Do not recreate or re-enable the old service to repeat its removal.
6. Record the resulting site/source identity and Wiki removal receipt in the migration guide, then close #356. Publishing archive notices, preserving legacy links or maintaining redirect pages is unnecessary.

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

Bounded rollback

A failed live destination check delays cutover until the site is corrected. After removal, recover the website through its protected flow with a previously published complete artifact and the exact currently live source. Do not restore Wiki publishing, move runtime tags or rewrite historical benchmark receipts.