anchors generated-paths

The paths of DERIVED files — whoever conflicts in them rebuilds.

Prints the patterns of the files that Anchors generates.

Whoever resolves a conflict uses this to tell NOISE from DIVERGENCE: in a generated
file, rebuilding produces the right answer; in a work file, two people
wrote different things and only they decide.

    anchors generated-paths              # one per line
    anchors generated-paths --format re  # as a regex alternation, for grep

The list comes from the PRODUCT, not from constants repeated in each project's script.
It is a single source: when a path changes, every project follows.

Usage

anchors generated-paths [flags]

Flags

Flag	Default	What it does
--format	lines	lines (one per line) or re (alternation, for grep -E)
--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 [ ]