igneum-labs 714fc79e7d The registry's structural transforms replay at the merge like batches: the REV generator and the notes; a NOT RUN row is stamped only on change ... merge-to-master.sh rebuilds the registry from master's copy whenever a landing carries any transform, then regenerates the REV suite from the merged tree's findings and dispatch (review-suite.mjs --write), replays every added batch, and replays every added note file (tools/ci/notes/<id>.json, {suite, text}, through test-record.mjs --note-file), then regenerates the harness page from the structurally merged map. The founder's two rulings ride as note files. test-record.mjs stamps a NOT RUN row only when its status or reason changes (every landing had been colliding on 39 untouched rows, the reference-apps lane's finding). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>		2026-10-08 19:16:03 +00:00
..
f04-fin-20261008.json	The registry's structural transforms replay at the merge like batches: the REV generator and the notes; a NOT RUN row is stamped only on change	2026-10-08 19:16:03 +00:00
f14-ops-20261008.json	The registry's structural transforms replay at the merge like batches: the REV generator and the notes; a NOT RUN row is stamped only on change	2026-10-08 19:16:03 +00:00
f14-ux-20261008.json	The registry's structural transforms replay at the merge like batches: the REV generator and the notes; a NOT RUN row is stamped only on change	2026-10-08 19:16:03 +00:00