2026-10-17 — The landing's push fence renews with the tip's own term, and a lane it stops on another person's hold is handed back as stuck (facilitator-on-delegation, drain-many-accounts): the check before the push is the land fence's own act, a fetch and a live renewal of this person's reservation from this copy, made for every run that holds a reservation, an intent's included, since a duplicate pull request is as wrong there; it renews with the tip's own term (renewalTerm) rather than the fence's day, so the push neither cuts nor stretches the lease the arming later sets; its refusals are the fence's, contention, worded for the push; a hold now another person's, or released as finished on origin's default branch, is a refusal that cannot change, so the drain hands the lane back at once through the stuck lane's route, kind stuck, with no new hand-back kind; and the drain's renewal of the lane in progress reads the move's own view, renews only a lane not parked at land (the merged-lane finish renews those), and names a renewal that failed or found the hold another's in the move's next step (grounds: lease keep-alives as Chubby and etcd keep them, fencing before a write, and one canonical primitive for the stuck route; spc-2610161044461448 step 7; iss-2610161015393523)

Frontmatter

.abcd/work/decisions/dcn-2610170028405029-the-landing-s-push-fence-renews-with-the.md
open on GitHub ↗ · commit history ↗

mentions4

• dcn-26101701165827252026-10-17 — A land fence that cannot read the reservation from origin is a wait by design, never a refusal a drain counts toward a stuck lane (facilitator-on-delegation, drain-many-accounts; refines dcn-2610170005357588 and dcn-2610170028405029): at the push and at the arming alike, any fetch the fence makes that fails is never logged as the lane's refused, whatever git says, since the drain's own read of origin at every move already waits on an origin it cannot read and gives up on one that stays unread through the outage schedule; a failure that reads as a lost network (implement.IsNetworkFailure) also waits on the shared outage probe, as the push's own failure does, and any other failure does not, because the network probe proves only the network back (grounds: one bound for an unreadable origin, the drain's, rather than a second one at the lane; the push's netFailure as the existing shape; review of spc-2610161044461448 steps 5 and 7)
• dcn-26101701264054122026-10-17 — A drain move renews only a lane its run still has in progress (facilitator-on-delegation, drain-many-accounts; refines dcn-2610170028405029): a lane the run has handed back, by its own step or as stuck, is renewed by no move, even while the drain has not yet routed it because its pace window is paused, so a reservation whose release origin refused is left to lapse or to the routing's release rather than kept alive by every move; a lane parked at land stays the merged-lane finish's to renew (grounds: a lease keep-alive belongs to work still being done, as Chubby and etcd sessions end with their client; review of spc-2610161044461448 step 7)
• iss-2610161015393523A drain's in-progress lane is renewed only when its own step or receipt runs, so if the host pauses the lane for more than the two-hour default lease another account takes the reservation over five minutes after expiry and works the same issue; the land fence runs only at arming, after the push and the pull request, so the duplicate becomes a public pull request.
• spc-2610161044461448drain-many-accounts