From 83d2ecb2243f1b0987ef2bc14de47f444285a684 Mon Sep 17 00:00:00 2001 From: f10-coder Date: Sat, 1 Aug 2026 10:06:09 -0500 Subject: [PATCH] chore(quality): advance registry activation seam --- docs/scratchpads/1029-rm-02-gate-registry.md | 5 +++++ gates/gates.manifest.json | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/scratchpads/1029-rm-02-gate-registry.md b/docs/scratchpads/1029-rm-02-gate-registry.md index 631ae905..65f8462b 100644 --- a/docs/scratchpads/1029-rm-02-gate-registry.md +++ b/docs/scratchpads/1029-rm-02-gate-registry.md @@ -73,6 +73,11 @@ The queue guard's `get_state_from_status_json` runs `python3 - <<'PY'` while pro - Independent review documentation check pending rev-974 at the revised exact head. - Canonical documentation remains in-repository; no external publication requested. +## Rebase onto RM-61 + +- Rebasing `f9746b23` onto main `f4fd5967` completed mechanically with no conflicts. +- The first post-rebase `pnpm gate:verify` correctly failed because the old activation seam `f65e9ea6` made the newly merged pre-registry RM-61 commit part of prospective history even though that commit predates the registry. The activation commit was advanced to the new main parent `f4fd5967`, so own-tree provenance starts with this branch's first registry commit rather than demanding a manifest from an unactivated baseline commit. No gate case or acceptance rule was weakened. + ## Risks/blockers - Current queue guard intentionally has required-versus-actual deltas owned by RM-03. diff --git a/gates/gates.manifest.json b/gates/gates.manifest.json index 9b46170f..94b344b7 100644 --- a/gates/gates.manifest.json +++ b/gates/gates.manifest.json @@ -1,6 +1,6 @@ { "schemaVersion": 1, - "activationCommit": "f65e9ea656ec466e12640bf6ab5d46fe07ff160c", + "activationCommit": "f4fd5967fc5d4cbc72d680b199d88224aa855131", "gateRoots": ["gates"], "governingClaimFiles": ["docs/remediation/MISSION.md", "docs/remediation/GATE-CLAIMS.md"], "coverageBoundary": {