psadt-deploy-skill 0.29.0 → 0.30.0

package/README.md

@@ -93,6 +93,10 @@ control plane.
 
 - **Guided intake** — the blocker questions up front as clickable options, pre-filled with researched
   defaults (app, latest version, installer type, package type).
+- **Switch catalog before the web** — identifies the installer engine from the *binary* (byte signatures in
+  the PE overlay, resources and section table, not a filename guess) and serves that engine's documented
+  silent / uninstall / log / no-reboot switches from a catalog that ships with the skill. Offline, and it
+  reports every stage it checked including the misses. A candidate is still a claim until a run proves it.
 - **Autonomous research** — checks the installed PSADT version against the latest release *and* whether
   commands changed; researches silent install / uninstall / repair switches and known Intune pitfalls.
 - **All three deployment types from the start** — Install, Uninstall *and* Repair, acid-tested, so
@@ -172,7 +176,7 @@ The app's **native installer is always the default**. Everything else is opt-in
 - **Self-update** — `scripts/Update-PsadtSkill.ps1` compares against GitHub, shows what changed, and
   updates in place on your confirmation (`git pull --ff-only` for a clone, otherwise a branch-zip overwrite
   of tracked files only). Machine-local state is never touched. Say *"psadt update"*.
-- **441 Pester tests** over the helper scripts, including drift guards that fail when the docs and the code
+- **503 Pester tests** over the helper scripts, including drift guards that fail when the docs and the code
   disagree.
 
 ## Requirements
@@ -345,9 +349,10 @@ psadt-deploy/
 │  ├─ README.md                          the reference map (label -> file)
 │  ├─ phases-0-6.md · phases-7-12.md     the twelve phases
 │  ├─ appendix-a-errors.md … -q-drivers.md  one file per appendix
+│  ├─ switch-catalog/                    engine defaults + JSON schema (App. L.0)
 │  ├─ Report-Template.html               the fixed dossier template
 │  └─ app-registration.md                THE Graph permission matrix + manual portal route
-└─ tests/                                Pester suite, 441 tests
+└─ tests/                                Pester suite, 551 tests
 ```
 
 Machine-local state lives outside the skill folder:
@@ -368,7 +373,7 @@ psadt-package.json                       identity · gate decisions · research
 ## Status
 
 In active use for the full build → package → test → dossier workflow, with the direct Graph upload
-verified against a live tenant. The helper scripts are covered by 441 Pester tests.
+verified against a live tenant. The helper scripts are covered by 503 Pester tests.
 
 One open point, honestly: **the driver `pnputil` exit-code semantics are documented, not verified here.**
 `0` / `259` / `3010` and the two `0xE...` failures come from Microsoft's documentation; confirming them
@@ -429,35 +434,36 @@ The two most recent releases are below. **[CHANGELOG.md](CHANGELOG.md)** carries
 every release since 0.1.0, and nothing is ever removed from it - this section is a window onto it, not a
 second copy to keep in sync.
 
-### 0.29.0 - 2026-09-11
-- **Fixed: the 0.28.0 Startup-folder trigger could not run a single task as SYSTEM.** The runner passed
-  the elevation check, yet `schtasks /Create` and `/Run` returned 0 while the task never executed - every
-  action timed out blaming the package. `<LogonCommand>` is back; #125 is left to the host's DONE.txt timeout.
-- **Fixed: `schtasks`' stderr notice ended the run before the first action** - in WinPS 5.1 a `2>file`
-  redirect does not stop the terminating `NativeCommandError`; the preference is lowered around the call.
-- **Fixed: the sandbox image lacked `de-DE\ArchiveResources.psd1`**, which PSADT needs just to import,
-  and **WMI refused SYSTEM** (`Win32_ComputerSystem` -> `0x80070005`), which `Open-ADTSession` needs.
-  Both surfaced as 60008 on every action with no log. `GuestPrepare` ships the host's module resources
-  into the guest and repairs the WMI repository.
-- **Added: three canaries before the loop** (SYSTEM task, toolkit import, toolkit session), **a 60008
-  action is re-run once via `powershell.exe -File` to capture the stderr the `.exe` discards**, and a
-  **heartbeat in the guest console** so a healthy install no longer looks like a hang. Suite 493 -> 501.
-### 0.28.0 - 2026-09-11
-- **Fixed: a space in the `.wsb` path silently disabled every custom mapped folder.** `Start-Process
-  -ArgumentList` does not quote its elements, so Windows Sandbox booted with the built-in shares only -
-  no error, no warning. A username with a space in it is enough, and it reads exactly like an upstream
-  Sandbox bug.
-- **Fixed: `<LogonCommand>` never ran** on the affected Sandbox app version
-  ([#125](https://github.com/microsoft/Windows-Sandbox/issues/125)). The work folder is now mapped onto
-  the guest's Startup folder and a trigger `.cmd` starts the runner, which lives one level down because
-  Startup auto-executes only `.exe/.bat/.cmd/.lnk/.vbs`.
-- **Fixed: a transient read reported a real result as empty** - a detection step captured `stdout: ""`
-  while the same file, re-read at the end of the run, held the right answer. The read now retries.
-- **Changed: `schtasks` failures are checked** instead of surfacing as a 900-second timeout, and the
-  runner verifies it is elevated before the first action - a Startup item does not carry the full admin
-  token by construction the way `<LogonCommand>` did.
-- **Added: NSIS MultiUser needs an explicit `/allusers` or `/currentuser`** (App. L.7). A bare `/S`
-  exits in under a second with no output and nothing installed. Now a Gate 2 decision.
-- **Added: an unbundled runtime prerequisite is researched in Phase 2 and decided at Gate 1**, and a
-  manual interactive test is offered after a GREEN Phase 6 - the loop proves the package works, never
-  that the app does. Suite 484 -> 493.
+### 0.30.0 - 2026-09-14
+- **Fixed: the sandbox could not test a heavy package - and it was never the package.** Smart App Control
+  is enabled in the Windows Sandbox base image while Defender is disabled, so `wintrust` asks the disabled
+  Defender to rate every signed file and waits ~2 minutes per package. A bootstrapper chaining a dozen MSIs
+  took 30+ minutes and looked like a hang, three times. Two lines in the guest remove it: the same run then
+  finished in **5.7 minutes with exit 0**. This also corrects the ADK lesson in Appendix G, which blamed
+  Defender scanning - Defender was switched off the whole time.
+- **Fixed: nothing was visible inside the sandbox.** On this Sandbox build the `LogonCommand` process gets
+  no console window, so the 0.29.0 heartbeat went to a file nobody could see. There is now a top-most
+  progress window in the guest, the host mirrors it, and the runner measures whether a console exists at
+  all. Runs are cancellable with `STOP.txt` (guest shuts itself down in 5 s, no orphaned VM worker), a
+  failed VM start is no longer reported as "the VM was closed", and a timed-out action captures the guest's
+  process table and vendor logs before the VM is discarded.
+- **Added: `Get-PsadtInstallerEngine.ps1`** - identifies the installer engine from the binary. A definitive
+  marker always beats a hint, so an install4j installer carrying NSIS branding no longer gets `/S`, which
+  hangs on its language dialog forever. Reports marker, byte offset and region; an unrecognised file
+  returns `unknown`, never a guess.
+- **Added: `Get-PsadtSwitchCandidates.ps1` + `references/switch-catalog/`** - ranked switch candidates from
+  19 engine defaults, offline, before the first web query, with a reason for every miss. It is an ENGINE
+  catalog, not an application catalog, and **winget stays opt-in** including as a research source.
+- **Faster:** staging 481 MB into the guest via `robocopy /MT` (3.6 s to 0.6 s), `-Scenarios` for partial
+  iteration runs, per-action timeout default 900 s to 600 s. Suite 503 -> 551.
+### 0.29.1 - 2026-09-14
+- **Fixed: Phase 5.5 mapped `Remove-MSIApplications` to `Remove-ADTApplication`**, which v4 does not
+  have - the v4 name is `Uninstall-ADTApplication`. The table's right column is now checked against the
+  installed toolkit's `FunctionsToExport`.
+- **Fixed: Appendix A named 60012 as the v4 deferral code.** 4.1.x exits a deferral with
+  `UI.DeferExitCode`, default 1602. Deliberately NOT added to the mandatory Intune table - every install
+  command this skill writes runs `-DeployMode Silent`, where a deferral cannot happen.
+- **Fixed: the Phase 4.3 MSI sample** put the `.mst` in `SupportFiles\` and passed an `-ArgumentList`
+  identical to the config defaults. The `.mst` belongs in `Files\` next to the MSI (`TRANSFORMSSECURE=1`);
+  extra properties go into `-AdditionalArgumentList`, because `-ArgumentList` REPLACES the defaults.
+- **Fixed: README claimed 441 Pester tests** in three places. Suite 501 -> 503.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "psadt-deploy-skill",
-  "version": "0.29.0",
+  "version": "0.30.0",
   "description": "Installer for the psadt-deploy Claude Code skill: build, test and deploy PSADT v4.x Intune Win32 packages.",
   "keywords": [
     "psadt",