Problem
#7290 proposed migrating packages/loopover-miner/lib/** to TypeScript, phased for gate safety.
Phase 1 (#7299) landed the tsc build pipeline. This issue is batch 3.4 of 4 (Phase 3, convert last in this phase -- these import many lib/*-cli.js files from batches 3.1-3.3 above): convert this batch's
files, using the same in-place-emit pattern Phase 1 already wired up.
Proposal
Convert these files (and their hand-maintained .d.ts siblings) from .js to real .ts:
bin/loopover-miner.js
bin/loopover-miner-mcp.js
No tsconfig.json changes are needed -- its existing include glob (bin//*.ts, lib//*.ts)
picks up newly-converted files automatically.
Deliverables
Test Coverage Requirements
No behavior change from this migration alone. Existing tests for these modules must continue to
pass unmodified (only import paths/build output shape might need adjustment).
Expected Outcome
These files are real, compiler-verified TypeScript with zero behavior change.
Links & Resources
Problem
#7290 proposed migrating packages/loopover-miner/lib/** to TypeScript, phased for gate safety.
Phase 1 (#7299) landed the tsc build pipeline. This issue is batch 3.4 of 4 (Phase 3, convert last in this phase -- these import many lib/*-cli.js files from batches 3.1-3.3 above): convert this batch's
files, using the same in-place-emit pattern Phase 1 already wired up.
Proposal
Convert these files (and their hand-maintained .d.ts siblings) from .js to real .ts:
bin/loopover-miner.jsbin/loopover-miner-mcp.jsNo tsconfig.json changes are needed -- its existing include glob (bin//*.ts, lib//*.ts)
picks up newly-converted files automatically.
Deliverables
Test Coverage Requirements
No behavior change from this migration alone. Existing tests for these modules must continue to
pass unmodified (only import paths/build output shape might need adjustment).
Expected Outcome
These files are real, compiler-verified TypeScript with zero behavior change.
Links & Resources