pins: the revisions the authorized campaign ran

forgectrl 8ef9509 at 0.1.2, grblhal-glowforge 2f5edee at 0.1.2, and the
forgefirm-app recipes at dd0ebf3, 0.1.23+git. These are the sources the
full campaign on image 20260903211413 passed against, now that their
repositories are pushed and the build no longer needs the local overlay.

meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc

@@ -2,5 +2,5 @@
 # only SRCREV and PV here - the image manifest leaves *-pin.inc out of the
 # layer content hash because the component entry already identifies the
 # pinned source (forgefirm-image-manifest.bbclass).
-SRCREV = "522cdb2c251338928d26b9e3d9dc3ea059e5a649"
-PV = "0.1.1"
+SRCREV = "8ef95091b7f22fa100814147bef437602d96dc26"
+PV = "0.1.2"

meta-forgefirm/recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc

@@ -4,9 +4,9 @@
 # because the component entry already identifies the pinned source
 # (forgefirm-image-manifest.bbclass). The python3-gfhardware recipe in
 # meta-glowforge-bsp pins the same repository; move both together.
-SRCREV = "1511336b36378f0a21e75dd650cdc1d8cf492e0c"
+SRCREV = "dd0ebf30838feb351cb552eb2e3839173521c9e6"
 
 # Bump PV with every SRCREV move: the hash-derived package version is not
 # monotonic on its own and buildhistory QA fails the build when it sorts
 # backwards.
-PV = "0.1.22+git"
+PV = "0.1.23+git"

meta-forgefirm/recipes-forgefirm/grblhal-glowforge/grblhal-glowforge-pin.inc

@@ -2,5 +2,5 @@
 # changes; keep only SRCREV and PV here - the image manifest leaves
 # *-pin.inc out of the layer content hash because the component entry
 # already identifies the pinned source (forgefirm-image-manifest.bbclass).
-SRCREV = "b951f3aea44d7dd3ce83c7679e98427c4df5ee17"
-PV = "0.1.1"
+SRCREV = "2f5edee5cdf4537793d7f98407fd8c7df8e1e438"
+PV = "0.1.2"