Build the autonomous repeat/supervising loop (discover → attempt → manage → repeat)

[JSONbored]

Problem: loop-reentry.js and loop-closure.js — the real-IO pieces that "automatically re-invoke discovery on a resolved outcome" and "summarize a completed cycle before considering re-entry" — are both CLI-unreachable (confirmed via import-graph traced from bin/gittensory-miner.js). The Dockerfile's own CMD is ["doctor"], a one-shot batch command, and its own comment concedes the loop only runs "unless an operator wraps the container in their own supervising loop." Nothing anywhere autonomously repeats the discover → attempt → manage cycle today — the "repeat" step of the system's own stated end-goal (discover → analyze → plan → prepare → create → manage → repeat) does not exist.

Area: AMS / Miner

Proposal: Build a real supervising loop (a CLI command or long-running process mode) that: runs discovery, attempts a claimed item via the CLI dispatch from the sibling issue, waits for its outcome via the existing manage poll, invokes loop-closure then loop-reentry, and repeats — checking the governor (persisted per the sibling issue) and the existing kill-switch at every iteration boundary.

Deliverables:

• A working autonomous loop entrypoint that runs unattended across multiple discover→attempt→close→reenter cycles.

Acceptance criteria:

• A dry-run loop completes at least 2 full cycles unattended, with no manual step between them.
• The existing kill-switch halts the loop within one iteration boundary when tripped mid-loop.
• The loop refuses to start (fails closed) if governor state (Persist governor cross-attempt state (rate-limit, budget, convergence, reputation, self-plagiarism) #5134) cannot be loaded — never silently falls back to a fresh/zeroed counter state.

Boundaries:

• Blocked on Wire CLI dispatch for the real attempt pipeline (attempt command) #5132 (CLI attempt dispatch), Build a real production runSlopAssessment implementation #5133 (production slop assessment), and Persist governor cross-attempt state (rate-limit, budget, convergence, reputation, self-plagiarism) #5134 (governor persistence) — do not wire unattended repetition before a single attempt cycle is real and durably governed. This is the core autonomous control-flow — the single most safety-critical piece of this whole milestone.

---

Part of #5130.

[linear-code]

JSO-3683