feat: close issues through a script

Closing was the last regular tracker operation with no script behind it.
The only way to move state: was a raw `tea api -X PATCH` against
repos/OWNER/REPO/issues/N with a hand-written body, which spells out the
owner, the repo and the request shape — the three things _gitea.py exists
to hide — and which needs a Bash(tea api *) permission wide enough to
cover -X DELETE on the repository.

close.py takes explicit ids, one or many, as a local slug or as any key
form pull.py accepts (42, #42, owner/repo#42, a URL). A slug resolves
through its gitea: field while the file is there and through .remote.json
after push has dropped it, so an issue with no local copy is still
closeable by name. --reopen is the same run backwards.

State only: the payload carries state and nothing else. Closing is not an
edit; editing stays pull -> change -> push --update. No --milestone and
no --label either — which issues are finished is a judgement about
content, and this only carries one out, one named id at a time.

An origin: local issue is refused: it is not in the tracker, so there is
no state there to change, and the error names the id rather than quietly
editing one field of a local file. Every argument is resolved before
anything is sent, so a typo in the third id cannot leave the first two
closed, and one run addresses one repo — a key that names its own is sent
there instead of to whatever repo the CWD happens to be in.

The local file is written only after the tracker confirmed this write: an
object carrying the number that was PATCHed, in the state that was asked
for (close.confirmed). A non-2xx, a transport that would not run, an
answer for another issue, a 200 that still says open — the run stops and
the file is byte for byte what it was. --dry-run prints the same lines,
makes no request at all and needs no pinned login.

tea-runner rule 4 narrows accordingly: closing was forbidden because
nothing but a raw call could do it, not because it is dangerous. It may
now close the ids the caller named, and no others; deleting and retitling
stay forbidden.

tests/test_close.py stubs the transport at _gitea.api and, for the
non-2xx path, one layer lower at _gitea.subprocess so a CLI that exits 1
is proved end to end. 286 tests, no network, no tmp/issues.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

agents/tea-runner.md

@@ -29,7 +29,8 @@ to fill the gap yourself.
 
 Load the skill, do not remember the flags:
 
-- `/tea:sync` — `pull.py`, `push.py`, `comment.py`, `remote.py`, `labels.py`
+- `/tea:sync` — `pull.py`, `push.py`, `comment.py`, `close.py`, `remote.py`,
+  `labels.py`
 - `/tea:issue` — `issue_check.py`, `issue_tree.py`, `issue_index.py`,
   `issue_new.py`, `issue_ac.py`
 - `/tea:wiki` — `wiki_ls.py`, `wiki_pull.py`, `wiki_push.py`
@@ -65,10 +66,15 @@ instead of trying it.
    `wiki_push.py` needs `-m`; use the caller's words, never your own summary.
    Report the number and URL `push.py` printed; that is now the only address
    the issue has.
-4. **Do not close, delete, or retitle anything** on either side. On the wiki
-   that means no `--retitle`: renaming a published page abandons the old one.
-   The one deletion you may cause is push's own, on the issue you were told to
-   push.
+4. **Close only the ids the caller named.** Closing is a script now
+   (`close.py`), so it is yours to run — under the same discipline as push: the
+   ids the caller named, and no others. Never widen the set, never infer that
+   an issue is finished because its checkboxes are ticked or its branch is
+   merged; whether work is done is a judgement about content, and content is
+   never yours. `--reopen` is the same rule backwards. **Deleting and
+   retitling stay forbidden** on both sides — on the wiki that means no
+   `--retitle`, since renaming a published page abandons the old one. The one
+   deletion you may cause is push's own, on the issue you were told to push.
 5. **One retry, maximum.** A command that fails twice is a finding. Do not
    permute flags looking for one that works.
 6. **No payload dumps.** Never run `tea issues -o json`, never `cat` a pulled
@@ -122,3 +128,4 @@ Report these and halt; none of them is yours to resolve.
 | a dependency is still `origin: local` | name the id; the caller decides whether to push it |
 | a milestone or label does not exist in the repo | the script prints the real ones — pass that list through |
 | a script asks for a decision (type, label, `--force`) | `blocked:` with the question |
+| `close.py` is refused by Gitea because the issue is still blocked | the tracker's own line, and the blocker's number; the caller decides |