refactor(gateway): check system-agent approval authority once at request start (#201998)

Problem: a delegated system-agent change re-checked the requesting run's authority after reconciliation, at proposal resolution, before and during apply (including a late auto-approve grant re-check), before a correction continued, and in a reconciliation poll. A change a human had already approved was silently not applied when its run ended first.

Fix: run authority is checked once at admission. The run-authority re-checks, the late grant re-check, the reconciliation poll, forceDenyIfRuntimeAuthorityClosed and isExecApprovalRuntimeActive are deleted. Kept: admission, session identity and pending-object ownership, proposal-hash reuse, the initial grant check, the one-correction bound, run-closure cancellation of pending approvals, and a user-Stop cancellation check at proposal resolution and at the apply boundary, so neither mode applies a change after the user stopped the run. A reload, worker removal or revoked source grant after approval applies to the next request; the approved apply finishes.

Known follow-up: the outer in-process tool caller still reports a rejection after an approved change applies (caller-authority chain, separate S1 PR).

Proof: source tier (ocx test). New regressions: a Full Access inference Stop applies nothing, and a human-approved change applies after its run ends. 367 tests across 33 system-agent and approval files; tsgo, test types, oxlint, format, lifetime-check, line-cap, session-identity, mock-export and max-lines ratchets; clean exact-head local ClawSweeper review; ocx build --dts plus packed install smoke on the head.

Co-authored-by: Ayaan Zaidi <hi@obviy.us>