feat(mcp): register plan-DAG tools + local scorer (build_plan/plan_status/record_step_result/run_local_scorer/predict_gate) in packages/loopover-mcp

[JSONbored]

Context

src/mcp/server.ts registers loopover_run_local_scorer (line 2219), loopover_build_plan (2283), loopover_plan_status (2288), loopover_record_step_result (2293), and loopover_predict_gate (1875) on the remote/hosted MCP server. packages/loopover-mcp/bin/loopover-mcp.js's miner-auto-dev profile (recommendedTools, lines 91-94 and 98) lists all five as tools that profile expects to call, but none are registered as local stdio tools in that file — only the string literals exist in the recommendedTools array. A contributor relying on the local server for this profile cannot actually invoke any of them.

Requirements

• Add registerStdioTool(...) registrations for loopover_run_local_scorer, loopover_build_plan, loopover_plan_status, loopover_record_step_result, and loopover_predict_gate to packages/loopover-mcp/bin/loopover-mcp.js, matching the input schema and REST/GraphQL calls their src/mcp/server.ts counterparts already make.
• Reuse the local server's existing HTTP-client/auth conventions rather than inventing new ones.
• Do not change the remote server.

Test Coverage Requirements

Match packages/loopover-mcp's existing test conventions; at least one test per new tool covering success and a representative failure path.

Deliverables

• All 5 tools registered locally.
• Tests for each.

Expected Outcome

The local MCP server's miner-auto-dev profile can actually call every tool it claims to recommend.

Links & Resources

• src/mcp/server.ts:2219,2283,2288,2293,1875
• packages/loopover-mcp/bin/loopover-mcp.js:91-94,98

[linear-code]

JSO-4258