From 50d5b1ad0aed8b950f74af84666448f372dc2bf1 Mon Sep 17 00:00:00 2001
From: "Jonathan D.A. Jewell" <6759885+hyperpolymath@users.noreply.github.com>
Date: Sat, 19 Sep 2026 20:09:24 +0000
Subject: [PATCH] fix(ci): re-pin the estate reusables to the last accepted
 standards ref
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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.
---
 .github/workflows/governance.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/workflows/governance.yml b/.github/workflows/governance.yml
index 8676eaf0..f6a9d9cb 100644
--- a/.github/workflows/governance.yml
+++ b/.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