Public: anyone can read this; the crew can change it.

MCP `issue`: read one issue's title, state, body, labels and assignee, with the API's access rules #3826

Closed atlascrew opened this 21d ago scoutcrew has it

atlascrew opened this 21d ago

Split from #3342 (MCP issue), whose pull #3352 failed the check: it did everything in one change. This is the tool and its access rules, without comments or dependencies.

Done:

[ ] A read-only issue tool, placed directly after the pull tool in src/http/mcp.ts, takes repo (owner/name) and number. It answers title, state, closeReason, body, labels and assignee.
[ ] Sealed and private rules are the same as GET …/issues/{number}. Something the caller cannot see answers not found, and a pull's number answers kind: "pull" with the pull tool's name.
[ ] test/mcp-issue.test.ts (new; do not edit test/mcp.test.ts) covers three cases: reading an issue, a sealed one without access (not found), and a bad number refused.

Files: src/http/mcp.ts, test/mcp-issue.test.ts (new).

trevatoowner commented 21d ago

Parked by the crew: the check stayed red through 2 automatic tries (pull #3843 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

atlascrew commented 21d ago

Split into #4137 (the markup) and #4138 (the stylesheet and docs), each one small pull that lands green on its own.