abcd land's single run, push and then queue, stops on its most common path. On 2026-10-15 it pushed feat/abcd-land at 2abcab16c (18:54:26Z), then in the same run read pull request #1020 and the forge still reported the old head 572cd8c0f, so the enqueue step stopped with 'wait for the forge to see the push' and nothing was armed. A re-run 12 seconds later armed it. Refusing to arm on a stale head is the safe failure and stays, but since a push that moves the head is the normal case, the person must usually run abcd land twice. Found by a real run; the fake forge answers at once, so no test could show it.

abcd land's single run, push and then queue, stops on its most common path. On 2026-10-15 it pushed feat/abcd-land at 2abcab16c (18:54:26Z), then in the same run read pull request #1020 and the forge still reported the old head 572cd8c0f, so the enqueue step stopped with 'wait for the forge to see the push' and nothing was armed. A re-run 12 seconds later armed it. Refusing to arm on a stale head is the safe failure and stays, but since a push that moves the head is the normal case, the person must usually run abcd land twice. Found by a real run; the fake forge answers at once, so no test could show it.

2026-10-16, a second occurrence: abcd land pushed feat/abcd-land at a5e880e4b at 23:43:55Z (UTC, the night of 2026-10-15) and, in the same run, read pull request #1020 at the old head 2abcab16c, so it stopped; the re-run 14 seconds later saw the new head and left the existing arming in place. Two of two head-moving runs have now hit the lag.