check:published found one bundle stale again, one tick after the last publish —
regions-dashboard, 558,958 bytes served against 559,482 built. The PUBLISHED
copy was LARGER's inverse: smaller, which is the direction that warrants a look
before overwriting, since a shrinking bundle can mean something was lost.
Diffed them rather than assuming. The sole difference is a
`@media (prefers-reduced-motion: reduce)` block present locally and absent live
— an accessibility rule honouring readers whose OS asks for less animation.
A token-set comparison found ZERO strings present live and missing locally, so
this publish is strictly additive: nothing is lost, one accessibility feature is
gained.
Nobody had pushed to source since the last publish, so this was not unpublished
work waiting on a merge — it was work that reached main and never got published,
the continuous-drift gap recorded in
OPS-PUBLISH-DRIFT-IS-CONTINUOUS-AND-NOTHING-PROMPTS-A-PUBLISH, demonstrated a
second time.
Verified before push: 24 bundles, 22 manifest bundles resolving, 57 leaves with
zero unresolved script srcs, zero bundles carrying the old broken asset path,
tree settled, diff scoped to app/doxa-maps.
b2a19e1d39