From 0449d67a7f00385fb8b2d9e267d2b91ec82737d7 Mon Sep 17 00:00:00 2001 From: Levi Neuwirth Date: Mon, 10 Aug 2026 00:02:31 +0200 Subject: [PATCH] docs: warn that this lane U4/U5 must become U6/U7 on rebase gate-protocol-build independently defines its own U4 and U5 --- a macOS lua54 PTY-resize failure and a Ctrl-C-as-SIGINT failure --- and it merges first, so on main those ids are taken. A rebase that resolves the textual conflict without renumbering leaves two different incidents sharing an id, which is precisely the failure this file matching rule exists to prevent. The registry authority rests on ids meaning one thing. The warning enumerates all four sites rather than saying "renumber the rows", because one of them is a prose cross-reference inside U5 relation-to-U4 field and another is in active-work.md --- both easy to miss when the conflict presenting itself is two adjacent headings. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_016bqGA6s9tTUFzYpbeW3tai --- docs/ci-red-signatures.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/ci-red-signatures.md b/docs/ci-red-signatures.md index 0f5cc34..51f642d 100644 --- a/docs/ci-red-signatures.md +++ b/docs/ci-red-signatures.md @@ -630,6 +630,22 @@ it again here by piping a sweep through `grep`. The fix is mechanical: stream. A signature that is cheap to capture and impossible to reconstruct should never be traded for terminal brevity. +> [!IMPORTANT] +> **RENUMBER THESE TO U6 AND U7 WHEN THIS LANE REBASES.** The +> `gate-protocol-build` lane independently defines its own **U4** and +> **U5** (a macOS `lua54` PTY-resize failure and a Ctrl-C-as-`SIGINT` +> failure), and it merges **first** — so on `main` those ids are taken. +> +> A rebase that resolves the textual conflict without renumbering leaves +> **two different incidents sharing an id**, which is exactly the +> failure this file's matching rule exists to prevent. +> +> **Every site, so none is missed:** +> 1. this heading (`### U4 …`) +> 2. `### U5 …` below +> 3. U5's **relation to U4** field, which names it in prose +> 4. `docs/active-work.md` — "Recorded as **U5**" in the worker lane entry + ### U4 — two wall-clock budget tests fail together in one `lib-crdt` step Recorded during worker identity Stage 1 review round 2, 2026-08-09, in