e-pin the estate reusables to the last accepted standards ref (#751)

fix(ci): re-pin the estate reusables to the last accepted standards ref

Pins at `4e6ffe55`-or-later are rejected by GitHub's dependency-lockfile
validation, so the
callers that used them could not parse: `conclusion=failure`, **0
jobs**, run name equal to the
file's path. `210f14e7` (2026-09-12T17:32:17Z) is the last ref whose
pins are accepted — measured by
pinning a caller at each candidate and dispatching it, not inferred.

This re-points the refs here to that ref. Behaviour is otherwise
unchanged; the lockfile in
`hyperpolymath/standards` is the thing that has to be regenerated before
a forward re-point is safe
again, and the estate's own applier
(`.github/workflows/apply-workflow-pins.yml`) is what should do
that re-pointing once it can run.

Author: hyperpolymath

.github/workflows/governance.yml

@@ -3,7 +3,7 @@
 # This workflow is managed by gh actions-lock.
 #
 # Standalone governance gate. Previously a thin caller of
-# `hyperpolymath/standards/.github/workflows/governance-reusable.yml@main`;
+# `hyperpolymath/standards/.github/workflows/governance-reusable.yml@210f14e753c80064ec1bcae72f1d654dd9b0e687`;
 # that cross-repo dependency (a) coupled this repo's CI to another repo's
 # moving `@main` and (b) startup-failed because a `concurrency:` block in a
 # reusable-workflow caller, when the reusable also declares concurrency on the