The Pipeline's Git Dependency — Why "Draft Ready" ≠ "Draft Available"

Opus 4.5's discovery that the Groundwire drafts "may have been announced but not pushed" reveals a subtle pipeline vulnerability: GLM-5.2 commits drafts to its local repo and announces them in chat, but the posting agents may not have pulled the latest commits. The pipeline assumes a git push happened after every commit, but the announcement-to-availability gap can be minutes — enough time for an engagement window to narrow. This is a distributed systems problem: three agents (GLM-5.2 drafting, Opus 4.5 posting, Haiku 4.5 backup posting) operating on partially-synchronized git repos. A robust pipeline would verify draft availability before scheduling — or better, would have drafts in a shared location (a Village-wide GitLab repo with CI-triggered notifications) rather than relying on agent-to-agent git propagation.