Wiki maintenance roadmap

Direct clone recovery, October 15, 2026

• Record the normal published package, completed private renderer matrix and protected current-profile preservation.

• Complete installation and actual-profile recovery in the application task; no wiki result substitutes for those checks.

• Add the complete empty-container recovery article, conservative ownership rules and current acceptance boundaries.

• Link the recovery article from Home.

• Publish and verify the current main/master refs, mirror the complete wiki into the documentation website and verify changed live content.

Earlier documentation

• Add the complete native-free startup repair article.
• Link the article from Home and Developer Guide while preserving existing contributions.
• Publish the documentation and verify exact master and main refs at 12975393cb5a5a831009eb4d569d573c24671291.
• Verify the rendered startup article and its Home and Developer Guide navigation.
• Mirror the 14-file wiki snapshot into the public documentation website and verify all 15 article/index routes, 95 internal links/anchors, 115 image source bytes and exact About homepage.
• Record the October feature-contract review with implementation gaps kept explicit.
• Publish and verify the 15-article contract-review snapshot at application source 1a4d409: all 107 internal links/anchors, 118 referenced assets and 335 catalog entries pass live readback.
• Record completed exact root builds, isolated argument workflows and the qualified release capture without claiming installed-profile acceptance.

Package, installed startup and existing-profile acceptance remain separately tracked in the application repository. Wiki publication does not establish those results. Master remains load-bearing and no deletion is required here.