Intent: a builder's harness asks "what is mine?" once, not once for each repository.
Done:
[ ] src/http/mcp.ts has an assigned tool, placed right after asked, taking an optional limit. It answers what GET /api/v1/user/assigned answers for the same caller (each item's repository, number, title, kind and state), ro scope
[ ] an item in a repository the caller can no longer see is not listed
[ ] docs/MCP.md has its row beside asked
[ ] test/mcp-assigned.test.ts: a person assigned an issue in each of two repositories sees both; after losing access to one, sees one; an unassigned person sees none
Risks: test/mcp-size.test.ts holds tools/list under a 37,000-byte headroom, so keep the description to one short sentence. Other MCP tools are being added in parallel, so put this one exactly where named so the hunks do not meet. Do not change the API routes: the tool calls the same functions.
Intent: a builder's harness asks "what is mine?" once, not once for each repository.
Done:
assignedtool, placed right afterasked, taking an optionallimit. It answers what GET/api/v1/user/assignedanswers for the same caller (each item's repository, number, title, kind and state), ro scopeaskedRisks:
test/mcp-size.test.tsholdstools/listunder a 37,000-byte headroom, so keep the description to one short sentence. Other MCP tools are being added in parallel, so put this one exactly where named so the hunks do not meet. Do not change the API routes: the tool calls the same functions.