aide-archivelisted

Archive a finished spec: settle any merge conflict on its branch, stamp it, move it to `archive/`, and merge what should outlive it into the project's living documentation. **Input:** $ARGUMENTS (a spec number, a full folder ID, or an issue key its title began with) ## Workflow The steps below are this skill's own, inside the queue's `archive` step. Mark each one in the log, so a reader can follow the run: when it starts, write one line `archive · Step N of X: <title> — started`, and when it ends, one line `archive · 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: Run the mechanical script First write `archive · Step 1 of 4: Run the mechanical script — started`, and when this step ends, `archive · Step 1 of 4: Run the mechanical script — done`. Everything mechanical — resolving the argument to a folder, checking whether a merge is open, reading `4-status.md`'s tables, and (when the work is done) stamping and moving the folder — is a script now, not something this session reasons about by hand: ```bash aide-archive-spec --project-dir <project root> --spec <argument> \ [--specs-dir <specs repo root, if separate>] ``` Pass `--specs-dir` whenever the specs root lives in a different git repo from the project — the specs repo has a branch of its own and can conflict independently of the project, and the script only check