ScottW514 527d864eaf Register the Z envelope harness and record the rebase ...

A new scripts/bench python file must be entered in the bench registry as
well as in that directory's README: the registry is what the acceptance
page reads, and a file in neither is a tool nobody can find. The harness
joins the other two host-side CI harnesses, marked not a bench-page tool
for the same reason they are - it drives the host-built null-sink
controller, not the machine.

CAMPAIGN-LOG gets the dated record of the rebase onto core build
20260905: the settings-struct measurement taken before the machine was
touched, the harness and the two broken builds it was validated against,
and the bench results.

2026-09-07 11:19:04 -04:00

..

BRINGUP.md

The GRBL settings store lives in /data/forgefirm

2026-09-06 22:22:33 -04:00

CAMPAIGN-LOG.md

Register the Z envelope harness and record the rebase

2026-09-07 11:19:04 -04:00