Wire WIP-cap-aware batch claiming into the real CLI path

[JSONbored]

Problem: A WIP-cap-aware batch claimer already exists, built and tested — but the CLI's actual queue next still calls a naive, uncapped claim function directly. Caps also aren't configurable via the miner's own config file today.

Area: AMS / Miner

Proposal: Route queue next through the WIP-cap-aware claimer, and make the cap configurable via .gittensory-miner.yml.

Deliverables:

• queue next respects a configurable WIP cap.

Acceptance criteria:

• Setting a WIP cap in config and running queue next repeatedly stops claiming once the cap is reached.

[linear-code]

JSO-3510