chore(quality): advance registry activation seam

2026-08-01 10:06:09 -05:00
parent 9e1a7a44b7
commit 83d2ecb224
2 changed files with 6 additions and 1 deletions
@@ -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.