anchors merge-progress

Progress merge driver: unites both sides, [x] beats [ ].

Resolves the merge of a `*-progress.md` by uniting the items of both sides.

Not meant to be run by hand. Configure git to call it:

  # .gitattributes (no repositório)
  *-progress.md merge=anchors-progress

  # once per clone
  git config merge.anchors-progress.name "anchors: unites the progress of the plans"
  git config merge.anchors-progress.driver "anchors merge-progress %O %A %B"

WHY: two branches delivering specs of the SAME plan mark neighboring checkboxes, and
git asks for manual resolution every time. Measured: three consecutive PRs, identical
resolution in all three. The rule is `[x]` beats `[ ]` — unmarking by merge would
erase a delivery that already happened.

The result is written to <ours>, which is what git expects.

Uso

anchors merge-progress <base> <ours> <theirs>

O mapa e seus sinais — família

Comandos da mesma família — o que distingue cada um:

Comando	O que faz
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 [ ]