Playbook 09: a deletion is approved as an ask on the operator's warrant once design 58 milestone 7 is built; until then the operator runs the approved list

.claude/skills/hq-cleanup/SKILL.md

@@ -33,8 +33,10 @@ place, and ask one question: delete the Safe list? Likely-safe and Unknown items
 - Forge branch: `gitea.gitea_delete_branch`.
 - Worktree: `git worktree remove <path>` (never `--force`), then `git worktree prune`.
 - Local branch: `git branch -d <name>` (never `-D`).
-A session's permission check may refuse these; then hand the operator the approved list as a file, with the
-commands, and do not work around the refusal.
+Once design 58 milestone 7 is built (issue 884), each deletion is a call held as an ask: the operator approves
+the exact list on Telegram and the mesh carries it out on the warrant. Until then a session's permission check
+refuses these; hand the operator the approved list as a file, with the commands, and do not work around the
+refusal.
 
 ## 4. Report
 

00-META/process/09-cleanup.md

@@ -35,7 +35,10 @@ reported and left.
    items as listed? The likely-safe and unknown items are separate questions, item by item when few.
 4. **Delete only the approved list**, each with the command that refuses an unsafe case (a worktree removal
    that refuses a dirty one, a branch deletion that refuses an unmerged one). A refusal is reported, never
-   forced.
+   forced. The operator approves a deletion on a channel that proves who answered, as an ask bound to that
+   exact list and carried out on the warrant (ADR 0387, design 58 milestone 7, issue 884). Until that is built,
+   an agent session's permission check refuses these deletions, and the approved list is handed to the
+   operator to run.
 5. **Report**: what was cleaned, what was kept and why, what was unknown, what the operator kept, and the
    missing tools, each opened as an issue (`issue-tracker.open`) or added to an existing one.