Generalized plan → implement → test → submit loop

[JSONbored]

Problem: The execution loop being built under Miner Wave 3 is scoped to gittensory's own CI/coverage/gate conventions. Making it work against an arbitrary repo's own CI is separate work.

Area: AMS / Miner

Proposal: Build on Wave 3's loop mechanics (discover → claim → code → submit → repeat plus its safety governor) rather than duplicating them, replacing every gittensory-specific CI/coverage assumption with the stack information from #4785, so the loop validates its own work against whatever CI the target repo actually has.

Deliverables:

• An execution loop that runs a full plan/implement/test/submit cycle against an arbitrary repo's own CI signal, using Wave 3's mechanics as its foundation.

Acceptance criteria:

• Completes a full cycle against at least one non-gittensory test repo, passing that repo's own CI.
• Does not assume gittensory's own coverage tooling or gate conventions anywhere in the path.

Test scenarios:

• End-to-end run against a test repo with a different CI setup than gittensory's own.

Boundaries:

• Blocked on Stack auto-detection #4785 and on Epic: Miner Wave 3.5 — Wire the autonomous loop end-to-end #5130 (Miner Wave 3.5 epic — a post-Wave-3 audit found the loop mechanics this issue assumes exist are not actually wired end-to-end yet; Epic: Miner Wave 3.5 — Wire the autonomous loop end-to-end #5130 closes that gap).

---

Part of #4778.

[linear-code]

JSO-3458