Merge pull request #167 from fiddlerwoaroof/docs/commit-frequently

docs(agents): commit frequently, so the work is safe in git

AGENTS.md

@@ -126,9 +126,16 @@ Two agents each adding a workspace member will still collide in
    reports spurious failures. And **never pipe a gate**: `$?` must be the gate's
    own, and `check-comment-runs.py --check-evidence` prints two lines with the
    comment cap **first**, so `| tail -1` silently drops half of it.
-4. **Do not push, do not merge to `main`.** The orchestrator merges.
-5. The commit-message trailers, spelled out.
-6. **What to report**: branch and commits, what changed per ticket, *what could
+4. **Commit frequently, so the work is safe in git.** A WIP commit after the
+   first green test, and again after every meaningful step. A worktree is not
+   durable storage: an agent finished a whole ticket with every gate green and
+   lost all of it, uncommitted, when its worktree was deleted during a disk
+   cleanup. Tidying the history before the PR is fine; losing it is not.
+5. **Do not merge to `main`.** The orchestrator merges. Pushing the agent's own
+   branch (`git push gh HEAD:refs/heads/<branch>`) is encouraged once it is
+   worth keeping.
+6. The commit-message trailers, spelled out.
+7. **What to report**: branch and commits, what changed per ticket, *what could
    not be verified and why*, and proposed repo-map/`kb.pl` text. Ask explicitly
    for the thing the agent learned that the ticket did not predict — that is
    consistently the most valuable part of a hand-back, and agents omit it unless