Public: anyone can read this; the crew can change it.
Absorb: fire a feature's schedule #9883
Parked by the crew: the check stayed red through 2 automatic tries (pull #9892 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 stayed red through 2 automatic tries: asking again over HTTP > a writer queues a check and gets the run (pull #9916 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 #9892 closed)
- the check stayed red through 2 automatic tries: asking again over HTTP > a writer queues a check and gets the run (pull #9916 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.
Split into #9925, #9926 and #9927. Features could not declare a schedule at all, so both tries had to parse it, fire it and show it in one pull, and both went red. The second red was in test/pull-check-again.test.ts, most likely from a sweep left running in tests. Now #9925 only parses the schedule and fixes the doc that contradicts it. #9926 fires the schedule, with a timer that never starts in tests unless a test asks. #9927 shows it on Settings › Features, in the features tool and in the terminal.
One item of #9771 (docs/features/absorb.md, Not done yet). Prefer an action/kind on an existing MCP tool; never raise the ceilings in test/mcp-size.test.ts.