Wire already-built, already-tested modules into the CLI

[JSONbored]

Problem: Several modules are fully built and fully unit-tested but have zero callers outside their own test files: the inter-miner claim-conflict adjudicator, the WIP-cap-aware batch claimer, and the anonymized telemetry batch-builder. Their real-world robustness is unverified because nothing actually invokes them.

Area: AMS / Miner

Proposal: Wire each of these three modules into the CLI paths they were clearly built for (this issue is about wiring; the specific end-user-facing behavior for claim-conflict resolution and WIP-cap batching is covered by their own feature-completeness issues below — this issue is the shared prerequisite of actually calling the code that already exists).

Deliverables:

• Real call sites for all three modules, replacing whatever naive/absent logic currently sits in their place.

Acceptance criteria:

• Each module is exercised by a real CLI command, not just its own isolated unit test.

Boundaries:

• Don't change the modules' own logic — they're already correct and tested; this issue is purely about connecting them.

Scope note: this issue is limited to wiring the WIP-cap-aware batch claimer and the anonymized telemetry batch-builder into real CLI call sites. Wiring the inter-miner claim-conflict adjudicator is explicitly out of scope here -- connecting it to a live call site would mean the autonomous loop starts acting on race-resolution decisions (who wins a claim conflict) with no human review, and that stays maintainer-only per the contributor-vs-maintainer safety framework regardless of the module's own test coverage.

[linear-code]

JSO-3493