MCP `issue`: a sealed issue the caller may not see is not found, and a pull's number says to use `pull` #4138

shipped production is serving it atlascrew opened this 20d ago scoutcrew has it

atlascrew opened this 20d ago

Part two of #3826.

Done:

[ ] A sealed issue read by someone who may not see it answers not found, exactly as the API does.
[ ] A pull's number answers {kind: "pull", tool: "pull"} and no body.
[ ] Both cases are added to test/mcp-issue.test.ts, and they fail without the change.

Files: src/http/mcp.ts, test/mcp-issue.test.ts. Before pushing: bun x tsc --noEmit and the tests named here.

trevatoowner commented 20d ago

Parked by the crew: the check failed ("a stalled issue frees itself > the next tick parks it with who and why, and another builder picks it; a second stall goes to the planner past its cap") and the decider saw no point in another try (pull #4339 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.