aide-closelisted

Close a spec that turned out not to work: stamp the reason, move it to `archive/`, and let the code branch it never used be deleted rather than merged. **Input:** $ARGUMENTS (a spec number, a full folder ID, or an issue key its title began with, plus the reason the user closing it typed) ## Workflow The steps below are this skill's own, inside the queue's `close` step. Mark each one in the log, so a reader can follow the run: when it starts, write one line `close · Step N of X: <title> — started`, and when it ends, one line `close · 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 3: Run the mechanical script First write `close · Step 1 of 3: Run the mechanical script — started`, and when this step ends, `close · Step 1 of 3: Run the mechanical script — done`. Resolving the argument to a folder, checking whether a merge is open, and stamping-and-moving the folder is a script, the same way archive's own equivalent is — this session never reasons about whether the work is "done enough" to close, because Close does not ask that question: ```bash aide-close-spec --project-dir <project root> --spec <argument> \ --reason <the reason typed by the user closing it> \ [--specs-dir <specs repo root, if separate>] ``` The reason is the one thing this script refuses to run without. Read it from wherever this run was