From 3139cb43646556540b36f63def25dfae08158f0c Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 1 Sep 2026 07:35:57 -0500 Subject: [PATCH] ci(core-ref): pin core at MODULE_API 1.9.0, unbreaking frozen-manifest The pin was `963d734` -- website `main` at the Teams cutover, MODULE_API **1.6.0**. That core has no `ceilings.js`, no `registerEventTriggers` and no `registerAudiences`, so this module has failed to load into it since Phase 11a added the first of those calls, and `frozen-manifest` has been red on every engagement PR since. The last green run was #39 (`6a276a7`, Phase 10's protocol-5 ingest), which added no `register*` call and so still loaded. The red X was never about the PR in front of it. This is the bump the org lead scheduled for the moment website#178 landed; it should have ridden in Module-uo#24 and did not. New pin: `52eac24` -- website `edge` carrying MODULE_API 1.9.0 (`registerEngagementSeeds`) and the Phase 11b core fixes (website#179). `routes.manifest.json` is unchanged and is NOT regenerated here: this phase's work added triggers, bodies and rules, and not one route. The job's own check confirms it -- 73 routes, all documented. Reproduced locally the way the job does it: core at the new sha, manifest without the module, module installed with `npm ci --omit=dev`, manifest with it, then `frozenManifest.js --check`. The module registers cleanly (26 triggers, 3 audiences) and the check passes. `check:imports` and `check:bundle` clean. Reverts to a `main` sha at the Phase 13 cutover. Co-Authored-By: Claude --- ci/core-ref.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ci/core-ref.json b/ci/core-ref.json index 3119e37..eed7298 100644 --- a/ci/core-ref.json +++ b/ci/core-ref.json @@ -1,6 +1,6 @@ { "$comment": "The core this module is proved against. MODULE_API.md §5.3: the frozen-manifest job clones RunicGateway/website at this exact ref, drops this module in as modules/uo and runs CORE's own routeManifest.js — nothing else can answer whether the URLs the module claims are the URLs it actually serves. Pinned rather than tracking `edge` on purpose: core moves for reasons that have nothing to do with this module, and a bump is then a deliberate commit saying which core the module was last proved against, instead of an unexplained red X on someone else's PR. Bump it, regenerate routes.manifest.json, and commit both together.", "repo": "https://gitea.whitlocktech.com/RunicGateway/website.git", - "ref": "963d734dcc09580a7d8bb676370b4faf9b8727b2", - "refName": "main @ the Teams cutover (website#161)" + "ref": "52eac24d170adbeb7cfb06486bc7512da1173ef9", + "refName": "edge @ MODULE_API 1.9.0, engagement Phase 11b (website#179)" }