feat(mcp): read complete native issue handoffs #141
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/native-handoff-reads-20261018"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A fresh native MCP session could list issue titles but could not read a handoff body or its follow-up comments. This adds
get_issueandlist_issue_comments, and giveslist_issuesexplicit native continuation so discovery can go beyond the first page.Issue and comment bodies are complete, with native identity and observation provenance. Comments follow Core's unpaginated ordinary-comment contract; they do not represent the full issue timeline. Existing caller permissions apply, malformed upstream responses produce redacted errors, and the public four-tool catalog is unchanged.
Validation: normal and optimized Python contracts, independent malformed-wire and native-pagination checks, and the full native end-to-end gate. A fresh read-scoped session found a private handoff after the first page, read its body and 35 comments, and exercised permission and PR-refusal cases. Independent source review and both native pull-request workflows passed on
d0029ba661032b1de0570a8cdb3ef391001f3365; deployment is a separate step.WIP: feat(mcp): read complete native issue handoffsto feat(mcp): read complete native issue handoffs