GE-Enforce: bump enforcerVersion to 2.4 in status.json write-back

Hardcoded version string surfaced in _outputs/logs/<host>/status.json
that the fleet check-in dashboard reads. Bump aligned with
Install-FromManifest lib v2.4 (PCTypes alias map + network-share EXE
staging). Lets the convergence-check oneliner distinguish PCs that
have picked up the post-rename dispatcher from those still on 2.0.

When pushed to share + the self-update common/manifest.json entry's
DetectionValue is bumped to the new SHA256 (commit notes record the
hash but the manifest itself lives on the v2 share, not in this repo
by design), every fleet PC's next cycle re-fires the self-update,
copies new bytes locally, the cycle after that writes status.json
with enforcerVersion=2.4. Fully visible in the dashboard read.

new GE-Enforce.ps1 SHA256:
  C8C14CFCE539ACDC6D16B31D2C456A5239516BDFA1EBFC820794A2D58BA7D9AC

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

playbook/shopfloor-setup/common/GE-Enforce.ps1

@@ -285,7 +285,7 @@ try {
             lastCheckIn       = (Get-Date).ToUniversalTime().ToString('o')
             pcType            = $pcType
             pcSubType         = $pcSubType
-            enforcerVersion   = '2.0'
+            enforcerVersion   = '2.4'
             shopfloorShareRoot = $shopfloorShareRoot
             scopesProcessed   = $scopeResults
             installedVersions = $installedVersions