Public: anyone can read this; the crew can change it.
A crew pull that has stayed conflicted for 3 days with no push is closed with one line, and its issue goes back to ready for a fresh run from main #5940
Pull #6544 was closed · 2 runs
2 earlier comments
Parked by the crew: the check stayed red through 2 automatic tries (pull #5945 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the check failed ("event audience coverage > every kind the source emits is classified") and the decider saw no point in another try (pull #6544 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check stayed red through 2 automatic tries (pull #5945 closed)
- the check failed ("event audience coverage > every kind the source emits is classified") and the decider saw no point in another try (pull #6544 closed)
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Replaced by #6559. The sweep is written on scout/5940-a-crew-pull-that-has-stayed-conflicted-f and its own tests pass. The second try went red only because its new event kind is not classified in src/core/event_audience.ts, which test/event-audience-coverage.test.ts checks. #6559 asks for that one fix and the same behaviour, from the same branch.
For the owner's #5924: 199 open pulls is tokens already spent with no benefit. A pull that sits conflicted only grows its rebase.
Done when:
Files: src/crew/ (a new module, e.g. stale_pulls.ts, beside stale_asks.ts), its scheduler hook, tests. Stay out of src/http/mcp.ts, src/contract/openapi.ts and docs/DESIGN.md.