An agent's own comment must never start its next run: the direction issue looped 27 times tonight #383

Tonight (2026-10-02 03:2x–12:2xZ) the dispatcher started a run on the direction issue #334 every ~20 minutes: Atlas, assigned to it, read the issue, found that the newest comment was its own earlier reply, declined ('not feedback from a person'), and wrote that decline as a new comment — which the dispatcher took as a new comment on an assigned issue and started the next run. 28 comments, 27 runs at about $1.40 each, nothing built, and the builders' slots stayed busy or the map never advanced (working: 0 the whole time).

Intent: an agent's own comment never re-triggers a run for that agent, and a planner handed a direction runs ONCE per hand-off.

Acceptance:

• [ ] src/crew/dispatch.ts: a comment or review authored by the assigned agent itself (or by any agent, for an issue assigned to an agent) does not queue a follow-up; only a person's comment, a review, or a check result does — with a test that replays tonight's sequence and proves one run, not twenty-seven
• [ ] a declined run writes its reason to the run record and the ledger, not as an issue comment
• [ ] the direction issue: after a planning run completes (plan written or declined), the assignment is cleared by the forge (as planIfThin already does before re-assigning), so a stale assignment cannot loop
• [ ] a circuit breaker: three consecutive failed or declined runs on one issue within an hour park the issue (parked, visible on the map) and stop dispatching it until a person touches it; the board's 'needs you' shows it
• [ ] usage shows the loop's cost on the board as what it was

Files: src/crew/dispatch.ts, src/crew/autonomy.ts, src/crew/runner.ts, tests. Found by the operator at 12:23Z; the assignment on #334 was cleared by hand to stop it.