psadt-deploy-skill 0.34.0 → 0.34.2

package/README.md

@@ -434,44 +434,21 @@ 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.34.0 - 2026-09-16
-- **Added: `-TrustedPublisherCert` on `Invoke-PsadtSandboxTest.ps1`.** An installer that stages a
-  third-party driver raises the Windows "install device software?" prompt unless the signer is already in
-  `TrustedPublisher` - and in the guest that prompt is **invisible**, because every action runs as SYSTEM
-  through a scheduled task and draws nothing on the desktop. The installer waits for an answer nobody can
-  give and the phase burns its whole timeout, looking exactly like a slow installer. Pass the `.cer` and
-  the harness imports it during GuestPrepare, the same thing an Intune `RootCATrustedCertificates` profile
-  does on the fleet. Measured on Time-Access 3010 / EDIsecure: **25 minutes of timeout versus 43 seconds**.
-  The import uses `certutil` (`Import-Certificate` returns `E_ACCESSDENIED` in the guest even when
-  elevated) and is **verified by reading the store back** - a failed import is indistinguishable from a
-  successful one when only the return value is logged, and that cost a full run.
-- **Fixed: the elapsed timer in the guest window stopped counting.** It rendered `progress.json` verbatim,
-  but `Update-Ui` returns early when that file has not changed - right for the phase list, fatal for a
-  clock, and phases that are not an action wait loop never rewrite the file at all (GuestPrepare alone can
-  sit there for 90 seconds). The one element whose job is to prove the run is alive was frozen exactly
-  when that gets asked. It now ticks on the window's own 1s timer and re-syncs on every file value.
-- **Fixed: the heartbeat was up to 20 seconds stale** - the guest wrote every 10s and the host read every
-  10s, and the two stacked. Both are 1s now; the console line and transcript keep the coarser beat so
-  phase boundaries stay legible.
-- Phase 6.1 now documents cancelling with `STOP.txt` (killing the process orphans `vmmemWindowsSandbox`
-  and blocks every further run) and scoping with `-Scenarios` while iterating. Suite 624, unchanged by this release - the new behaviour is guarded by the existing sandbox-harness and progress-UI tests.
-### 0.33.0 - 2026-09-16
-- **Fixed: the Phase 2 research fan-out is gated.** `SKILL.md` ordered it in the imperative - *"Dispatch
-  the three Researcher roles concurrently"* - one line above the two probe sentences, and rule 1 routed
-  every unknown into it because asking is forbidden. Three agents ran whether or not anyone needed them;
-  on an app already installed on the packaging machine, one such run cost 400k tokens to rediscover a
-  `QuietUninstallString` the Uninstall registry had been holding all along.
-- **Added: `scripts/Get-PsadtLocalEvidence.ps1`**, the ladder that decides whether an agent is warranted.
-  Four rungs, deterministic and offline: the installed PSADT module's manifest (retiring the
-  version/command-drift research topic outright), the Uninstall registry, the existing MSI and
-  switch-candidate probes composed rather than reimplemented, and this skill's own corpus plus a vendor
-  doc URL it **names but never fetches**. It reports `OpenQuestions[]` and `AgentBudget`, and that number
-  is the dispatch cap: zero open questions, zero sub-agents.
-- **Capped by family, so the cap is structural.** Questions one vendor deployment page answers fold into
-  a single agent. Three families can ever dispatch, so the budget cannot exceed three however the
-  question set grows - measured at **2 for an MSI or an app installed locally, 3 at worst**.
-- **Honest about its limits.** The external runtime prerequisite and known Intune pitfalls are marked
-  `CanCloseLocally = $false` - a statement about other people's fleets does not follow from this machine -
-  so the realistic floor is two agents, not zero. Everything open but not worth an agent lands in
-  `Deferred[]` with a reason, and `repair-strategy` is now a first-class question because
-  `rule:all-three-deployment-types` makes Repair a deliverable.
+### 0.34.2 - 2026-09-16
+- **Added: `tests/SiteFigures.Tests.ps1`** - the landing page's stat tiles are now derived from the
+  repository and compared, instead of being hand-maintained and unchecked. A reader found the page
+  claiming 19 installer engines in the tile and "1 of 14" in the Phase 2 step right below it; the
+  script count had also been one behind since 0.33.0. index.html lives on gh-pages, so the suite had
+  never seen it. The guard reads it out of that ref, skips itself when the ref is absent, and the
+  workflow fetches it so CI checks it for real. Both stale figures fixed. Suite 624 -> 631.
+
+### 0.34.1 - 2026-09-16
+- **Changed: SKILL.md now names `-TrustedPublisherCert` at Phase 6**, with `-Scenarios` for iteration and
+  `STOP.txt` for cancelling. 0.34.0 documented the certificate in phase 6.1 only, because the control
+  plane had 55 bytes of headroom against its 5000-token budget - the wrong trade for a failure that is
+  expensive and silent, since an agent that never opens 6.1 repeats the 25-minute timeout blind. Room was
+  made the way the budget test prescribes: `rule:author-version-changelog` and `rule:start-menu-only`
+  moved to `references/conventions.md`, which already carried their full text and which SKILL.md routes
+  to. Both are editorial rules - their failure costs a doc edit or a stray desktop icon, not a
+  deployment. Control plane 17348 / 17500 bytes, headroom 55 -> 152. Suite 624, unchanged.
+

package/package.json

@@ -1,37 +1,37 @@
-{
-  "name": "psadt-deploy-skill",
-  "version": "0.34.0",
-  "description": "Installer for the psadt-deploy Claude Code skill: build, test and deploy PSADT v4.x Intune Win32 packages.",
-  "keywords": [
-    "psadt",
-    "psappdeploytoolkit",
-    "intune",
-    "win32",
-    "claude-code",
-    "claude-skill",
-    "packaging"
-  ],
-  "homepage": "https://github.com/pt1987/claude-code-psadt-skill#readme",
-  "bugs": {
-    "url": "https://github.com/pt1987/claude-code-psadt-skill/issues"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/pt1987/claude-code-psadt-skill.git"
-  },
-  "license": "MIT",
-  "author": "Patrick Taubert, PHAT Consulting GmbH",
-  "type": "module",
-  "bin": {
-    "psadt-deploy-skill": "bin/install.mjs"
-  },
-  "files": [
-    "bin"
-  ],
-  "engines": {
-    "node": ">=18"
-  },
-  "os": [
-    "win32"
-  ]
-}
+{
+  "name": "psadt-deploy-skill",
+  "version": "0.34.2",
+  "description": "Installer for the psadt-deploy Claude Code skill: build, test and deploy PSADT v4.x Intune Win32 packages.",
+  "keywords": [
+    "psadt",
+    "psappdeploytoolkit",
+    "intune",
+    "win32",
+    "claude-code",
+    "claude-skill",
+    "packaging"
+  ],
+  "homepage": "https://github.com/pt1987/claude-code-psadt-skill#readme",
+  "bugs": {
+    "url": "https://github.com/pt1987/claude-code-psadt-skill/issues"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/pt1987/claude-code-psadt-skill.git"
+  },
+  "license": "MIT",
+  "author": "Patrick Taubert, PHAT Consulting GmbH",
+  "type": "module",
+  "bin": {
+    "psadt-deploy-skill": "bin/install.mjs"
+  },
+  "files": [
+    "bin"
+  ],
+  "engines": {
+    "node": ">=18"
+  },
+  "os": [
+    "win32"
+  ]
+}