Wire CLI dispatch for the real attempt pipeline (attempt command)

[JSONbored]

Problem: bin/gittensory-miner.js's full command table (init/status/doctor/manage/queue/claim/ledger/plan/governor/feasibility/hooks/state/discover) has no attempt or run branch. runMinerAttempt (packages/gittensory-miner/lib/attempt-runner.js:96, the real create→review→gate→submit orchestrator from #2337) is unreachable from the CLI entirely — git grep runMinerAttempt on main returns only its own definition and test/unit/miner-attempt-runner.test.ts.

Area: AMS / Miner

Proposal: Add a real CLI subcommand (e.g. gittensory-miner attempt <target>) dispatching to runMinerAttempt, wiring its AttemptDeps from real config/state — including the driver from #5131 and the slop-assessment implementation from the sibling issue below.

Deliverables:

• A working CLI subcommand that runs a real attempt end to end (create → review → gate → submit) against a real target, dry-run by default.

Acceptance criteria:

• Running the command against a real target in dry-run produces a real AttemptResult (not a test double).
• Dry-run remains the default per the project's existing safety posture (maintainer: dry-run-by-default enforcement #2342).
• The command respects the governor chokepoint (maintainer: wire the fail-closed Governor chokepoint before every write action #2340) exactly as runMinerAttempt's own tests already verify.

Boundaries:

• Blocked on Build production CodingAgentDriver construction + wire into the create phase #5131 (driver construction) and on the slop-assessment issue below — dispatching without real implementations behind it just moves the gap, it doesn't close it.

---

Part of #5130.

[linear-code]

JSO-3680

[JSONbored]

Splitting this: the CLI-arg-parsing, ledger wiring (claim/event/attempt-log/governor), live-issue-snapshot fetch, local-write execution, mode resolution, and worktree allocation are all buildable now and don't depend on anything unbuilt. But runMinerAttempt requires loopInput.reviewContext: SelfReviewContext — filed #5145 for that fetcher, since stubbing it with empty/default data would produce a self-review pass that looks real but checks nothing. Landing the ready parts first; this issue stays open until #5145 lands and the CLI can actually call runMinerAttempt with a real context.