plans: row 237 follow-up N1 brief, a retry after publish-timeout pushes once (duckworth-0069, P19 440)

docs/plans/2026-10-20_agent-credentials.md

@@ -125,3 +125,22 @@ exists, and no code change is planned. What's missing is a test that pins each g
 
 Gate: Duckworth approves the manifest. The bus, seat and cli suites and every `scripts/test-*.sh` are green
 on Sage's gate, and the three mutants are killed.
+
+## Brief: row 237 follow-up N1, a retry after publish-timeout pushes once
+
+Sage, 2026-10-21, from Duckworth's row 237 note N1 (#1743 comment 29810, duckworth-0069) and Megavolt's
+row 237 BUILD.md residual 2. Owner Megavolt, reviewer Duckworth, gate owner Sage. Builds on row 237's landing
+d7d943199. Vikunja P19 440.
+
+The git socket gives up with `publish-timeout` (`packages/cli/src/git-socket.mjs:433`) while the bus
+process's push may still be running (`publishPush` in `packages/bus/src/runtime.mjs`, entry `running`).
+`publishRefused` then drops the ticket, so row 237's `publish-busy` check no longer holds the decision. A
+retry to another branch can then push a second ref to the fork.
+
+Pick one fix and say why in BUILD.md. Either keep the decision held until the bus's push ends, or kill the
+push on timeout and wait for it to exit before the ticket goes. Add a test that starts a slow push, times
+it out, retries to another branch, and finds exactly one ref on the fork. Add a mutant that removes the
+fix. Don't change the `publish-timeout` refusal text.
+
+Gate: Duckworth approves the manifest. The bus and cli suites and every `scripts/test-*.sh` are green on
+Sage's gate, and the mutant is killed.