A session holding several push-ready branches drives each through preflight and landing by hand: on 2026-10-24 this session had four (docs/itd-82-landed-steps, fix/landing-marks-step-landed, fix/lapsed-release-hold, fix/name-ungated-tests), and with the rule relayed that day of one preflight per session at a time it started each preflight itself, watched for the 2-hour gate timeout (three runs timed out and had to be restarted by hand), ran 'abcd land' after each that passed, and kept the order in its own notes and wake-ups. No verb holds a session's queue of branches, so the chaining, the re-queue after a timeout and the landing all depend on the session staying alive and remembering.

Frontmatter

.abcd/work/issues/open/iss-2610241412028278-a-session-holding-several-push-ready.md
open on GitHub ↗ · commit history ↗

mentions2

• iss-2610171105560765abcd's wait and timeout defaults are fixed numbers, while what they wait for grows with the project. The load gate gives up after 30 minutes by default and after 2 hours in preflight, and go test kills a package at 10 minutes unless told otherwise. On 2026-10-17 two preflights here lost hours to these limits without any check failing: one waited the full 2 hours at the gate and gave up, and another was killed when one package took about ten minutes on a loaded machine. As a managed project gets more packages, tests and concurrent sessions, every fixed default is outgrown in turn, and each time a person or session must notice it and raise it by hand.
• itd-82`abcd drain` fixes the issues that need no decision, and hands the rest back by kind