From ea63ad019c5f221acd34dfff5accbe61bd7668c0 Mon Sep 17 00:00:00 2001 From: wtclaude Date: Wed, 9 Sep 2026 19:48:29 -0500 Subject: [PATCH] chore(ci): the core pin comes home to main (Phase 16b cutover) `ci/core-ref.json` pointed at a website `edge` sha for the length of the Event System window (org lead, 2026-09-04), because `api.registerEventActions` exists only from MODULE_API 1.10.0: under the old `main` pin the frozen-manifest job's `register()` threw and this module did not load at all, so the job would have been red by construction for eight phases while a real regression hid behind it. The cutover put 1.10.0 on `main` (website#199, 655fbf3f), so the pin returns to a `main` sha -- and this is the same move that turns the Integration kit green, since `checkCoreApi` asserts equality against whatever core this pin names. `routes.manifest.json` needed NO regeneration. The frozen-manifest job's own steps were run against this exact ref -- core's manifest alone, the module installed, core's manifest again, then `frozenManifest.js --check` -- and it answered `routes.manifest.json is current, 73 routes, all documented`. So the file's own "commit both together" instruction had nothing to pair with this time. website's `main` and `edge` are the identical tree (930422ff), which is why the measurement taken on the branch holds for the merge. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_016wDDVXWMDz82WqE1i969r4 --- ci/core-ref.json | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ci/core-ref.json b/ci/core-ref.json index d71a373..2afa537 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. **It points at `edge` for the length of the Event System window** (org lead, 2026-09-04), and that is the one line here a reader should not tidy back. This module registers event actions from EVENTS_PLAN.md Phase 9, and `api.registerEventActions` exists only from MODULE_API 1.10.0 -- under the previous `main` pin `register()` throws and the module does not load at all, so the job would be red by construction for eight phases and would prove nothing while a real regression hid behind it. Phase 16's cutover re-pins it to `main`, which is the same commit that turns the Integration kit green again.", + "$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 a branch 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. **It pointed at `edge` for the length of the Event System window** (org lead, 2026-09-04), and this commit ends that: `api.registerEventActions` exists only from MODULE_API 1.10.0, so under the previous `main` pin `register()` threw and the module did not load at all — the job would have been red by construction for eight phases and would have proved nothing while a real regression hid behind it. The Phase 16b cutover put 1.10.0 on `main`, so the pin comes home, and this is the same move that turns the Integration kit green again. **routes.manifest.json needed NO regeneration**: the job's own steps were run against this exact ref and answered `routes.manifest.json is current — 73 routes, all documented`, so the \"commit both together\" instruction above had nothing to pair with this time.", "repo": "https://gitea.whitlocktech.com/RunicGateway/website.git", - "ref": "d4516739b43de5cb83b8f0333f8f966280a5632f", - "refName": "edge @ MODULE_API 1.10.0, the event module contract (website#189, #190)" + "ref": "655fbf3f69a6a1fd650ecbc81afd6cf9c2ad9f66", + "refName": "main @ MODULE_API 1.10.0, the Event System cutover (website#199)" }