Part of the '-coverage' bolt-on consolidation epic (#8574 — non-closing reference).
test/unit/miner-cli-json-error-coverage.test.ts (223 lines) is coverage-named but structurally different from the other bolt-ons: it spans the JSON-error paths of MANY miner CLI entrypoints (claim-ledger-cli, event-ledger-cli, governor-ledger-cli, loop-cli, manage-poll, plan-store-cli, queue CLIs, …) rather than duplicating one sibling suite. miner-cli-error.test.ts covers only the shared cli-error module, so a straight merge there is wrong.
Task — pick ONE:
Either way, verify zero coverage regression on the touched packages/loopover-miner/lib/*-cli.ts files with an unsharded npm run test:coverage before/after comparison.
Part of the '-coverage' bolt-on consolidation epic (#8574 — non-closing reference).
test/unit/miner-cli-json-error-coverage.test.ts(223 lines) is coverage-named but structurally different from the other bolt-ons: it spans the JSON-error paths of MANY miner CLI entrypoints (claim-ledger-cli,event-ledger-cli,governor-ledger-cli,loop-cli,manage-poll,plan-store-cli, queue CLIs, …) rather than duplicating one sibling suite.miner-cli-error.test.tscovers only the sharedcli-errormodule, so a straight merge there is wrong.Task — pick ONE:
miner-cli-json-error-paths.test.ts) so it stops reading as a coverage-filler file, and retitle generic case names.miner-attempt-cli.test.ts-style siblings), then delete the file.Either way, verify zero coverage regression on the touched
packages/loopover-miner/lib/*-cli.tsfiles with an unshardednpm run test:coveragebefore/after comparison.