Fix the unattend that broke Engineer builds; gate unattend deploys on the linter

a94c203 added a RunSynchronous Path of 417 chars to both std/eng answer
files. Windows caps it at 259 and then rejects the WHOLE answer file, so
an Engineer build stopped at 'Windows could not parse or process unattend
answer file'. The live files were restored to their pre-a94c203 versions
the same day.

- The status steps now fit: Send-ImagingStage.ps1 -Persist copies itself
  out of C:\Deploy (no cmd copy chain), short PowerShell switches, default
  arguments left out. Longest Path is 168 chars; lint-unattend passes.
  NOT deployed: these files must go live only through deploy-unattend.sh.
- scripts/deploy-unattend.sh: the only route for an answer file to a PXE
  server. Lints first and refuses on any error, backs up, swaps
  atomically, lints the live copy and restores the backup if that fails.
- .githooks/pre-commit (git config core.hooksPath .githooks): refuses a
  commit whose staged unattend fails the linter. Verified by planting a
  352-char Path (blocked) and against the exact a94c203 file (rejected).
- Boot menu: also accept SecureBoot read as hex 01, and show the raw values
  in the warning so a wrong read can be diagnosed from the screen.

playbook/ipxe/GetPxeScript.aspx

@@ -21,8 +21,10 @@ choose --default winpe --timeout 30000 target && goto ${target}
 # iPXE 2.0 reads the firmware variable; older iPXE cannot (empty), so it
 # warns as before. Secure Boot confirmed on: no warning, no wait.
 iseq ${efi/SecureBoot:uint8} 1 && goto winpe_boot ||
+iseq ${efi/SecureBoot:hex} 01 && goto winpe_boot ||
 echo
 echo   Secure Boot is OFF on this PC (or this iPXE cannot tell).
+echo   (iPXE read SecureBoot as: [${efi/SecureBoot:hex}] [${efi/SecureBoot:uint8}])
 echo   Windows deployment requires Secure Boot to be ENABLED.
 echo   If you disabled it for Clonezilla/Memtest, re-enable it now.
 echo