refactor(rebrand): flip SEA-NNN issue refs to RIG-NNN across the tree (RIG-2804) - #716
Open
rigel-mintaka wants to merge 1 commit into
Open
refactor(rebrand): flip SEA-NNN issue refs to RIG-NNN across the tree (RIG-2804)#716rigel-mintaka wants to merge 1 commit into
rigel-mintaka wants to merge 1 commit into
Conversation
… (RIG-2804) Number-preserving `SEA-<n>` → `RIG-<n>` sweep over the tracked compass tree, matching the settled orion #1829 (RIG-2569) pattern. The Linear team-key rename preserved issue numbers 1:1 (SEA-1512 == RIG-1512), so this is a pure token flip to match the live team name — no renumbering, no behavior change. Mechanical guarantee. Applied by a one-shot codemod matching `\bSEA-(\d+)\b`, then verified per file: for 344 of the 345 changed files, re-deriving the flip from the `main` version yields byte-identical output — i.e. the only change is `SEA-<n>→RIG-<n>`. 1515 refs across 345 files. The one exception is `docs/designs/DECISIONS.md`, which additionally flips 4 lowercase anchor-link slugs (`#...sea-1721...` → `#...rig-1721...`, likewise 1722/1723/1364). Those links target design-record headings whose text this flip renamed (`### A1 — SEA-1721:` → `### A1 — RIG-1721:`), so the heading's derived GitHub anchor moved to `rig-`; the link has to follow or it dangles. The design-ledger gate validates exactly these ledger→record anchors and is what surfaced it. Verified: DECISIONS.md deviates from the pure token flip on exactly those 4 lines and nothing else. Deliberately left untouched (the codemod does not match them): - lowercase `sea-<n>` branch-slug artifacts (e.g. `compass-sea-1243-...`) — historical git branch names quoted in design records; the team rename does not rewrite the past. - `SEA-nnn` / `SEA-NNN` / `SEA-N` prose placeholders — the digit class rejects letters, so these stay as generic "some issue number" prose. No carve-outs needed. orion #1829's three (issue-owner dual-spell matcher, linear-auto-done TEAM_KEY, pr-title negative fixture) do not exist in compass (verified: zero TEAM_KEY consts, zero `(SEA|RIG)` dual-spell matchers, no SEA-detection negative fixture). The sole `forks/` file carrying a SEA ref is forks/README.md, first-party compass prose that flips like any authored file; vendored forks/** subtrees carry zero SEA issue refs. A follow-up commit adds tools/sea-ref-gate to keep the boundary from re-rotting. Spec-impact: none (issue-ref token flip; number-preserving; no externally-visible behavior change). Refs RIG-2804. Co-authored-by: Matt Wilkinson <matt@rigel.build>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is part of a stack containing 2 PRs:
mainNumber-preserving
SEA-<n>→RIG-<n>sweep over the tracked compass tree,matching the settled orion #1829 (RIG-2569) pattern. The Linear team-key rename
preserved issue numbers 1:1 (SEA-1512 == RIG-1512), so this is a pure token flip
to match the live team name — no renumbering, no behavior change.
Mechanical guarantee. Applied by a one-shot codemod matching
\bSEA-(\d+)\b,then verified per file: for 344 of the 345 changed files, re-deriving the flip
from the
mainversion yields byte-identical output — i.e. the only change isSEA-<n>→RIG-<n>. 1515 refs across 345 files.The one exception is
docs/designs/DECISIONS.md, which additionally flips 4lowercase anchor-link slugs (
#...sea-1721...→#...rig-1721..., likewise1722/1723/1364). Those links target design-record headings whose text this flip
renamed (
### A1 — SEA-1721:→### A1 — RIG-1721:), so the heading's derivedGitHub anchor moved to
rig-; the link has to follow or it dangles. Thedesign-ledger gate validates exactly these ledger→record anchors and is what
surfaced it. Verified: DECISIONS.md deviates from the pure token flip on exactly
those 4 lines and nothing else.
Deliberately left untouched (the codemod does not match them):
sea-<n>branch-slug artifacts (e.g.compass-sea-1243-...) —historical git branch names quoted in design records; the team rename does not
rewrite the past.
SEA-nnn/SEA-NNN/SEA-Nprose placeholders — the digit class rejectsletters, so these stay as generic "some issue number" prose.
No carve-outs needed. orion #1829's three (issue-owner dual-spell matcher,
linear-auto-done TEAM_KEY, pr-title negative fixture) do not exist in compass
(verified: zero TEAM_KEY consts, zero
(SEA|RIG)dual-spell matchers, noSEA-detection negative fixture). The sole
forks/file carrying a SEA ref isforks/README.md, first-party compass prose that flips like any authored file;
vendored forks/** subtrees carry zero SEA issue refs.
A follow-up commit adds tools/sea-ref-gate to keep the boundary from
re-rotting.
Spec-impact: none (issue-ref token flip; number-preserving; no externally-visible behavior change).
Refs RIG-2804.
Co-authored-by: Matt Wilkinson matt@rigel.build