anchors renumber

Renumber the revisions this branch added when the base already took their number.

Finds the revision blocks (`CODE-R000N`) this branch ADDED whose number the base
already uses — two pull requests that each took the next free number — and moves them to
the next free numbers, rewriting every citation of the old code in what the branch changed:
specs, plans, features, tests and code comments.

Only the branch's revisions move. A revision the base has is history others have already
read and cited; renumbering it would point every one of those citations at the wrong change.
Likewise, a citation is rewritten only on a line the branch added — a line that existed
where the branch forked cites what the base means by that code.

With no file given, every Markdown file the branch changed against the base is examined.
Run it after rebasing onto the base (or before — both work):

    git rebase origin/main
    anchors renumber --dry-run                 what would move, and where it is cited
    anchors renumber                           applies
    anchors renumber specs/Pricing.spec.md     only this spec's revisions
    anchors renumber --base origin/develop     against another base

The base defaults to `origin/<integration_branch>` (or the local branch when there is no remote).

Usage

anchors renumber [spec files...] [flags]

Flags

Flag	Default	What it does
--base		the ref the branch merges into (default: origin/<integration_branch>)
--dry-run		show what would be renumbered, without writing
--root	.	project root

The map and its signals — family

Commands of the same family — what tells each apart:

Command	What it does
anchors map	Operate the dependency map (anchors.graph.yaml)
anchors ingest	Ingest test signals (JUnit/lcov) the project generated and bind them to the map
anchors test	Run the test suites declared in anchors.yaml and ingest the reports
anchors mutation	Run the mutation suites declared in anchors.yaml and ingest the reports
anchors keep-evidence	Declare that a change proves nothing new, keeping the files’ evidence fresh
anchors stamp	Write the missing @contract stamps on test doubles (never rewrites an existing one)
anchors recode	Rename an identity code and propagate it across the project
anchors renumber	Renumber the revisions this branch added when the base already took their number
anchors generated-paths	The paths of DERIVED files — whoever conflicts in them rebuilds
anchors merge-progress	Progress merge driver: unites both sides, [x] beats [ ]