The gate cannot lock itself out (#7790)

On 2026-11-01 a bug in the live gate could not be fixed through the gate, and landing stopped for about 4.7 days.

- the pull's Files step: a "Land past the gate" form (a labelled reason field and a danger button, plain post, no script needed); - MCP: land_past_gate { repo, number, reason, dryRun: false } (planned unless dryRun is false; the plan checks who, the stop and the reason, as the apply does); - the terminal: L on the pull screen asks the reason, shows it back in a confirm, then lands. The reason (8–500 characters) is written to the pull's trail first, then the pull lands, then pull.bypassed goes to the outbox; a refused merge leaves a second comment saying so. Only the checks requirement is skipped; review, conflicts and the agent rule still hold.

Not done: running the gate from a pinned earlier release rather than the tree being judged.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs