Landing

A change has landed when the integration ref holds it, however it got there, so landing is read from git and never from the text of a bash command.

How a landing is decided

A landing is read from git ref state, never from bash text. When a watched ref moves, a worker’s branch counts as landed by ancestry, equal patch ids, or equal content of every path it touched, and land counts as the act. anchorloop_stage landed (sha, ref, task) records an owner’s notice and checks it the same way.

A loop that lists an observation watches its own repo’s integration ref even with no linked child. A branch this session pushed (git shows the remote-tracking ref moved by its own push) is a car whose landing counts for the unit its name names by ticket. A push is found through global options with quoted values (git -c 'credential.helper=!glab auth git-credential' push, -C "a b", --git-dir /x) or a path to git, and a branch the command names as a refspec destination (git push origin agent/mp-x, HEAD:refs/heads/x, src:dst) is this session’s car even from a checkout on another branch; --dry-run, -n, git stash push, and a branch the command does not name are not.