aide-wikilisted

Build or rebuild the project's wiki. The run is headless: no one answers questions, so decide and finish. **Input:** $ARGUMENTS (the tracking key `wiki-<project>`, then `refresh` when the run is a refresh; the project is the current directory and the specs root is named in the prompt) A **build** rewrites every generated page from the code as it is now, whether or not its files changed. A **refresh** rewrites only the pages `aide-wiki status` marks `changed`, adds a page for a part that has none, and leaves every current page as it is. The runner checks the result: a build that leaves a page from an older commit, or a refresh that leaves a `changed` page, ends unfinished. The wiki is the folder `wiki/` inside the specs root: `index.md`, `schema.md` and one page per part of the system. Every write under `wiki/` goes through `aide-wiki`, never through Write or Edit, and nothing is written outside `wiki/`. The prompt names the specs root and the project directory; pass them to every call as `--specs-root` and `--project-dir`. ## Workflow The steps below are this skill's own, inside the queue's `wiki` step. Mark each one in the log, so a reader can follow the run: when it starts, write one line `wiki · Step N of X: <title> — started`, and when it ends, one line `wiki · Step N of X: <title> — done`. A step that ends the run early says `— stopped: <why>` in place of `— done`, and one that does not apply to this run `— skipped: <why>`. ### Step 1 of 4: See what exists First w