Wiki Maintenance

The wiki is a summary and routing layer, not a second full copy of the docs tree and not the primary public docs site.

The primary polished docs surface should be GitHub Pages.

Wiki Rules

• keep the wiki homepage current
• keep _Sidebar.md aligned with the current docs information architecture
• use wiki pages to summarize and route, not to mirror every command contract
• refresh the wiki when the top-level feature map or start-here path changes
• keep the wiki thinner than the Pages docs site

When To Update The Wiki

• a new major feature bucket is added
• a new default user path appears
• a new host or integration meaningfully changes onboarding
• a knowledge-layer integration such as NotebookLM becomes a practical optional path for research or documentation workflows
• vault or graph analysis reveals missing hub pages, duplicated topic areas, or weak wiki routing
• README or docs/start-here.md changes enough that the wiki homepage would now mislead readers
• the docs layer starts surfacing more routes than a new user can reasonably absorb in the first pass
• repeated wiki confusion appears across sessions strongly enough to justify framework-level cleanup instead of just local routing help

Refresh Targets

• wiki/Home.md
• wiki/Getting-Started.md
• wiki/Feature-Index.md
• wiki/Workflow-Index.md
• wiki/Commands.md
• wiki/Hosts-and-Harnesses.md
• wiki/Automation.md
• wiki/Examples.md
• wiki/FAQ.md