Problem
#7291 proposed migrating packages/loopover-mcp to TypeScript, phased by file size. This is Phase 3,
the last and by far largest piece: bin/loopover-mcp.js is 6,594 lines -- larger than
packages/loopover-miner's entire remaining migration (#7290) combined.
Proposal
Convert bin/loopover-mcp.js from .js to .ts, building on Phase 1 (#7328) and Phase 2 (#7329).
Explicitly not decided here: whether a straight 1:1 file rename is even the right move for a
file this size, versus splitting it into multiple .ts modules as part of the conversion (the
file almost certainly has natural seams -- command parsing, tool definitions, request handling,
etc. -- worth identifying before committing to a single massive diff). That's a real design
decision for whoever picks this up to make explicitly, not something to assume either way in
advance. If a split is chosen, treat each resulting module as its own sub-batch rather than landing
the whole thing in one PR -- the same one-shot-gate risk that motivated phasing #7290/#7291 in the
first place applies doubly here given the file's size.
Deliverables
Test Coverage Requirements
No behavior change from this migration alone. Existing tests must continue to pass unmodified.
Expected Outcome
packages/loopover-mcp is 100% real, compiler-verified TypeScript, closing out #7291.
Links & Resources
Problem
#7291 proposed migrating packages/loopover-mcp to TypeScript, phased by file size. This is Phase 3,
the last and by far largest piece:
bin/loopover-mcp.jsis 6,594 lines -- larger thanpackages/loopover-miner's entire remaining migration (#7290) combined.Proposal
Convert
bin/loopover-mcp.jsfrom.jsto.ts, building on Phase 1 (#7328) and Phase 2 (#7329).Explicitly not decided here: whether a straight 1:1 file rename is even the right move for a
file this size, versus splitting it into multiple
.tsmodules as part of the conversion (thefile almost certainly has natural seams -- command parsing, tool definitions, request handling,
etc. -- worth identifying before committing to a single massive diff). That's a real design
decision for whoever picks this up to make explicitly, not something to assume either way in
advance. If a split is chosen, treat each resulting module as its own sub-batch rather than landing
the whole thing in one PR -- the same one-shot-gate risk that motivated phasing #7290/#7291 in the
first place applies doubly here given the file's size.
Deliverables
bin/loopover-mcp.js(or its resulting modules) converted from.jsto.tsloopover-mcp --help/--versionand every realcommand behave unchanged)
Test Coverage Requirements
No behavior change from this migration alone. Existing tests must continue to pass unmodified.
Expected Outcome
packages/loopover-mcpis 100% real, compiler-verified TypeScript, closing out #7291.Links & Resources