feat(mcp): register the 8 write-tools (open_pr/file_issue/apply_labels/etc.) that packages/loopover-mcp's own recommendedTools already promise

[JSONbored]

Context

src/mcp/server.ts:2231-2282 (the hosted/remote MCP server) registers 8 write-tools: loopover_open_pr, loopover_file_issue, loopover_apply_labels, loopover_post_eligibility_comment, loopover_create_branch, loopover_delete_branch, loopover_generate_tests, loopover_file_follow_up_issue. None of these appear among the 37 registerStdioTool(...) calls in packages/loopover-mcp/bin/loopover-mcp.js (the local, contributor-installed --stdio server) — even though that same file's AGENT_PROFILES["miner-auto-dev"].recommendedTools (bin/loopover-mcp.js:89-106) explicitly lists loopover_create_branch, loopover_open_pr, loopover_file_issue, loopover_apply_labels, loopover_post_eligibility_comment, loopover_delete_branch as tools that profile expects to be able to call. A contributor running the local MCP server with the miner-auto-dev profile currently cannot use any of these documented tools.

Requirements

• Add registerStdioTool(...) registrations for all 8 tools listed above to packages/loopover-mcp/bin/loopover-mcp.js, matching the input schema and behavior of their src/mcp/server.ts counterparts (read each remote tool's implementation for the exact REST/GraphQL calls it makes, and reuse the local server's existing HTTP-client/auth conventions rather than inventing a new one).
• loopover_generate_tests and loopover_file_follow_up_issue may have no local-server precedent yet for their underlying action — verify each has a real REST endpoint the local server can call before registering it; if one is missing, note that as a blocker in the PR rather than stubbing a fake tool.
• Do not change the remote server (src/mcp/server.ts) — this issue is scoped to bringing the local server up to parity.

Test Coverage Requirements

This repo's Codecov patch gate (99%+) applies to any src/** changes; packages/loopover-mcp is a separate package — check its own existing test conventions (packages/loopover-mcp/test/) and match them for the new tool registrations, including at least one test per new tool covering both success and a representative failure path.

Deliverables

• All 8 write-tools registered in packages/loopover-mcp/bin/loopover-mcp.js.
• Tests for each new tool registration.

Expected Outcome

A contributor running the local loopover-mcp server with the miner-auto-dev profile can actually call every tool that profile's own recommendedTools list promises.

Links & Resources

• src/mcp/server.ts:2231-2282 (remote tool implementations to mirror)
• packages/loopover-mcp/bin/loopover-mcp.js:89-106 (the profile that documents these as expected)

[linear-code]

JSO-4257