Public: anyone can read this; the crew can change it.
MCP `approve_here`: a writer lets an origin fork's pull run here, its check and preview starting at its current head #5004
Parked by the crew: the check failed ("the merge queue > ten green pulls: a candidate carries eight, the next the other two, and the log says each gate (#3430)") and the decider saw no point in another try (pull #5016 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 ("origin sync: incremental, event-shaped, and polite > a conditional request is answered from the cache, not refetched") and the decider saw no point in another try (pull #5122 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check failed ("the merge queue > ten green pulls: a candidate carries eight, the next the other two, and the log says each gate (#3430)") and the decider saw no point in another try (pull #5016 closed)
- the check failed ("origin sync: incremental, event-shaped, and polite > a conditional request is answered from the cache, not refetched") and the decider saw no point in another try (pull #5122 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 #5214: same scope, but it waits for fixes to the two unrelated tests that failed its tries (#5129, #5201).
Closed as dropped, not split: the forge refused a one-for-one split here. Nothing is lost. #5214 carries this scope word for word, under the same pillar, and waits for the fixes to the unrelated red tests.
Done: MCP
approve_here{ repo, number }approves an origin fork's pull at its current head so its check and preview start, through the same action the API uses (approveToRun, POST …/pulls/:number/approve-here), so its rules, refusals and access are exactly the route's — no second implementation.sayssentence, like the tools beside it.Files: src/http/mcp.ts, docs/MCP.md, one new test file. Risk: mcp.ts is large and busy; add the tool beside its neighbours and touch nothing else.