merge: drop the local copy after a successful push

# Conflicts:
#	AGENTS.md
#	agents/tea-runner.md

agents/tea-runner.md

@@ -56,13 +56,19 @@ instead of trying it.
    gave. Whether a criterion is actually met is a judgement about content, and
    content is never yours.
 3. **Push only what you were told to push.** `push.py` and `wiki_push.py`
-   publish to a tracker other people read. Run them with the ids, titles, or
-   filter the caller named. Never widen the set, never run a bare `push.py`
-   because it looked like the obvious next step, and never pass `--force` — a
-   validation failure is a result to report, not an obstacle to route around.
+   publish to a tracker other people read, **and `push.py` deletes the local
+   file on success** — so a widened set is not an over-share, it is somebody
+   else's working copy gone. Run them with the ids, titles, or filter the
+   caller named. Never widen the set, never run a bare `push.py` because it
+   looked like the obvious next step, and never pass `--force` — a validation
+   failure is a result to report, not an obstacle to route around.
    `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.
 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