backlog(B-0545): B-0498 ID collision — renumber sweep (Riven cursor-terminal → next ID)

[AceHack]

Summary

• Real ID collision caught by copilot-pull-request-reviewer on PR shard(tick): 2217Z — arm-sweep continued: #3601 (merged), #3603 (armed) #3604 (tick shard 2217Z thread):
  • docs/backlog/P1/B-0498-riven-cursor-terminal-*-2026-05-15.md (from merged feat(riven): Riven cursor-terminal loop scaffold [B-0498] (decomposed) #3603)
  • docs/backlog/P2/B-0498-substrate-evolution-algebra-*-2026-05-14.md (pre-existing)
• Per b0451_per_collision_renumber_procedure: first-merged-wins → P2 (2026-05-14) keeps B-0498; P1 (2026-05-15) renumbers to next free (B-0546).
• This row IS the filed-correction surface; implementation in a follow-up PR.
• P2 priority — collision exists but no active break; address within 1-2 weeks.

Test plan

• Verified via git ls-tree origin/main -- docs/backlog/ — both files exist
• Rule discipline confirmed via memory file lookup
• B-0545 ID allocated via on-disk + in-flight check (B-0543/0544 in research(B-0543/B-0544): QG isomorphism proof-path + Step 1 formalization + Adinkra/Cayley-Dickson extensions (Riven + Otto) #3614; B-0545 free)
• Implementation PR (renumber sweep) to follow

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b0bcac6436

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Replace wildcard destination in rename command

The documented sweep command uses a wildcard in the destination (git mv ... B-0546-riven-*), which is unsafe in Bash because unmatched destination globs are passed literally; running this as written can rename the file to a path containing a * character instead of the intended concrete filename. In the renumber workflow, that would leave the backlog row under an invalid/unexpected name and likely break follow-up references/indexing, so the command should name the exact target file (or compute it programmatically) rather than using a wildcard destination.

Useful? React with 👍 / 👎.

[Copilot]

Pull request overview

Adds a new P2 backlog row (B-0545) to document and track the discovered B-0498 ID collision, and to define the intended renumber target/sweep scope for a follow-up implementation PR.

Changes:

• Introduces backlog row B-0545 describing the B-0498 collision (P1 vs P2 rows) and the “first-merged-wins” renumber procedure reference.
• Captures proposed renumber target (B-0546) and a checklist of cross-reference updates to perform in the implementation sweep.
• Records rationale for P2 priority and scope-bounds (filed-correction surface only).

Comments suppressed due to low confidence (3)

docs/backlog/P2/B-0545-b0498-collision-renumber-sweep-2026-05-15.md:47

• P1: The example command gh pr list --search "B-NNNN" --state all won’t actually enumerate the in-flight IDs you list below (it searches for the literal string B-NNNN). Use a concrete search term/pattern that matches real PR titles (e.g., the specific IDs, or a prefix like B-054), or reword this to describe the check without giving a non-functional command.

## Next free ID

At time of filing (2026-05-15T22:55Z), `git ls-tree origin/main` plus `gh pr list --search "B-NNNN" --state all` shows:

- B-0542 last on main
- B-0543/B-0544 taken in flight (PR #3614, OPEN)
- B-0545 — THIS ROW, claimed
- **B-0546** — next free for the renumber target

docs/backlog/P2/B-0545-b0498-collision-renumber-sweep-2026-05-15.md:70

• P1: tick-shards-are-immutable is referenced as if it’s a named rule, but there’s no such rule/doc in the repo; this reads like a dead xref. Consider linking to an existing authority that states shard immutability (e.g., docs/hygiene-history/ticks/README.md, which describes shards as immutable events) or rename this to the actual rule/document name.

- Update `id:` frontmatter inside the moved file
- Update any `depends_on:` / `composes_with:` fields in OTHER backlog rows that pointed at B-0498 in the Riven sense
- Update tick shards that QUOTE the Riven B-0498: PER `tick-shards-are-immutable` discipline, do NOT in-place-edit; instead, append a correction note in a new shard OR add a glossary entry in the renumber row
- Update any tools/scripts: rename references via `grep -rln "B-0498-riven\|B-0498.*riven" memory/ docs/ .claude/ tools/`

docs/backlog/P2/B-0545-b0498-collision-renumber-sweep-2026-05-15.md:88

• P2: In the “Composes with” section, claim-acquire-before-worktree-work.md and refresh-before-decide.md are referenced as bare filenames, but the canonical paths are under .claude/rules/…. Consider linking them with their full repo paths (as other backlog rows do) so readers can navigate unambiguously.

## Composes with

- The `b0451_per_collision_renumber_procedure` memory (2026-05-14) — same shape, second instance
- The `claim-acquire-before-worktree-work.md` rule's "ID allocation discipline" section — this collision is an instance the discipline is meant to prevent
- `refresh-before-decide.md` invariant at ID-allocation scope — both surfaces (merged + in-flight) must be checked; the Riven-cursor row at 2026-05-15 likely skipped the on-disk B-0498 P2 check