mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-10-15 17:19:55 -07:00
ScottW514
f8dc21b309
motion.button-hold-resume held on the machine that the button holds a travel job and the next press resumes it to its target. The host proves it now: laser_lifecycle_test rule 7 runs the same job (M5, G91, G1 X40 F300) through the toggle and lands it within 0.05 mm of +40 (a0a4edb), beside the armed half that owns the pause and resume messages. Real stepping stays with the kept motion tests; the physical button with setup.check-switches. - The test goes; no helper was its alone (start_move and Watch serve motion.lid-cancel-home, which keeps _LID_COVERS). - laser.pause-resume-lid-cancel no longer requires it. The removed test required only motion.pacing, which motion.lid-cancel-home still brings. Proof: the coverage lint reports 0 uncovered paths and 0 host-tested row problems over 106 tests (its one failure is setup.check-lens's src/lensfind.* entry, which the forgectrl pin bump clears); the gate self-check refuses an empty artifact cleanly; pyflakes adds no finding. The unit modules that load the whole catalog pass under Linux: test_artifact, test_campaign, test_cooling_order, test_fixture, test_manifest, test_operator. Acceptance: motion.py's shared text and laser.pause-resume-lid-cancel's own text move. Against the image on the bench that adds no run:6a434bbalready changed both laser.py's and motion.py's shared text.