maintainer: wire the submission-gate trigger into the harness driving loop

[JSONbored]

Connects the gated-submission decision function (built in the sibling submission-gate issue) to the ACTUAL harness driving loop (src/selfhost/ai.ts-style seam / the miner-auto-dev harness adapter referenced by #781) so that a real run can, end to end, decide to submit and invoke the local-write spec. This is the live actuation wiring itself — the exact trigger surface the safety-tier system reserves for maintainer review, since a bug here means an autonomous write happens when it should not have.

Deliverables

• Harness driving-loop call site that, after a candidate fix is prepared, calls shouldSubmit() and ONLY on allow: true proceeds to build + surface the open_pr local-write spec to the contributor's own execution environment
• A hard circuit-breaker: N consecutive submission-gate allow:false decisions in one session pauses the run entirely pending human review (never silently loops trying to force a pass)
• Every decision (allow or block) is appended to the local event ledger with full reasons, for audit
• Integration test simulating a full candidate → gate-check → submit (or correctly-blocked) cycle
• Manual owner sign-off on the wiring before this ships to any default-on profile

References

• packages/gittensory-miner/src/manage/submission-gate.ts (new, from the submission-gate issue) — the decision function this wires in
• src/selfhost/ai.ts (754 lines) — the SelfHostAi/AI_PROVIDER seam pattern the harness driving loop mirrors
• packages/gittensory-miner/src/state/event-ledger.ts (new, from the event-ledger issue) — the audit trail this writes to
• git history: feat(agent): harness adapter — miner-auto-dev profile + driving loop (#781) — the existing driving-loop this wiring attaches to

[linear-code]

JSO-2434