CMM: wire per-bay settings restore into the imaging flow

Restore-CMM.ps1 (new) restores a CMM's PC-DMIS + goCMM settings at imaging from
its staged backup. Self-gating: reads C:\Enrollment\cmm\{cmmid,version,doda,
partgroup}.txt, skips DODA bays and bays with no staged backup, and restores
ONLY the config-version PC-DMIS zip via the existing Install-*Settings scripts.
Same-bay restore (cmmid match) so the backed-up controller CommPort is this
bay's own value - no cross-bay clobber.

Version selection matches the VERSION FIELD of the zip name, anchored on the
trailing timestamp, so version=2026 does not false-match a 2019/2016 zip whose
backup timestamp (20260612...) merely contains "2026".

09-Setup-CMM.ps1: new Step 2.8 calls Restore-CMM after app install + first-run
init (so a restored config is not clobbered by PC-DMIS defaults) and before the
C:\CMM-Install cleanup (the backup set lives under <stagingRoot>\backups\<cmmid>).
Best-effort: Restore-CMM always exits 0, imaging never fails on a restore.

startnet.cmd: stage ONLY the picked bay's backup into C:\CMM-Install\backups\
%CMMID% (the bulk robocopy now /XD-excludes the backups tree, which holds every
bay's backup - some 240 MB each - to avoid copying GBs to every imaged CMM).
Also bump the PPKG to v4.16 (the live boot.wim was already v4.16; the repo had
drifted to v4.14).

sync-cmm-backups.sh: source the backups from pxe-images/cmm/backups (where
Backup-CMM writes via the pulled-down copies), not the old cmm-bk path.

Smoke tested on the win11 VM against CMM3's real backup: version=2019 restored
the 2019 R2 zip (not 2016.0), imported HKLM+HKCU reg, converted the part-group
S:\ path to the tsgwp00525 UNC, created C:\geaofi, exit 0; version=2026 correctly
found no matching zip (anchor works).

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

playbook/startnet.cmd

@@ -181,8 +181,8 @@ REM --- PPKG configuration (constructed at menu time, see docs) ---
 REM Vendor ships one source PPKG; we construct the BPRT-tagged filename
 REM by filling in Office, Region, Expiry, Version on the target copy.
 REM Update SOURCE_PPKG + PPKG_VER when a new PPKG is released.
-set SOURCE_PPKG=GCCH_Prod_SFLD_v4.14.ppkg
-set PPKG_VER=v4.14
+set SOURCE_PPKG=GCCH_Prod_SFLD_v4.16.ppkg
+set PPKG_VER=v4.16
 set PPKG_EXP=20260831
 set REGION=US
 
@@ -524,13 +524,24 @@ REM unified GE-Enforce dispatcher takes over from the share for ongoing updates.
 if /i not "%PCTYPE%"=="gea-shopfloor-cmm" goto skip_cmm_stage
 if exist "Y:\installers-post\cmm\cmm-manifest.json" (
     mkdir W:\CMM-Install 2>NUL
-    robocopy "Y:\installers-post\cmm" "W:\CMM-Install" /E /MT:16 /R:1 /W:1 /NFL /NDL /LOG+:"%STAGELOG%"
+    REM /XD the backups tree: it holds EVERY bay's settings backup (some 240 MB
+    REM each). Copying all of it to every imaged CMM would waste GBs. The bulk
+    REM copy excludes it; the selected bay's backup is staged separately below.
+    robocopy "Y:\installers-post\cmm" "W:\CMM-Install" /E /XD "Y:\installers-post\cmm\backups" /MT:16 /R:1 /W:1 /NFL /NDL /LOG+:"%STAGELOG%"
     if errorlevel 8 echo WARNING: cmm robocopy exit %ERRORLEVEL%
     echo Staged CMM bootstrap to W:\CMM-Install.
     echo [%TIME%] Staged CMM bootstrap >> "%STAGELOG%"
 ) else (
     echo WARNING: Y:\cmm-installers not found - CMM PC cannot install Hexagon apps at imaging time.
 )
+REM Stage ONLY the selected bay's settings backup. 09-Setup-CMM's Restore-CMM
+REM reads W:\CMM-Install\backups\%CMMID%\ to restore PC-DMIS + goCMM settings.
+if not defined CMMID goto skip_cmm_stage
+if exist "Y:\installers-post\cmm\backups\%CMMID%" (
+    robocopy "Y:\installers-post\cmm\backups\%CMMID%" "W:\CMM-Install\backups\%CMMID%" /E /MT:16 /R:1 /W:1 /NFL /NDL /LOG+:"%STAGELOG%"
+    echo Staged %CMMID% settings backup for restore.
+    echo [%TIME%] Staged %CMMID% backup >> "%STAGELOG%"
+)
 :skip_cmm_stage
 
 REM --- Stage Keyence per-model bootstrap bundle (Keyence PCs only) ---