grblhal-glowforge SRCREV 683a36a (comment-free core fix); BRINGUP cites the fork commit hash-free

docs/BRINGUP.md

@@ -155,9 +155,9 @@ overflow detected" in /data/glowforge.log — before serving: the core's
 `step_us_min[4]` holds `ftoa(hal.step_us_min, 1)` and our 28160 Hz
 stream tick renders "35.5" (5 bytes). Bench builds (no fortify)
 silently truncated the adjacent unit string instead, which is why it
-never showed on the bench. Fixed by sizing the buffer (core fork
-commit e7ef419, `forgefirm` branch); `$ES` now reports
-`[SETTING:0|…|35.5|…]` intact. Repro/diagnosis path if ever needed
+never showed on the bench. Fixed by sizing the buffer (the single
+local commit the core fork's `forgefirm` branch carries atop upstream
+master); `$ES` now reports `[SETTING:0|…|35.5|…]` intact. Repro/diagnosis path if ever needed
 again: `scripts/bench/build-glowforge.sh` variant with
 `-D_FORTIFY_SOURCE=2`, gdb `set breakpoint pending on` + `break
 __chk_fail`, run on the board. The image is whole only once

meta-forgefirm/recipes-forgefirm/grblhal-glowforge/grblhal-glowforge.bb

@@ -11,7 +11,7 @@ PV = "0.1.0"
 # upstream).
 SRC_URI = "gitsm://github.com/ScottW514/grblHAL-glowforge.git;protocol=https;branch=main"
 # Pinned; bump deliberately after pushing grblHAL-glowforge changes.
-SRCREV = "bdab31c812dbb7a1da88553fe493054036543774"
+SRCREV = "683a36a9330dfbbddc7785bfbc8f5ba73dbd8ff3"
 
 SRC_URI += "file://grblhal.init"