Estate instrument
estate-deployed
Fetches a domain’s served bytes and finds the commit whose committed copy is byte-identical — pinning exactly which commit a deploy serves, without trusting a date stamp or a CDN header.
source: flashyos/tools/estate-deployed.mjs
node tools/estate-deployed.mjs (flashyos)It separates two findings every earlier report collapsed into "stale": a deploy behind its own default branch has stopped; a deploy serving a commit not on that branch was pointed somewhere else. Opposite fixes.
Edge cases — each one paid for once
Count the commits that changed the artefact, not every commit since
Counting all commits read "220 behind" twenty minutes after a good deploy.
Zero-behind is not current when the bytes already differ
The loudest case — a deploy serving another branch — reported healthy until the head comparison outranked the count.
refused is its own state
A 403 from a sandbox’s egress gateway is indistinguishable from a site refusing; reading it as the site once wrote up a healthy domain as having Deployment Protection.