A park note says what each failed try of the pull changed #10883

When the crew parks an issue whose pull went red more than once, the "Parked by the crew" comment now adds one line per failed try, e.g. try 2: src/b.ts. Checks run before the push: bun scripts/gate.ts and bun x tsc --noEmit pass, and every touched or related test file passes. I did not run the full suite.

• Wiring: a new parkPullTold in src/crew/park_pull.ts calls triesChanged and passes the lines to parkPull. Its two callers, the red-check answer in src/crew/dispatch.ts and sweepStaleReds in src/crew/stale_reds.ts, now use it.
• Limits: src/crew/tries.ts now tells at most 5 tries and 10 files per try (it was 2 and 4). It is out of scripts/unreached-allow.json.
• When it fires: the lines are added only when there are two or more tries. parkPull is unchanged for other callers.
• New test: test/crew-tries.test.ts builds a fixture repo with two red heads. It parks the pull and finds both try 1: and try 2: lines in the issue comment.
• Changed existing tests: I updated the expectations in test/crew-tries.test.ts to the new limits. Parking now reads git history first, so it lands a moment after the announcement. test/crew-failed-while-building.test.ts and test/crew-shared-red.test.ts now wait for the pull to close instead of asserting it immediately.
• Left out: if the git read fails, the note is written without the try lines.

To try it, park an autonomous repo's agent pull that has two red heads and open its issue.

Closes #10863

When the crew parks an issue whose pull went red more than once, the "Parked by the crew" comment now adds one line per failed try, e.g. try 2: src/b.ts. Checks run before the push: bun scripts/gate.ts and bun x tsc --noEmit pass, and every touched or related test file passes. I did not run the full suite.

• Wiring: a new parkPullTold in src/crew/park_pull.ts calls triesChanged and passes the lines to parkPull. Its two callers, the red-check answer in src/crew/dispatch.ts and sweepStaleReds in src/crew/stale_reds.ts, now use it.
• Limits: src/crew/tries.ts now tells at most 5 tries and 10 files per try (it was 2 and 4). It is out of scripts/unreached-allow.json.
• When it fires: the lines are added only when there are two or more tries. parkPull is unchanged for other callers.
• New test: test/crew-tries.test.ts builds a fixture repo with two red heads. It parks the pull and finds both try 1: and try 2: lines in the issue comment.
• Changed existing tests: I updated the expectations in test/crew-tries.test.ts to the new limits. Parking now reads git history first, so it lands a moment after the announcement. test/crew-failed-while-building.test.ts and test/crew-shared-red.test.ts now wait for the pull to close instead of asserting it immediately.
• Left out: if the git read fails, the note is written without the try lines.

To try it, park an autonomous repo's agent pull that has two red heads and open its issue.

When the crew parks an issue whose pull went red more than once, the "Parked by the crew" comment now adds one line per failed try, such as try 2: src/b.ts.

The earlier check failure was one test, "above the floor: a red is the pull's own, parked as ever, and no card" in test/checks-disk-red.test.ts. Parking now reads the pull's git history first, so the pull closes a moment after the red is announced. That test asserted it was closed immediately. It now waits for the close, the same fix I made earlier in test/crew-failed-while-building.test.ts and test/crew-shared-red.test.ts. The test was wrong, not the code. test/checks-disk-red.test.ts passes and bun x tsc --noEmit is clean. I did not re-run the full suite.

• Wiring: the new parkPullTold in src/crew/park_pull.ts calls triesChanged and passes the lines to parkPull. The red-check answer in src/crew/dispatch.ts and sweepStaleReds in src/crew/stale_reds.ts now use it.
• Limits: src/crew/tries.ts now tells at most 5 tries and 10 files per try, up from 2 and 4. It is out of scripts/unreached-allow.json.
• When it fires: the lines are added only when there are two or more tries.
• Tests: test/crew-tries.test.ts has a fixture repo with two red heads, parks the pull, and finds both try 1: and try 2: lines in the issue comment. I updated that file's expectations to the new limits.
• Left out: if the git read fails, the note is written without the try lines.

To try it, park an autonomous repo's agent pull that has two red heads and open its issue.

The park note now lists only the tries since the last human word, and the review items are done. bun scripts/gate.ts and bun x tsc --noEmit are clean, and I ran the tests for the files I touched. I did not re-run the full suite. The change is pushed.

• Since: parkPullTold takes a since argument, and both callers pass the lastHumanWord they already compute (answerRed in src/crew/dispatch.ts, sweepStaleReds in src/crew/stale_reds.ts). A red head older than that word is left out of the note. A new test in test/crew-tries.test.ts checks that an old red head is left out.
• Behaviour change in src/crew/tries.ts: triesChanged now diffs the first told try from the last excluded head instead of from the base. Without this the first told line would still list the excluded try's files. I changed the expectation in the existing "skips a green run, a run before since…" test to match, since it had pinned the old base diff.
• Race: a new test fires two parkPullTold calls together. It finds one winner and one note. parkPull re-reads the issue as open and closes it before returning, so the second caller sees it closed.
• Shared helper: test/helpers/pull-closes.ts exports pullCloses, which polls every 2 ms. It replaces the copied closes in test/crew-failed-while-building.test.ts and test/crew-shared-red.test.ts, and the inline loop in test/checks-disk-red.test.ts.
• Docs: docs/features/park-note-tries.md describes the try lines in the park note, with how to try it. I made it a new file, since neither app-crew.md nor crew-line.md covers parking.