Merge origin/main into feat/evict-closed-issues

Three doc conflicts, all unions: the script lists in AGENTS.md and the runner
gain both close.py and evict.py, and the sync skill keeps both the closing and
the evicting sections. Rule 4 of the runner is rewritten once to carry both
halves — closing is now a script it may run on named ids, retitling and remote
deletion stay forbidden, and the two allowed local deletions (push's own, and
eviction) are listed together.

skills/issue/SKILL.md

@@ -118,7 +118,9 @@ the table. Checkboxes are the exception — use `issue_ac.py`, below.
 
 If the issue is synced (`origin: gitea`), the file is a working copy: your edit
 is local until you run `push.py --update` from `/tea:sync`, and that push
-**deletes the file** once Gitea has it. Nothing tracks drift, and with one copy
+**deletes the file** once Gitea has it. Closing one of those is `close.py` from
+`/tea:sync` — it moves the state on both sides in a single run; editing
+`state:` here alone would only ever tell this machine. Nothing tracks drift, and with one copy
 at a time there is little to track — a file that is still here has not been
 pushed. Get it back with `pull.py <n>`; the slug does not change.