psadt-deploy-skill 0.26.7 → 0.27.1

package/README.md

@@ -1,865 +1,973 @@
-<h1 align="center">PSADT v4 → Intune Deployment Skill</h1>
-
-<p align="center">
-  <em>A Claude Code skill that drives the full lifecycle of a PowerShell App Deployment Toolkit (PSADT) v4.x Intune Win32 package — from first conversation to a tested, upload-ready <code>.intunewin</code>.</em>
-</p>
-
-<p align="center">
-  <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue.svg?style=flat-square" alt="License: MIT" /></a>
-  <img src="https://img.shields.io/badge/PSADT-v4.x-0a7bbb?style=flat-square" alt="PSADT v4.x" />
-  <img src="https://img.shields.io/badge/Platform-Windows-0078d6?style=flat-square&logo=windows&logoColor=white" alt="Windows" />
-  <img src="https://img.shields.io/badge/Claude%20Code-Skill-d97757?style=flat-square" alt="Claude Code Skill" />
-</p>
-
-<p align="center"><sub><a href="#quick-start">Quick start</a> · <a href="#how-it-works">How it works</a> · <a href="#features">Features</a> · <a href="#first-run-setup">Setup</a> · <a href="#roadmap">Roadmap</a> · <a href="#changelog">Changelog</a></sub></p>
-
----
-
-## What is this?
-
-A **Claude Code skill** (not a plugin): a reusable instruction package that teaches the agent how to build,
-package, test, troubleshoot and deploy a **PSADT v4.x Intune Win32 app**. You describe the application; the
-skill runs the workflow — intake, web research, scaffolding, all three deployment types
-(Install / Uninstall / Repair), pre-flight checks, the SYSTEM test, packaging, the dossier, and the
-optional Graph upload.
-
-A skill is a folder with a `SKILL.md` (YAML frontmatter + Markdown instructions), here bundled with
-`scripts/` and `references/`. It loads progressively: the agent sees only the name and description until a
-task makes it relevant, then the full body loads on demand.
-
-<img width="1024" height="254" alt="image" src="https://github.com/user-attachments/assets/7c7931ba-dcae-4476-a648-11115eceb3b5" />
-
-## Quick start
-
-```powershell
-npx psadt-deploy-skill
-```
-
-That installs the skill into `~/.claude/skills/psadt-deploy` and runs the setup doctor, which provisions
-everything it can and names the handful of values only you can supply (see
-[First-run setup](#first-run-setup)). Then open Claude Code in any folder and say what you want:
-
-> *"Create the Win32 Intune package for 7-Zip 24.09"* — or *"package Notepad++ for Intune"*
-
-The skill asks at most **four decision gates** (scope · deployment semantics · SYSTEM-test consent ·
-upload confirmation). Everything else it researches and states as an assumption instead of asking.
-
-## How it works
-
-Twelve phases, each owned by a script rather than by prose, so a step either passed or did not:
-
-| Phase | What happens | Owner |
-|---|---|---|
-| **0** Setup | 13 prerequisite checks, GREEN/YELLOW/RED, `-Fix` provisions | `Initialize-PsadtSkill.ps1` |
-| **1–2** Intake + research | blocker questions as clickable options; parallel research of version, silent switches, Intune pitfalls | agent (gates 1–2) |
-| **3** Scaffold | a generator writes launcher + detection + per-run log name + manifest; `New-ADTTemplate` only when none fits | `New-MsiPackage` · `New-BrowserExtensionPackage` · `New-WindowsFeaturePackage` · `New-DriverPackage` |
-| **4** Customize | all three hooks filled from the research, helpers in the Extensions module | agent |
-| **5** Pre-flight | 10 checks (encoding, AST parse, v3 cmdlets, structure, detection contract, manifest, log name, driver trust …) → GREEN/RED | `Invoke-PsadtPreflight.ps1` |
-| **6** SYSTEM test | installs/uninstalls as **SYSTEM** like the IME does; **binding before any upload** | `Invoke-PsadtSystemTest.ps1` |
-| **7** Package | one command → verified `.intunewin`, named after the app | `Invoke-PsadtPackage.ps1` |
-| **8** Dossier | always, uploaded or not: bilingual self-contained HTML | `New-PsadtReport.ps1` |
-| **9** Upload *(opt-in)* | dry run → confirm → `win32LobApp` via raw Graph | `Invoke-IntuneWin32Upload.ps1` |
-| **10** Assignment *(opt-in)* | create/reuse Entra groups by naming scheme | `Invoke-IntuneAppAssignment.ps1` |
-| **11–12** Test + rollout | DEV-VM cycles, test group, pilot → staged production | agent |
-
-**Everything one app knows lives in `<pkg>\psadt-package.json`** — identity, the decisions taken at the
-gates, the research findings, every phase's result and the artifacts produced. The generators write it,
-every later phase reads and updates it, and pre-flight fails without it. That is what stops two packages of
-the same app from disagreeing about their own version.
-
-Depth lives in `references/PSADTv4-Deployment-Guide.md` (Phases 0–12 + Appendices A–Q); `SKILL.md` stays the
-control plane.
-
-## Features
-
-### Setup and prerequisites
-
-- **Setup doctor** — one idempotent script checks PowerShell 7, Windows PowerShell 5.1, elevation, git,
-  PSAppDeployToolkit, the content-prep tool, `Invoke-CommandAs`, Pester, the config, a legacy config, the
-  skill tree, a pending update and the Intune credentials. Each line carries a concrete fix; `-Fix` applies
-  the ones that need no decision.
-- **Self-healing prerequisites** — installs the PSAppDeployToolkit module from the PowerShell Gallery and
-  downloads `IntuneWinAppUtil.exe`, keeping both current against their official sources.
-- **Config outside the skill folder** — `config.json`, `secret.dpapi` and `tools/` live in
-  `%LOCALAPPDATA%\psadt-deploy\` (override: `$env:PSADT_DEPLOY_HOME`), so a `git pull`, a re-clone or a
-  re-install can no longer take your setup with it. A pre-0.19 config keeps working and is migrated on
-  request, never deleted.
-- **One-line install** — `npx psadt-deploy-skill` (Node 18+, zero dependencies) does clone-or-update plus
-  the doctor run in one step.
-
-### Build and verify
-
-- **Guided intake** — the blocker questions up front as clickable options, pre-filled with researched
-  defaults (app, latest version, installer type, package type).
-- **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
-  Company-Portal uninstalls actually work.
-- **Pre-flight gate** — encoding/BOM, AST parse, launcher acid test, v3-cmdlet scan, hook structure,
-  detection-script contract, the package manifest, the per-run log name and driver trust. GREEN or RED,
-  with the failing file named.
-- **Automated SYSTEM test loop** *(opt-in, binding before upload)* — installs, uninstalls and reinstalls as
-  the **SYSTEM** account via `Invoke-CommandAs`, mirroring the Intune Management Extension; reads the fresh
-  session log and the detection result, and hands back a structured verdict for the fix-and-retry loop.
-  Needs an elevated session; belongs on a VM with a snapshot.
-- **Deterministic packaging** — `<outputRoot>\<Vendor>_<App>_<Version>_<Arch>\<same stem>.intunewin`,
-  verified after the fact (`Detection.xml`, `SetupFile`, size, SHA256), with the detection script and the
-  real logo beside it. It refuses an output folder inside the package, and never deletes a foreign
-  `.intunewin` it finds there.
-- **One PSADT log per run** — `<Vendor>_<App>_<Version>_<Arch>_<Install|Uninstall|Repair>_<timestamp>.log`
-  instead of every run of every version appending to one unreadable file.
-
-### Package types
-
-The app's **native installer is always the default**. Everything else is opt-in and only on request:
-
-- **MSI / EXE** — the ordinary case, via `New-MsiPackage.ps1` or a hand-filled scaffold.
-- **WinGet** — the full `PSAppDeployToolkit.WinGet` lifecycle: the extension module self-heals into the
-  package, the Package ID is discovered with `Find-ADTWinGetPackage`, hooks use `*-ADTWinGet*`
-  (`-Scope Machine`). Never selected on its own initiative.
-- **Browser extensions** — force-install via the Edge/Chrome/Firefox policy keys (including the Firefox
-  `REG_MULTI_SZ` trap), with selective removal on uninstall.
-- **Windows features** — `Enable-WindowsOptionalFeature` and `Add-WindowsCapability`, offline source or a
-  temporary WSUS bypass that is restored afterwards, `EnablePending` handled honestly.
-- **Third-party drivers** — the trust situation is classified *before* anything is built: Microsoft-signed
-  installs silently, vendor-signed needs the signer certificate owned in exactly one place, and a
-  vendor-signed **kernel** driver is refused because `TrustedPublisher` satisfies the PnP prompt but never
-  Code Integrity — it would install and then not load. Unsigned is refused outright, with three honest
-  options and no testsigning. Staging is per-INF `pnputil`; uninstall resolves `oemNN.inf` by original name
-  instead of a remembered index.
-- **Script-only / remediation packages** — ESP-safe patterns for fix packages with no installer at all.
-
-### Deliverables
-
-- **HTML dossier — always generated**, uploaded or not. One self-contained file
-  (`Intune-Dossier.html`) built from a fixed template, never hand-assembled: the **Intune dossier** (App
-  Info, return-code map, detection rule, requirements, assignments, driver trust, and a ready-to-paste
-  **Markdown** description for the Company-Portal field) plus a **technical package report** (the three
-  hooks, PSADT cmdlets used, pre-flight and SYSTEM-test results, logo and `.intunewin` verification).
-  Bilingual with a DE/EN toggle, browser-translatable, logo embedded as a data URI.
-- **Real logo only** — finds and downloads the actual application logo (vendor source or Wikimedia
-  Commons), verifies real pixel transparency *and* looks at the image. The PSADT default `AppIcon.png` is
-  blocked by hash.
-- **Start Menu only** — creates Start Menu entries and removes stray desktop icons.
-
-### Intune
-
-- **Access as state, not as a 403** — `Test-PsadtIntuneAccess.ps1` answers before Phase 9 whether the app
-  can upload, assign groups or create policies, and for how long the credential lives. Verified / refused /
-  **unknown** are three different answers, and an offline check never overwrites what was verified before.
-- **Direct upload via Microsoft Graph** *(opt-in)* — pushes the `.intunewin` as a `win32LobApp` (app +
-  logo), self-contained raw Graph, no third-party module. Identity comes from the manifest, so Intune shows
-  the same name and version as the artifact and the dossier. Read-only dry run → confirm → upload. Fills the
-  whole App-information tab, **never deletes an older version** (new versions coexist, with optional
-  supersedence wiring), never auto-assigns categories or notes.
-- **One-time Entra bootstrap** — `New-PsadtEntraApp.ps1` signs in via **WAM**, creates the app, grants and
-  admin-consents the roles and stores the credential: a **certificate** (preferred — nothing secret at rest,
-  JWT client-assertion auth) or a DPAPI-encrypted client secret. Re-running it is normal: it finds the
-  recorded app, merges requested permissions instead of replacing them, and never prompts.
-- **Opt-in group assignment** — creates/reuses Entra security groups by a configured naming scheme and
-  assigns Required / Available / Uninstall. Least-privilege (`Group.Create` + `GroupMember.Read.All`),
-  dry run → confirm, idempotent, and it never deletes a group or another app's assignment.
-- **Certificate + firewall policies** — Custom OMA-URI profiles for `TrustedPublisher` / `TrustedPeople`
-  (the built-in template cannot reach those stores) and settings-catalog firewall-rule policies. Both
-  scripts are self-contained deliverables: they can be copied to a test client that has no skill installed.
-
-### Operations
-
-- **Troubleshooting** — decodes Intune error/HRESULT codes, maps symptoms to root causes, and triages the
-  right log (`AppWorkload.log`, the PSADT session log, `setupapi.dev.log` for drivers).
-- **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 *"update skill"* or *"psadt update"*.
-- **326 Pester tests** over the helper scripts, including drift guards that fail when the docs and the code
-  disagree.
-
-## Requirements
-
-- Windows with PowerShell 5.1+ / PowerShell 7+
-- For the `npx` installer only: **Node 18+** (the skill itself never needs Node)
-- [PSAppDeployToolkit](https://psappdeploytoolkit.com/) v4.x *(installed/updated automatically from the
-  PowerShell Gallery if missing)*
-- [Microsoft Win32 Content Prep Tool](https://github.com/microsoft/Microsoft-Win32-Content-Prep-Tool)
-  *(provisioned automatically)*
-- For the **SYSTEM test loop**: an **elevated** session; the
-  [`Invoke-CommandAs`](https://github.com/mkellerman/Invoke-CommandAs) module is installed automatically
-- For the **direct Intune upload**: an Entra app with the Graph application role
-  `DeviceManagementApps.ReadWrite.All` (admin-consented) — created in one run by
-  `scripts/New-PsadtEntraApp.ps1` (WAM sign-in as Global Admin / Privileged Role Admin, device-code
-  fallback). Check what is actually in place with `scripts/Test-PsadtIntuneAccess.ps1`. Full permission
-  matrix and the manual portal route: `references/app-registration.md`.
-- For **Pester tests**: Pester 5+ (`Install-Module Pester -MinimumVersion 5.0 -Scope CurrentUser`)
-- **Optional (recommended): the [superpowers](https://github.com/obra/superpowers) plugin** — if installed,
-  the research fan-out and the reviewer gate use it. Not required: without it the skill falls back to the
-  native Agent tool and `/code-review`, and nothing in the workflow depends on the plugin.
-
-## Installation
-
-```powershell
-npx psadt-deploy-skill
-```
-
-Installs into `~/.claude/skills/psadt-deploy` and runs the setup doctor. Flags: `--dir <path>` ·
-`--project` (into `./.claude/skills`) · `--ref <branch|tag>` · `--no-setup`. Node 18+ and Windows; the
-installer itself has zero dependencies and the package carries only `bin/` — the skill is fetched from
-GitHub at install time.
-
-Re-running it updates an existing installation, and so does saying *"update skill"* to Claude Code
-(`git pull --ff-only` for a clone, otherwise a branch-zip overwrite of tracked files only — machine-local
-state is never touched).
-
-**Or clone it yourself** — the repo root *is* the skill folder:
-
-```powershell
-git clone https://github.com/pt1987/claude-code-psadt-skill.git "$env:USERPROFILE\.claude\skills\psadt-deploy"
-pwsh "$env:USERPROFILE\.claude\skills\psadt-deploy\scripts\Initialize-PsadtSkill.ps1" -Fix
-```
-
-`npx skills add pt1987/claude-code-psadt-skill` works too, since `SKILL.md` sits in the repository root.
-
-No git on the machine? The installer falls back to the branch tarball and Windows' own `tar.exe`, so the
-one-liner still works.
-
-The skill activates automatically when you ask Claude Code to build an Intune package, or when you work in
-a folder containing `Invoke-AppDeployToolkit.ps1`.
-
-## First-run setup
-
-`scripts/Initialize-PsadtSkill.ps1` (also reachable by saying *"psadt setup"* / *"psadt doctor"*) checks
-every prerequisite in one pass and reports **GREEN / YELLOW / RED**. Every line comes with a concrete fix
-hint, and `-Fix` applies the ones that need no decision (module installs, the tool download, the
-`language.*` defaults, `paths.intuneWinAppUtil`, and migrating a pre-0.19 config). It is idempotent — run it
-as often as you like.
-
-Only four values genuinely need you; the doctor lists them in `.Missing` and takes them via `-Set`:
-
-```powershell
-pwsh scripts/Initialize-PsadtSkill.ps1 -Fix -Set @{
-    'paths.packageRoot' = 'D:\Pakete'; 'paths.outputRoot' = 'D:\Intune'
-    'author.person'     = 'Pat Taubert'; 'author.company' = 'PHAT Consulting'
-}
-```
-
-| Setting | Purpose |
-|---|---|
-| `paths.packageRoot` / `outputRoot` | Where packages are built and where artifacts are written |
-| `paths.intuneWinAppUtil` | Content-prep tool location — filled by `-Fix` |
-| `language.script` / `dossier` | Script language (EN) vs. dossier language (DE for the Company Portal) — filled by `-Fix` |
-| `author.person` / `company` | Stamped into every package's `AppScriptAuthor` |
-| `intune.*` *(optional)* | Direct upload: tenant/client, credential reference, verified roles — written by `New-PsadtEntraApp.ps1` |
-| `intune.groups.*` *(optional)* | Opt-in group assignment (`enabled` / `create` / `membershipType` / `naming`) — guide Appendix M |
-
-### Where the setup is stored
-
-`config.json`, `secret.dpapi` and `tools/` live in the **config home** — `%LOCALAPPDATA%\psadt-deploy\`,
-overridable with `$env:PSADT_DEPLOY_HOME` — **not** in the skill folder, so they survive a `git pull`, a
-re-clone and a re-install. They are machine-local and never committed. A `config.json` from a pre-0.19
-install (beside `scripts/`) keeps working read-only; the doctor flags it and `-Fix` migrates it, renaming
-the originals to `*.migrated` rather than deleting anything.
-
-> DPAPI is bound to the Windows user profile: a re-installed OS invalidates a stored client secret. The
-> doctor and `Test-PsadtIntuneAccess.ps1` both say so, and the fix is one `New-PsadtEntraApp.ps1` run.
-
-## Project structure
-
-```
-psadt-deploy/
-├─ SKILL.md · README.md · CHANGELOG.md · LICENSE
-├─ package.json · bin/install.mjs        the npx installer (Node 18+, zero dependencies)
-├─ scripts/
-│  │  setup + config
-│  ├─ Initialize-PsadtSkill.ps1          setup doctor (Phase 0, GREEN/YELLOW/RED, -Fix/-Set)
-│  ├─ Get-PsadtConfig.ps1                config read + config-home resolver
-│  ├─ Set-PsadtConfig.ps1                config write (deep merge, DPAPI secret, -Remove)
-│  ├─ Get-PsadtModule.ps1                PSADT module (self-heal)
-│  ├─ Get-IntuneWinAppUtil.ps1           content-prep tool (self-heal)
-│  ├─ Get-WinGetModule.ps1               WinGet extension (opt-in)
-│  ├─ Update-PsadtSkill.ps1              self-update from GitHub
-│  │  per-package truth
-│  ├─ Get-PsadtPackageManifest.ps1       manifest read (+ the artifact stem)
-│  ├─ Set-PsadtPackageManifest.ps1       manifest write (merge / append)
-│  │  package generators
-│  ├─ New-MsiPackage.ps1                 MSI packages
-│  ├─ New-BrowserExtensionPackage.ps1    browser-extension force-install (opt-in)
-│  ├─ New-WindowsFeaturePackage.ps1      optional features / capabilities (opt-in)
-│  ├─ New-DriverPackage.ps1              driver packages, pnputil staging (opt-in)
-│  ├─ Get-DriverSignatureInfo.ps1        driver trust classifier (signed? kernel? deployable?)
-│  │  gates + deliverables
-│  ├─ Invoke-PsadtPreflight.ps1          pre-flight GREEN/RED gate (Phase 5, 10 checks)
-│  ├─ Invoke-PsadtSystemTest.ps1         SYSTEM test (Phase 6)
-│  ├─ Invoke-PsadtPackage.ps1            build the .intunewin (Phase 7, named + verified)
-│  ├─ New-PsadtReport.ps1                HTML dossier (Phase 8, always)
-│  │  intune / graph
-│  ├─ New-PsadtEntraApp.ps1              Entra app bootstrap (WAM)
-│  ├─ Get-GraphToken.ps1                 app-only Graph token (cert / DPAPI)
-│  ├─ Test-PsadtIntuneAccess.ps1         access verdict (roles, capabilities, expiry)
-│  ├─ Invoke-IntuneWin32Upload.ps1       direct upload (Phase 9)
-│  ├─ Invoke-IntuneAppAssignment.ps1     group assignment (Phase 10, opt-in)
-│  ├─ New-IntuneTrustedCertPolicy.ps1    Custom OMA-URI cert policy (self-contained)
-│  ├─ New-IntuneFirewallPolicy.ps1       firewall-rule policy (self-contained)
-│  ├─ _GraphCommon.ps1                   shared Graph helpers (retry, errors, token roles)
-│  └─ _GraphInteractive.ps1              shared WAM sign-in
-├─ references/
-│  ├─ PSADTv4-Deployment-Guide.md        Phases 0-12 + Appendices A-Q
-│  ├─ Report-Template.html               the fixed dossier template
-│  └─ app-registration.md                THE Graph permission matrix + manual portal route
-└─ tests/                                Pester suite, 326 tests
-```
-
-Machine-local state lives outside the skill folder:
-
-```
-%LOCALAPPDATA%\psadt-deploy\             ($env:PSADT_DEPLOY_HOME overrides)
-├─ config.json                           settings incl. the optional intune.* block
-├─ secret.dpapi                          DPAPI client secret (only without cert auth)
-└─ tools/                                IntuneWinAppUtil.exe + WinGet module
-```
-
-And per package, next to `Invoke-AppDeployToolkit.ps1`:
-
-```
-psadt-package.json                       identity · gate decisions · research · results · artifacts
-```
-
-## 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 326 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
-against `setupapi.dev.log` on a DEV VM with a real vendor-signed and a real Microsoft-signed driver is
-still open.
-
-## Roadmap
-
-Designed and waiting to be built:
-
-- **Sync finished packages to a GitHub repo** — a setup option (`output.target` = `local` / `git` / `both`)
-  to push the per-app artifacts (`.intunewin`, dossier, detection, logo) to a Git repo instead of, or in
-  addition to, a local folder — versioned and shareable. Will need **Git LFS** for large `.intunewin` files
-  (GitHub's 100 MB per-file limit).
-
-Have a request? Open an issue.
-
-## Contributing
-
-Issues and pull requests are welcome. Keep `SKILL.md`, the references and the docs in **English**. The only
-non-English content is the generated end-user output (the Intune dossier and the Company-Portal app
-description), whose language follows the `language.dossier` config value — **default German**, but
-configurable per machine.
-
-Two conventions worth knowing before you send a patch: generated `.ps1` content is **7-bit ASCII** (the
-pre-flight fails on non-ASCII without a BOM), and anything that lands in a package's output folder must be
-**self-contained** — it gets copied to test clients that have no skill installed.
-
-## License
-
-[MIT](LICENSE) © Patrick Taubert, PHAT Consulting GmbH
-
-## Acknowledgements
-
-- [PSAppDeployToolkit](https://github.com/PSAppDeployToolkit/PSAppDeployToolkit)
-- [Microsoft Win32 Content Prep Tool](https://github.com/microsoft/Microsoft-Win32-Content-Prep-Tool)
-- [`Invoke-CommandAs`](https://github.com/mkellerman/Invoke-CommandAs)
-- README structure inspired by [ComposioHQ/awesome-claude-skills](https://github.com/ComposioHQ/awesome-claude-skills)
-
-## Changelog
-
-Recent releases below; the complete history is in **[CHANGELOG.md](CHANGELOG.md)** (nothing is ever removed
-from either).
-
-### 0.26.7 - 08.09.2026
-- **Fixed: the control plane did not know MSIX exists.** L.8/L.9 landed in 0.26.5, but Gate 1's package-type list
-  never mentioned MSIX — so a `.msix` fell through to "native installer (default)", the one route that is wrong for
-  it, and nothing pointed at the new appendix. Gate 1 now carries **MSIX/AppX** with the decision attached: Intune
-  takes it **natively as a line-of-business app**, so the default is to use that and *not* build a PSADT package;
-  the wrapper is the exception, and L.8 is read first when it is used.
-- **Added `tests/SKILL.Tests.ps1`**, a coherence guard: every appendix SKILL.md points at must exist, and the Gate 1
-  decision must actually route MSIX. Research that the router cannot reach is dead weight — now a test failure.
-### 0.26.6 - 08.09.2026
-- **Fixed: the sandbox host timeout force-killed the viewer, then told you to close the window.** A timed-out run
-  was torn down like a finished one. That **orphans `vmmemWindowsSandbox`** — the Hyper-V compute service owns it,
-  so the host cannot kill it, and it keeps the work folder locked until the next run throws on it — and it removes
-  the only window through which the guest could still be shut down cleanly. The script's own comments name this
-  mechanism as the reason the *guest* must shut itself down; the timeout path did it anyway. A timeout now touches
-  nothing and explains what to close and which knob to raise.
-- **Fixed: the warning claimed 60 seconds while the code waited 180** — a literal duplicating a parameter default.
-  One declared value now feeds both.
-- **Appendix G finding 6 corrected**: "no recovery path" is now scoped to a run killed from *outside* the script.
-### 0.26.5 - 08.09.2026
-- **L.8, new: MSIX/AppX**, verified against Microsoft Learn and against the live cmdlets. MSIX is a two-step
-  model — machine-wide **staging**, then **per-user registration at logon** — and three traps follow from it:
-  **`Add-AppxPackage` as SYSTEM registers the app for the SYSTEM account and reports success** (nobody can launch
-  it), **`Get-AppxPackage` is the wrong detection cmdlet** (finds nothing right after provisioning, so Intune
-  reinstalls forever), and **de-provisioning does not remove the app from existing users** — a complete uninstall
-  needs `Remove-AppxProvisionedPackage` *and* `Remove-AppxPackage -AllUsers`. Plus signing: the certificate
-  Subject must equal the manifest Publisher (so a vendor MSIX cannot just be re-signed), self-signed certs belong
-  in `LocalMachine\TrustedPeople`, and missing timestamping is what makes an expired certificate break installs.
-  And the decision that comes first: **usually don't wrap MSIX in PSADT** — Intune takes it natively.
-- **L.9, new: App-V is not end of life.** The client and sequencer are **no longer deprecated** (fixed extended
-  support, no end date, no extra cost); only the **server components** end in **April 2026**. Also: `-Global` is
-  the device-context switch, and a package in use goes *pending* — a global task applies only after a restart.
-- **The MSIX row in L.2 was misleading and is rewritten**; L.2 gains an App-V row.
-### 0.26.4 - 08.09.2026
-- **L.7, new: Inno Setup and NSIS**, verified against vendor documentation. `/VERYSILENT` **reboots the
-  machine by itself** when a restart is needed — so `/NORESTART` is mandatory, and `/RESTARTEXITCODE=3010`
-  turns the fact into the code Intune already understands. And `Uninstall.exe /S` in NSIS **returns before
-  the uninstall has finished** (it copies itself to temp and detaches), so any verification afterwards races
-  it — `_?=<installdir>` makes it synchronous, must be last, must not be quoted.
-- **Advanced Installer wired into L.1 and L.2**, not just the new L.6 — with a measured fingerprint
-  (`AI_*` custom actions, `aicustact.dll`, `OLDPRODUCTS;AI_NEWERPRODUCTFOUND`).
-### 0.26.3 - 08.09.2026
-- **Appendix L gains three sections**, researched against vendor documentation instead of written from
-  memory: **MSP patches** (the full `/p` matrix, why `/i` and `/p` never combine, and that exit 1642 means
-  *either* "not installed" *or* "wrong patch revision" — so it must not be treated as a blanket success),
-  **WiX Burn bundles** (BundleProviderKey rather than a ProductCode for detection; `/layout` is a Burn
-  action but the bootstrapper decides whether it can be narrowed — the ADK refuses, so an offline layout is
-  always the whole kit), and **Advanced Installer projects** (the `.aip` CLI, a fresh ProductCode per build
-  changing the package identity every time, and the undocumented behaviour that relative paths resolve
-  against the .aip's own location — moving a project between drives breaks it silently).
-### 0.26.2 - 08.09.2026
-- **Fixed: a WHQL driver pack turned the pre-flight red.** `Get-DriverSignatureInfo.ps1` did not strip the
-  inline comment that WHQL packs write after `CatalogFile=` (`; for WHQL certified`), so the catalog never
-  resolved and validly signed drivers classified as `Unsigned` — 6 of 70 INF in a Dell WinPE set, all of
-  whose catalogs were Authenticode-valid and Microsoft-signed. An unquoted `;` now ends the value.
-- **Fixed: `New-MsiPackage.ps1` was the sixth script with the `-File` binder trap.** `-ProcessesToClose
-  'a','b'` arrived as one element, so the scaffold closed no processes at all — silently, while reporting
-  success. 0.25.1 had fixed the other five and missed the generator.
-- **Documented: seven findings from a three-package dependency chain** (Appendix G) and four new
-  anti-patterns (Appendix B), including `msiexec /a` against bundled payload, the `-Include` trap, 8.3
-  short names in path comparisons, and what a service's `%TEMP%` really is on Windows 11.
-### 0.26.1 - 06.09.2026
-- **Fixed: a syntax error in the template silently killed the whole dossier script.** A `
-` inside a JS
-  string literal became a real newline; JavaScript then discards the entire `<script>` block, so the
-  language toggle, all copy buttons and the condensing sticky header died at once — while all 419 tests
-  stayed green, because they only assert on rendered HTML. `tests/Report-Template.Tests.ps1` now runs
-  `node --check` on the script block plus a node-free quote-balance check, both proven against the
-  reintroduced bug.
-- **Changed: every table copies by clicking the row**, replacing the hover icon. Key/value tables give the
-  value, return codes the code, assignments the group name, the SYSTEM-test table the whole row. Clicks on
-  a row's own controls (the foldable detection script) and text selections are left alone. The Markdown
-  description keeps its own copy button.
-
-### 0.26.0 - 06.09.2026
-- **Fixed: the dossier could name a return-code type Intune does not have.** Graph accepts exactly
-  `success`, `softReboot`, `hardReboot`, `retry`, `failed` — there is no `ignored`, yet "Ignored" reached a
-  real dossier because the report rendered a caller-supplied table without validating anything (`Label` was
-  free text, `Cls` was interpolated raw into a `class` attribute). `Label` and `Cls` are now derived from
-  `Type` through a closed switch and cannot be supplied at all; an invalid type throws.
-- **Return codes are sorted and copyable.** Sorted by type in Appendix F.4 order, then numerically — the
-  order the table is verified against and typed into the portal. Each code cell has a copy icon and the
-  section a "copy table" button.
-- **New `Get-PsadtReturnCodes.ps1`: one source of truth for the dossier AND the upload.** Previously two
-  independent literals that agreed by coincidence. `Invoke-IntuneWin32Upload.ps1` gained `-ReturnCodes`, so
-  installer-specific codes finally reach the app instead of only the document, and a new manifest key
-  `research.returnCodes` records them once for both.
-- 419 tests; six new regression guards, each verified to fail on its reintroduced bug.
-
-### 0.25.2 - 06.09.2026
-- **Fixed: a sandbox run left an error dialog on the desktop.** The guest shuts itself down at the end, the
-  RDP-style client loses its session and shows a connection-lost box. The host now disposes of the viewer as
-  soon as the run reports in. The tempting fix — let the host kill the VM instead of shutting the guest down
-  — was measured and is wrong: it orphans the `vmmemWindowsSandbox` worker, which then holds the work folder
-  open for minutes and cannot be killed. Guest shuts down, host closes the window, and the wait is on the VM
-  worker rather than on the client processes.
-
-### 0.25.1 - 06.09.2026
-- **Fixed: array parameters broke under the `-File` binder.** `pwsh script.ps1 -Intents a,b` passes the
-  whole string as ONE element, so `Invoke-IntuneAppAssignment.ps1` rejected a perfectly valid comma-separated
-  intent list with a ValidateSet error naming a value nobody typed. It now splits the list itself and still
-  rejects a real typo by name. `Invoke-PsadtSandboxTest.ps1 -Paths*` had the same trap with a worse outcome —
-  only the first path was asserted and the run still reported GREEN. Six regression tests; suite at 382.
-
-### 0.25.0 - 05.09.2026
-- **New: `Get-PsadtMsiFacts.ps1` reads an MSI in one pass** — identity, signature, SHA256, features with
-  component counts, *decoded* upgrade flags, shortcuts, directories, file versions, registry rows and the
-  Icon table. For an MSI this probe **is** the research: it is what reveals an auto-updater sitting in its
-  own feature (so `ADDLOCAL` replaces post-install cleanup), a `DesktopFeature` you must not install, and
-  `MigrateFeatures` on the upgrade row — the flag that means `ADDLOCAL` alone is not enough. Five
-  regression guards, each verified to fail on its reintroduced bug.
-- **Fixed: the sandbox test left litter and put the evidence in the wrong place.** It kept one work folder
-  per app under the config home forever, and `result.json` plus the PSADT logs lived there with the
-  manifest pointing into a profile directory. Evidence now lands in
-  `<outputRoot>\<Stem>\SandboxTest\` beside the dossier — not in the package folder, which is what
-  IntuneWinAppUtil packs — the logs are recorded in `artifacts.logs[]`, and the scratch is removed.
-  `-KeepWorkFolder` keeps it, and a failed run keeps it automatically.
-- **Fixed: the test suite wrote into the real config home.** It now redirects `PSADT_DEPLOY_HOME` to a temp
-  directory, with a test that asserts it.
-- **Measured:** PuTTY 0.85 packaged with these lessons applied took **13 min 45 s end to end** — versus 75
-  minutes for the Notepad++ run that produced them. The largest single factor: the sandbox test costs zero
-  wall-clock time when started as soon as pre-flight goes GREEN, because packaging and the dossier do not
-  depend on its verdict.
-
-### 0.24.0 - 05.09.2026
-- **New: `Invoke-PsadtSandboxTest.ps1` runs the whole Phase 6 loop in a throwaway Windows Sandbox** —
-  Install, detection, Uninstall, detection, Reinstall, Repair, final Uninstall, every action as
-  `NT AUTHORITY\SYSTEM` via a scheduled task. **No elevation on the host, and the host is never touched**,
-  so the SYSTEM test stops being the step that gets deferred to "a DEV VM later". Every action starts from
-  a machine that has never seen the app, so a pass cannot be an artefact of the previous run. The verdict
-  is keyed on the detection script; package-specific facts go in via `-PathsPresentAfterInstall` /
-  `-PathsAbsentAfterInstall` / `-PathsAbsentAfterUninstall`. Verified end to end on Notepad++ 8.9.8 x64:
-  GREEN, all seven steps, 5 min 58 s.
-- **Why it is a script and not a snippet:** a hand-rolled version hit three bugs that each destroyed a full
-  VM run and each present as a timeout or a null-reference minutes after launch — `echo %ERRORLEVEL%>file`
-  silently becoming the `0>` stdin redirection (empty file, never a number), file existence read as
-  completion, and `[string]$null` still being `$null` in Windows PowerShell 5.1 (an empty detection output
-  is the *normal* result, so the harness crashed because the package was clean). All three now have
-  regression guards that were each verified to fail on the reintroduced bug.
-- Phase 6 in SKILL.md and the guide now lead with the sandbox route; the per-action route stays for apps a
-  VM cannot host. New anti-patterns cover hand-rolled harnesses, debugging through a long job instead of a
-  two-second local check, and "speeding up" the test by disabling Defender or dropping Uninstall/Repair.
-
-### 0.23.1 - 04.09.2026
-- **Fixed: two generators were broken since 0.21.0.** `New-BrowserExtensionPackage.ps1` and
-  `New-WindowsFeaturePackage.ps1` died at run time — the per-run `LogName` change had wedged a statement
-  into the template `Replace(...)` chain, which PowerShell parses as a property assignment with an empty
-  name. Valid syntax, so neither the parse check nor the source-inspecting tests could see it; it surfaced
-  the first time the whole chain ran against a real package. A guard in all four generator test suites now
-  fails on a broken chain, and the guard itself was verified against a broken and a good sample.
-
-### 0.23.0 - 04.09.2026
-- **`npx psadt-deploy-skill`.** One line installs or updates the skill into `~/.claude/skills/psadt-deploy`
-  and runs the setup doctor. Flags `--dir`, `--project`, `--ref`, `--no-setup`. Cloning to exactly the right
-  path by hand was the first thing a new user could get wrong.
-- **Zero dependencies** (Node 18's `fetch` + the `tar.exe` Windows ships). Three acquisition routes:
-  update an existing clone, else `git clone --depth 1`, else the branch tarball — because plenty of managed
-  machines have no git. The npm package ships only `bin/`; the skill comes from GitHub at install time, so
-  a new skill version needs no republish.
-- **The installer never writes the config itself** — it spawns `Set-PsadtConfig.ps1` and
-  `Initialize-PsadtSkill.ps1 -Fix`, because a second config-home implementation in JavaScript would drift
-  from `Get-PsadtConfig`. `Update-PsadtSkill.ps1` now tracks `package.json` and `bin/` so the archive
-  update route stops dropping them. Suite 307 → 326 tests.
-
-### 0.22.0 - 04.09.2026
-- **Third-party drivers.** New `scripts/Get-DriverSignatureInfo.ps1` classifies a driver folder before
-  anything is built — Microsoft-signed / vendor-signed / unsigned — by checking the **catalog** signature
-  rather than the `.sys` (a dual-signed `.sys` reports only its primary signature). New
-  `scripts/New-DriverPackage.ps1` builds the package: pnputil staging per INF, uninstall that resolves
-  `oemNN.inf` by original name instead of a remembered index, `Get-WindowsDriver` detection.
-- **The rule that saves the most time:** a vendor-signed *kernel* driver is RED, not a warning. With Secure
-  Boot on, only Microsoft Dev-Portal-signed kernel drivers load — importing the signer certificate removes
-  the "install device software?" prompt but does nothing for Code Integrity, so the driver installs and
-  then never loads. Unsigned drivers are refused outright, with three honest options and no testsigning.
-- Pre-flight gained a `DriverTrust` check that fires for **any** package shipping an `.inf` (a vendor
-  installer staging a driver is the case nobody declares), the dossier has a driver-trust row, and
-  `New-IntuneTrustedCertPolicy.ps1` is now fully self-contained like the firewall script.
-- New guide **Appendix Q** with the decision tree, pnputil exit codes and the installer-bundled-driver
-  case. Suite 251 → 307 tests.
-
-### 0.21.0 - 04.09.2026
-- **Every package gets a manifest** (`psadt-package.json`): identity, gate decisions, research findings,
-  every phase result and the produced artifacts, in one file per app. The generators write it, every phase
-  script reads and updates it — so an app's version, name and test evidence stop living in someone's head.
-- **The `.intunewin` is named after the app.** New: `<outputRoot>\<Vendor>_<App>_<Version>_<Arch>\<same
-  stem>.intunewin`, produced by the new `scripts/Invoke-PsadtPackage.ps1`. Until now every package came out
-  as `Invoke-AppDeployToolkit.intunewin` — that name reached Intune, and concurrent uploads collided in one
-  shared temp folder. The new script also verifies the archive before calling it a deliverable and refuses
-  an output folder inside the package (which made the tool pack its own previous output).
-- **One PSADT log per run** instead of one ever-growing file:
-  `<Vendor>_<App>_<Version>_<Arch>_<Install|Uninstall|Repair>_<timestamp>.log`. PSADT appends to a fixed
-  name by default, so by the third attempt a failed install was unreadable.
-- **Pre-flight gained two checks:** a missing or incomplete manifest is RED, a pre-0.21 launcher without a
-  per-run log name is a WARN. Report and upload both take their identity from the manifest.
-- Guide: the missing `Phase 6 / 9 / 10` sections now exist, and Appendix E is numbered by phase.
-  Suite 173 → 251 tests.
-
-### 0.20.0 - 04.09.2026
-- **Intune access is state, not a 403.** New `scripts/Test-PsadtIntuneAccess.ps1` answers *before* Phase 9
-  whether the configured app can actually upload, assign groups or create policies — and for how long the
-  credential lives. `TokenOk` and every capability are three-valued: verified / refused / **unknown**,
-  because Graph tokens are opaque by contract and "we could not tell" is not "not permitted". An offline run
-  never overwrites what was verified earlier.
-- **The scripts assert the role they need before their first write** instead of discovering it from a 403
-  mid-upload. Group assignment requires *both* group roles and names the missing half.
-- **`New-PsadtEntraApp.ps1` is re-runnable.** It finds the app by the recorded `clientId`, **merges**
-  requested permissions instead of replacing them (a run without `-IncludeConfigurationManagement` used to
-  silently revoke that role), never prompts, persists what it learned, and only sets `uploadEnabled` once
-  consent is really in place. Older client secrets are counted, never deleted.
-- **Auth failures say what to do:** expired/invalid client secret, unknown app or tenant, Conditional Access
-  block — and an undecryptable DPAPI secret now explains that DPAPI is bound to the Windows user profile.
-- `references/app-registration.md` is now the single permission matrix (app roles → capabilities → how to
-  grant), referenced from the guide instead of duplicated. Suite 128 → 173 tests.
-
-### 0.19.0 - 04.09.2026
-- **Setup doctor: `scripts/Initialize-PsadtSkill.ps1`.** One idempotent script replaces the Phase 0 prose
-  wizard and reports GREEN/YELLOW/RED over 13 prerequisite checks, each with a concrete fix hint. `-Fix`
-  installs the modules, downloads the content-prep tool, fills the EN/DE + tool-path defaults and migrates an
-  old setup; `-Set @{...}` persists your values first; `-Json` / `-JsonPath` for other tooling. `.Missing`
-  lists only the four values a human has to supply (`paths.packageRoot`, `paths.outputRoot`, `author.person`,
-  `author.company`) — never a key the doctor could fill itself.
-- **Config, secret and tools moved to a per-user config home** (`%LOCALAPPDATA%\psadt-deploy\`, override
-  `$env:PSADT_DEPLOY_HOME`) instead of the skill folder, so a `git pull`, re-clone or re-install no longer
-  takes the whole setup with it — and scripts started from an output folder still find their config.
-  `Get-PsadtConfig.ps1` is the single resolver and now returns `.Home` / `.DefaultHome` / `.LegacyInUse`. An
-  old config beside `scripts/` keeps working read-only until `-Fix` migrates it (originals renamed
-  `*.migrated`, nothing deleted).
-- **`Set-PsadtConfig.ps1 -Remove`** deletes dotted keys, so switching credential type can clean up the
-  stale one. **Fixed:** `New-PsadtEntraApp.ps1` reported `<skill>\config.json` even when the config lived
-  elsewhere. Suite 120 → 128 tests.
-
-
-<details>
-<summary><strong>Earlier releases (0.18.1 and older)</strong></summary>
-
-### 0.18.1 - 03.09.2026
-- **Upload: `-MaxRunTimeMinutes`.** `Invoke-IntuneWin32Upload.ps1` can now set
-  `installExperience.maxRunTimeInMinutes` (1–1440); `0` (default) omits the field and keeps the service default
-  of 60 min. Raise it for long-running installs (OS in-place upgrades, large suites) so the IME does not kill them.
-
-### 0.18.0 - 01.07.2026
-- **HanseMerkur corporate design + editorial report redesign.** The dossier/report template is re-themed to the
-  HanseMerkur CD (green brand family on a light mint canvas; Metric font stack with Segoe fallback and no
-  web-font fetch → no CORS console errors on a local `file://` open) and relaid out as an "editorial
-  data-report": flat hairline sections, auto-numbered headings (`01…13`), an at-a-glance KPI band under the hero
-  (version · pre-flight · min OS · arch), and a wider 1600px layout. The detection script is folded behind a
-  collapsed `<details>` (the rule summary stays visible). German report text now uses real umlauts. Fixed the
-  sticky-header flicker (Chrome/Edge scroll-anchoring vs. the condensing hero → `overflow-anchor: none`,
-  Playwright-verified) and removed the redundant hero status pill.
-
-### 0.17.0 - 01.07.2026
-- **install4j fingerprint + behavioral silent-switch verification.** Appendix L.1 now recognises install4j
-  (Java) installers (`com/install4j/runtime`, `exe4j`, `i4jparams.conf`, bundled `jre\`) and records that `/S`
-  is NOT its switch (it hangs on the language dialog) — the unattended switch is `-q`, run elevated. New BINDING
-  rule: a single string match is a hint, not proof; confirm the engine by its definitive fingerprint AND run the
-  silent switch once (timeout+kill, expect exit 0, no dialog) before packaging. Appendix L.3 adds the
-  trademark-sign gotcha (`Name(R)` breaks `-match 'Name'` → tolerant regex); Appendix B adds anti-patterns 13–15.
-  (Driven by an Aperio install4j installer misidentified as NSIS, where `/S` hung on the language dialog.)
-
-### 0.16.0 - 29.06.2026
-- **Dossier auto-sync convention (BINDING)** + report header layout fix. Any change to the package scripts
-  (launcher, Extensions, detection, version/changelog, return codes, re-packaging) now requires regenerating
-  `Intune-Dossier.html` in the same pass; a stale dossier is a defect. The `.pill-lg` status badge caps at 230px
-  and wraps so a long status no longer overlaps the hero title.
-
-### 0.15.2 - 15.06.2026
-- **Follow-up doc fix.** A contradiction sweep after 0.15.1 caught one more stale "Phase 7.5" in
-  `New-PsadtReport.ps1` help (upload is Phase 9); corrected. No other live stale references remain.
-
-### 0.15.1 - 15.06.2026
-- **Generator hardening from a self-review (correctness + security).** All three generators now single-quote-escape
-  values embedded in `$adtSession` literals, so an apostrophe in the App name/vendor/author (e.g. "Bob's App",
-  "L'Oreal") no longer produces an unparseable package; the MSI `-AdditionalArgumentList` / `ProcessesToClose`
-  literals are escaped too (also closing a SYSTEM code-injection path). Detection exit-code drift fixed:
-  `New-MsiPackage.ps1` + the WinGet example now `exit 0` for "not installed" (a non-zero exit reads as a detection
-  error), and a new **pre-flight Detection check** WARNs on a non-zero exit in `Detect*.ps1`. The WSUS bypass in
-  `New-WindowsFeaturePackage.ps1` now saves all prior state before writing and runs inside the `try/finally`, so a
-  partial failure can't leave `UseWUServer=0` permanently. Added input guards (`$Name` path-traversal, `__TOKEN__`
-  leak), MSI `-Author` config fallback + `-InstallerPath` validation. Stale refs fixed (SKILL.md "A-M"->"A-P",
-  `New-PsadtEntraApp.ps1` "Phase 7.5"->"Phase 9").
-
-### 0.15.0 - 15.06.2026
-- **Windows-feature packages (optional features + capabilities / FoD).** New `scripts/New-WindowsFeaturePackage.ps1`
-  — one-call generator that enables Windows **Optional Features** (`Enable-WindowsOptionalFeature`: NetFx3,
-  Hyper-V, WSL, TelnetClient, …) and **Capabilities / Features on Demand** (`Add-WindowsCapability`: RSAT.*,
-  OpenSSH, …) from one typed list, multiple per package. Uninstall reverts (disable/remove); Repair re-enables
-  (idempotent). Reboot surfaces **3010** via `$adtSession.SetExitCode(3010)` (`-NoRestart`); detection treats
-  `EnablePending` as not-yet-done. Content comes from a bundled `-Source` (offline SxS) else Windows Update
-  behind a **temporary** WSUS bypass (`RepairContentServerSource=2`, `UseWUServer=0`) whose exact prior state is
-  restored. Guide **Appendix P**, SKILL.md Gate-1/anti-patterns/ref-lookup. Pre-flight GREEN; helper logic
-  verified against an in-memory registry sim; ASCII-clean.
-
-### 0.14.0 - 15.06.2026
-- **Browser-extension force-install packages (Edge / Chrome / Firefox).** New
-  `scripts/New-BrowserExtensionPackage.ps1` — one-call generator for force-installing browser extensions via
-  enterprise **policy registry keys** (policy-only, no installer, ESP-safe). Multiple extensions per package.
-  Chromium helper computes the **next free `ExtensionInstallForcelist` index** (never hard-codes `1`), dedupes by
-  ID and removes only its own entry (coexistence); Firefox merges into the single `ExtensionSettings` JSON written
-  as **`REG_MULTI_SZ`** (single-line `REG_SZ` is silently ignored — Mozilla bug 1750233). Guide **Appendix O**,
-  SKILL.md Gate-1/anti-patterns/ref-lookup. Pre-flight GREEN; helpers validated against a scratch registry hive;
-  ASCII-clean.
-
-### 0.13.1 - 15.06.2026
-- **Firewall policy body fixed against the live template (verified 201).** `New-IntuneFirewallPolicy.ps1`
-  produced a body Graph rejected (400). Corrected via the **msgraph skill** (not guessed): the group id needs
-  the `{firewallrulename}` token, the program path is the direct child `..._app_filepath`, action values are
-  `_action_type_1`/`_0`, and a template-based policy requires `settingInstanceTemplateReference` per instance +
-  `settingValueTemplateReference` per simple/choice value (profiles collection: instance ref only — a per-value
-  ref is a duplicate). Confirmed by a live **201 Create**; tests assert the references. Mirrored into the
-  MxManagementCenter Output deliverable.
-
-### 0.13.0 - 15.06.2026
-- **Self-contained firewall deliverable (copy-to-client safe).** `scripts/New-IntuneFirewallPolicy.ps1` is now
-  fully self-contained — no dot-sourcing of `_GraphCommon`/`_GraphInteractive`, no skill path; WAM sign-in +
-  policy body builder + console helpers are embedded. It runs on a test client that does **not** have the skill
-  installed (`-Interactive` WAM, or `-GraphToken`). Fixes the "Skill script not found … -SkillRoot" failure when
-  the deliverable was copied to another machine. New **binding SKILL.md convention "Self-contained deliverables"**
-  + a Pester test that enforces it (no dot-source / no skill path / embeds WAM). Test-first per writing-skills.
-
-### 0.12.0 - 15.06.2026
-- **Interactive WAM sign-in for the Intune policy scripts.** `New-IntuneFirewallPolicy.ps1` and
-  `New-IntuneTrustedCertPolicy.ps1` gain `-Interactive` (+ `-TenantId`): delegated sign-in via **WAM**
-  (Windows Web Account Manager) when there is no app registration — **no device code**. The WAM machinery
-  (`Initialize-MsalBroker` / `Get-WamToken` / new `Get-InteractiveGraphToken`) was extracted from
-  `New-PsadtEntraApp.ps1` into a shared `scripts/_GraphInteractive.ps1` (one implementation, no copy-paste
-  drift); the bootstrap now consumes it. The MxManagementCenter firewall deliverable became a thin wrapper
-  over the generic script.
-
-### 0.11.0 - 15.06.2026
-- **Intune firewall-rules policy + app config-management permission.** New `scripts/New-IntuneFirewallPolicy.ps1`
-  (Endpoint Security "Windows Firewall Rules" policy, one program-scoped rule; dry-run / `-Execute` / manual
-  portal fallback) + Pester test. Suppresses the first-run Windows Firewall prompt for apps that listen inbound.
-  New `New-PsadtEntraApp.ps1 -IncludeConfigurationManagement` consents `DeviceManagementConfiguration.ReadWrite.All`
-  (needed by the firewall and trusted-cert policies for `-Execute`).
-
-### 0.10.0 - 15.06.2026
-- **Certificate store deployment (driver-trust / TrustedPublisher).** New `scripts/New-IntuneTrustedCertPolicy.ps1` —
-  a Custom OMA-URI profile that places a certificate into a Windows machine store via the
-  `RootCATrustedCertificates` CSP (the policy-based way to suppress the Windows "install device software?"
-  driver-trust prompt). Guide Appendix N, dossier "Treiber-Zertifikat" row, SKILL.md convention + Pester test.
-
-### 0.9.2 - 12.06.2026
-- **Reconciled a diverged install copy back into the repo.** Fixed `Invoke-PsadtSystemTest.ps1` crashing at
-  param binding under the WinPS 5.1 re-exec (`$SkillRoot` default is now fail-safe, so the SYSTEM Install/
-  Uninstall gate works on a pwsh-7 host). Added per-field copy buttons + a `file://`-safe clipboard to the
-  HTML dossier (`Report-Template.html`, token set unchanged). Added `scripts/New-MsiPackage.ps1` (reusable
-  MSI package generator, `$PSScriptRoot`-relative, ASCII-only) + its Pester test.
-
-### 0.9.1 - 12.06.2026
-- **Applicability/portability drift cleanup** (docs + instructions; no script logic changed). Removed the
-  phantom `test.maxIterations` / `test.endState` config keys from SKILL.md Phase 6 (the cap is a hard count of
-  5 the orchestrator owns); fixed stale "Phase 7.5" -> **Phase 9** in SKILL.md + `app-registration.md`; fixed
-  the README project tree (report **Phase 8**, added the 3 missing scripts `Invoke-PsadtPreflight`,
-  `Invoke-IntuneAppAssignment`, `_GraphCommon`).
-- **`superpowers` downgraded from hard `REQUIRED` to optional/preferred.** The Researcher/Reviewer roles now
-  prefer `superpowers:*` if installed and otherwise fall back to the native Agent tool / `/code-review`; the
-  Requirements list documents it as an optional (recommended) enhancement. The workflow no longer depends on it.
-
-### 0.9.0 - 11.06.2026
-- **Audit cleanup** (quality / content / applicability+compatibility / tests). Highlights: shared
-  `scripts/_GraphCommon.ps1` (de-duplicates the 3 Graph scripts) + **28 new Pester tests** for the previously
-  untested upload/assignment/Entra-app/token scripts (suite now 74); fixed an `Invoke-WithRetry` precedence
-  bug (retried every error 6x) and PS7-fragile throttling reads; the HTML report no longer shows synthetic
-  "passed" rows when no pre-flight/SYSTEM-test results are supplied (neutral "not run") and derives the PSADT
-  version from the installed module; GUID `ValidatePattern` on the MSI codes.
-- **Phase numbering unified** across SKILL.md + guide into one integer scheme **0-12**; every Phase/Appendix
-  cross-reference re-verified. Anti-pattern list trimmed; SYSTEM-test prerequisites, `/beta` drift caveat,
-  rollback step, logging convention, and config help added. Guide `$adtSession` template `1.0.0`->`0.1` +
-  author-from-config; intro appendix index -> A-M.
-
-### 0.8.1 - 11.06.2026
-- **Docs consistency.** Fixed a stale cross-reference in SKILL.md (the guide range said **Appendix A-J** but
-  the guide now runs through **M** — K/L were added in 0.7.0 and M in 0.8.0 without updating it). Restored the
-  **0.5.3** entry that was missing from this README changelog mirror (it was present in `CHANGELOG.md`).
-
-### 0.8.0 - 11.06.2026
-- **Opt-in Entra group assignment, wired end-to-end.** New Phase 10 + `Invoke-IntuneAppAssignment.ps1`:
-  create/reuse Entra security groups by a configured naming scheme (`intune.groups`) and assign the uploaded
-  app (Required / Available / Uninstall). Read-only dry-run → confirm → execute; idempotent; never deletes a
-  group or another app's assignment; ambiguous/duplicate names skipped. Least-privilege roles
-  (`Group.Create` + `GroupMember.Read.All`) via `New-PsadtEntraApp.ps1 -IncludeGroupManagement`. Full
-  reference in **guide Appendix M** (config schema, naming tokens, version-independent default vs `%version%`
-  opt-in, permission model).
-- **Upload min-OS fix.** `-MinWindowsRelease` is now a `ValidateSet` of backend-accepted release IDs
-  (`1607..2004`) — `21H2`/`22H2` are server-rejected and used to kill the upload mid-flight with a Graph
-  `BadRequest`. Fails fast at param binding instead; set a higher minimum in the portal. Guide **H.11**.
-
-### 0.7.5 - 10.06.2026
-- **Honest exit codes + detection (correctness fix).** Removed the dangerous "always `exit 0`" guidance from
-  guide Appendix K — a blanket `exit 0` (or a detection tag written in a `finally`) reports GREEN on failure.
-  New **K.7**: the exit code reflects whether the fix could RUN (couldn't-run -> non-zero; the 64-bit relaunch
-  propagates the child's exit code), detection reflects the real END-STATE (tag only on success), with a
-  per-package decision table; "never block enrollment" is now an explicit ESP-assignment + return-code-mapping
-  choice, not a masked exit code. SKILL.md anti-pattern added.
-
-### 0.7.0 - 10.06.2026
-- **Value-adding extensions.** New `scripts/Invoke-PsadtPreflight.ps1` turns the Phase-5 Reviewer gate into one
-  deterministic `GREEN/RED` tool (encoding/parse/v3-scan/top-level/structure/GUID-to-`-FilePath`), with a Pester
-  suite. New guide **Appendix K** (script-only remediation / fix packages, ESP-safe — the debloat/Cisco pattern)
-  and **Appendix L** (installer technologies + silent switches, a lookup consulted before web research). Expanded
-  error-code catalogue (MSI 1603/1605/1619/1638/1639…, PSADT 60001/60008 + ranges) in guide Appendix A and the
-  SKILL.md troubleshooting table. SKILL.md rewired to point at the pre-flight script and the new appendices.
-
-### 0.6.2 - 10.06.2026
-- **Audit & harden.** Agent-based audit + source-level verification (discarded ~8 false positives). Fixes: the
-  guide's broken `New-ADTTemplate` "Extended scaffold" (passing app metadata params that v4.1.x rejects);
-  the Graph uploader leaving its extracted work dir (with the AES keys in `Detection.xml`) in `%TEMP%` (now
-  `try/finally` cleanup); the report `Notes` default `&middot;` double-escape; the fallback initials-SVG logo
-  now XML-escapes + base64-encodes (no markup injection, with a regression test). Robustness: `Invoke-Graph`
-  429/5xx retry with `Retry-After`; malformed-`config.json` safety in four scripts; WinGet 2-byte header read;
-  symmetric temp cleanup in self-update. Graph request shapes left untouched.
-
-### 0.6.1 - 10.06.2026
-- **Report header flicker fixed** (`references/Report-Template.html`): at widths where the content height met
-  the viewport edge, the vertical scrollbar toggled on/off and the header's `vw`-based `clamp()` padding and
-  `h1` font-size reflowed on every toggle — a wild flicker loop. Reserving the scrollbar gutter
-  (`html { overflow-y: scroll; scrollbar-gutter: stable; }`) keeps the width constant and breaks the loop.
-
-### 0.6.0 - 10.06.2026
-- **SKILL.md slimmed to a control plane** (733 → 244 lines, ~67% fewer tokens) via progressive disclosure:
-  the long inline code moved into the reference guide (new **Appendix I** WinGet + **Appendix J** app-logo),
-  loaded on demand. Intake restructured into **4 decision gates** (researchable facts become stated
-  assumptions, not questions); explicit **sub-agent roles** (Researcher×3 / Builder / Reviewer) with GREEN
-  handoff gates; a single **blockade protocol** for errors. No binding rule or behaviour dropped.
-
-### 0.5.3 - 09.06.2026
-- **Guide code-fences are now English/ASCII.** Anglicized every German comment, string literal and placeholder
-  living **inside** PowerShell/text code fences in the guide (and the inline-code placeholders in the Appendix
-  F.1 table) — snippets get copied verbatim into deployment scripts, where the binding rule is English + 7-bit
-  ASCII. German explanatory **prose** and the **F.2 Company-Portal dossier template** deliberately stay German
-  (legitimate `language.dossier` end-user text). No script/tooling code changed.
-
-### 0.5.2 - 08.06.2026
-- **HTML package report is now always generated** (upload or not) by `scripts/New-PsadtReport.ps1` from the
-  fixed template `references/Report-Template.html`. One self-contained, **bilingual (DE/EN toggle)** document
-  combining the Intune dossier + a technical package report; Fluent-2 styled, sticky shrink header, logo
-  embedded as a data URI, description preview rendered from its Markdown source. New Pester test
-  `tests/New-PsadtReport.Tests.ps1`.
-
-### 0.5.1 - 06.06.2026
-- Self-update now decides by **commit** (git `HEAD` vs `origin/main`, or the GitHub commits-API sha vs a
-  recorded `tooling.skillCommit`) instead of the CHANGELOG version — no more CDN lag / circular version reads.
-- README project-structure tree compacted so it renders without horizontal scroll.
-
-### 0.5.0 - 06.06.2026
-- **Skill self-update** — `scripts/Update-PsadtSkill.ps1` checks GitHub for a newer version, shows what's new,
-  and updates in place on confirmation (`git pull` for a clone, else branch-zip overwrite of tracked files
-  only; `config.json` / `secret.dpapi` / `tools/` preserved). Triggers: *"update skill"*, *"/update-skill"*,
-  *"psadt update"*.
-
-### 0.4.0 - 06.06.2026
-- **WinGet packaging support** (strictly opt-in, never the default) + **certificate-based auth** for the Phase 9
-  upload (no secret at rest) + MSI icon-table logo fallback + device-code first-poll fix. Contributed by
-  **@joakim-i** (PR #4), reviewed and hardened before merge. See [CHANGELOG.md](CHANGELOG.md).
-
-### 0.3.2 - 06.06.2026
-- **Test-before-upload is now a binding gate:** Install + Uninstall must pass the Phase 6 SYSTEM test before
-  any Phase 9 upload. If it can't be run (no elevation / VM), stop before upload and hand back the command.
-
-### 0.3.1 - 06.06.2026
-- `Invoke-IntuneWin32Upload.ps1` gains **`-DetectionScriptPath`** (PowerShell-script detection rule) for
-  EXE / non-MSI installers without a ProductCode (e.g. Vivaldi). Verified live by uploading Vivaldi 8.0.4033.44.
-- Lesson: a *detection* script rule accepts only `ruleType,enforceSignatureCheck,runAs32Bit,scriptContent`
-  (guide Appendix H.2).
-
-### 0.3.0 - 06.06.2026
-- **Direct upload** (`scripts/Invoke-IntuneWin32Upload.ps1`, Phase 9): self-contained raw-Graph
-  `win32LobApp` upload (parse `.intunewin` → token → probe → idempotency → create/update → content → SAS
-  block-blob upload via HttpClient → commit → activate → categories → supersedence). Read-only dry-run by
-  default; `-Execute` to write.
-- **WAM Entra-app bootstrap** (`scripts/New-PsadtEntraApp.ps1`): interactive Windows-broker sign-in (device
-  code fallback), creates the app + admin consent + secret, DPAPI-stored.
-- **App-only token helper** (`scripts/Get-GraphToken.ps1`).
-- **Coexistence-safe versioning:** never deletes an older version; new versions coexist; optional
-  supersedence wiring. **Logo guard:** refuses the PSADT default `AppIcon.png`. Fills the full
-  App-information tab; never auto-assigns category/notes/groups.
-- Fixed the Repair `-FilePath`→`-ProductCode` example; reference guide gains **Appendix H**.
-
-### 0.2.0 - 05.06.2026
-- **Automated SYSTEM test loop** (`scripts/Invoke-PsadtSystemTest.ps1`, Phase 6): install → uninstall →
-  reinstall the package as the SYSTEM account via `Invoke-CommandAs`, with agent-driven auto-fix until
-  green or a max-iteration cap. Opt-in; elevated session required.
-- Phase 8 now prefers `Invoke-CommandAs -AsSystem` for SYSTEM-context testing (PsExec kept as a fallback).
-
-### 0.1.0 - 04.06.2026
-- Initial release: guided PSADT v4 → Intune Win32 lifecycle (intake, autonomous research, scaffolding, all
-  three deployment types, pre-flight checks, packaging, dossier + logo, guided testing, troubleshooting).
-- First-run setup writing a machine-local `config.json` (paths, language, author).
-- Self-healing prerequisites: PSAppDeployToolkit module (PSGallery) and `IntuneWinAppUtil.exe`
-  (auto-download + version check).
-- HTML dossier document with a Markdown app-description block (the Intune description field is
-  Markdown-only).
-- English skill + reference guide; MIT licensed.
-
-</details>
+<h1 align="center">PSADT v4 → Intune Deployment Skill</h1>
+
+<p align="center">
+  <em>A Claude Code skill that drives the full lifecycle of a PowerShell App Deployment Toolkit (PSADT) v4.x Intune Win32 package — from first conversation to a tested, upload-ready <code>.intunewin</code>.</em>
+</p>
+
+<p align="center">
+  <a href="https://github.com/pt1987/claude-code-psadt-skill/actions/workflows/tests.yml"><img src="https://github.com/pt1987/claude-code-psadt-skill/actions/workflows/tests.yml/badge.svg" alt="tests" /></a>
+  <a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-blue.svg?style=flat-square" alt="License: MIT" /></a>
+  <img src="https://img.shields.io/badge/PSADT-v4.x-0a7bbb?style=flat-square" alt="PSADT v4.x" />
+  <img src="https://img.shields.io/badge/Platform-Windows-0078d6?style=flat-square&logo=windows&logoColor=white" alt="Windows" />
+  <img src="https://img.shields.io/badge/Claude%20Code-Skill-d97757?style=flat-square" alt="Claude Code Skill" />
+</p>
+
+<p align="center"><sub><a href="#quick-start">Quick start</a> · <a href="#how-it-works">How it works</a> · <a href="#features">Features</a> · <a href="#first-run-setup">Setup</a> · <a href="#security">Security</a> · <a href="#roadmap">Roadmap</a> · <a href="#changelog">Changelog</a></sub></p>
+
+---
+
+## What is this?
+
+A **Claude Code skill** (not a plugin): a reusable instruction package that teaches the agent how to build,
+package, test, troubleshoot and deploy a **PSADT v4.x Intune Win32 app**. You describe the application; the
+skill runs the workflow — intake, web research, scaffolding, all three deployment types
+(Install / Uninstall / Repair), pre-flight checks, the SYSTEM test, packaging, the dossier, and the
+optional Graph upload.
+
+A skill is a folder with a `SKILL.md` (YAML frontmatter + Markdown instructions), here bundled with
+`scripts/` and `references/`. It loads progressively: the agent sees only the name and description until a
+task makes it relevant, then the full body loads on demand.
+
+<img width="1024" height="254" alt="image" src="https://github.com/user-attachments/assets/7c7931ba-dcae-4476-a648-11115eceb3b5" />
+
+## Quick start
+
+```powershell
+npx psadt-deploy-skill
+```
+
+That installs the skill into `~/.claude/skills/psadt-deploy` and runs the setup doctor, which provisions
+everything it can and names the handful of values only you can supply (see
+[First-run setup](#first-run-setup)). Then open Claude Code in any folder and say what you want:
+
+> *"Create the Win32 Intune package for 7-Zip 24.09"* — or *"package Notepad++ for Intune"*
+
+The skill asks at most **four decision gates** (scope · deployment semantics · SYSTEM-test consent ·
+upload confirmation). Everything else it researches and states as an assumption instead of asking.
+
+## How it works
+
+Twelve phases, each owned by a script rather than by prose, so a step either passed or did not:
+
+| Phase | What happens | Owner |
+|---|---|---|
+| **0** Setup | 13 prerequisite checks, GREEN/YELLOW/RED, `-Fix` provisions | `Initialize-PsadtSkill.ps1` |
+| **1–2** Intake + research | blocker questions as clickable options; parallel research of version, silent switches, Intune pitfalls | agent (gates 1–2) |
+| **3** Scaffold | a generator writes launcher + detection + per-run log name + manifest; `New-ADTTemplate` only when none fits | `New-MsiPackage` · `New-BrowserExtensionPackage` · `New-WindowsFeaturePackage` · `New-DriverPackage` |
+| **4** Customize | all three hooks filled from the research, helpers in the Extensions module | agent |
+| **5** Pre-flight | 10 checks (encoding, AST parse, v3 cmdlets, structure, detection contract, manifest, log name, driver trust …) → GREEN/RED | `Invoke-PsadtPreflight.ps1` |
+| **6** SYSTEM test | installs/uninstalls as **SYSTEM** like the IME does; **binding before any upload** | `Invoke-PsadtSystemTest.ps1` |
+| **7** Package | one command → verified `.intunewin`, named after the app | `Invoke-PsadtPackage.ps1` |
+| **8** Dossier | always, uploaded or not: bilingual self-contained HTML | `New-PsadtReport.ps1` |
+| **9** Upload *(opt-in)* | dry run → confirm → `win32LobApp` via raw Graph | `Invoke-IntuneWin32Upload.ps1` |
+| **10** Assignment *(opt-in)* | create/reuse Entra groups by naming scheme | `Invoke-IntuneAppAssignment.ps1` |
+| **11–12** Test + rollout | DEV-VM cycles, test group, pilot → staged production | agent |
+
+**Everything one app knows lives in `<pkg>\psadt-package.json`** — identity, the decisions taken at the
+gates, the research findings, every phase's result and the artifacts produced. The generators write it,
+every later phase reads and updates it, and pre-flight fails without it. That is what stops two packages of
+the same app from disagreeing about their own version.
+
+Depth lives in `references/` (phases 0–12 + appendices A–Q, one file per domain — see
+`references/README.md`); `SKILL.md` stays the
+control plane.
+
+## Features
+
+### Setup and prerequisites
+
+- **Setup doctor** — one idempotent script checks PowerShell 7, Windows PowerShell 5.1, elevation, git,
+  PSAppDeployToolkit, the content-prep tool, `Invoke-CommandAs`, Pester, the config, a legacy config, the
+  skill tree, a pending update and the Intune credentials. Each line carries a concrete fix; `-Fix` applies
+  the ones that need no decision.
+- **Self-healing prerequisites** — installs the PSAppDeployToolkit module from the PowerShell Gallery and
+  downloads `IntuneWinAppUtil.exe`, keeping both current against their official sources.
+- **Config outside the skill folder** — `config.json`, `secret.dpapi` and `tools/` live in
+  `%LOCALAPPDATA%\psadt-deploy\` (override: `$env:PSADT_DEPLOY_HOME`), so a `git pull`, a re-clone or a
+  re-install can no longer take your setup with it. A pre-0.19 config keeps working and is migrated on
+  request, never deleted.
+- **One-line install** — `npx psadt-deploy-skill` (Node 18+, zero dependencies) does clone-or-update plus
+  the doctor run in one step.
+
+### Build and verify
+
+- **Guided intake** — the blocker questions up front as clickable options, pre-filled with researched
+  defaults (app, latest version, installer type, package type).
+- **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
+  Company-Portal uninstalls actually work.
+- **Pre-flight gate** — encoding/BOM, AST parse, launcher acid test, v3-cmdlet scan, hook structure,
+  detection-script contract, the package manifest, the per-run log name and driver trust. GREEN or RED,
+  with the failing file named.
+- **Automated SYSTEM test loop** *(opt-in, binding before upload)* — installs, uninstalls and reinstalls as
+  the **SYSTEM** account via `Invoke-CommandAs`, mirroring the Intune Management Extension; reads the fresh
+  session log and the detection result, and hands back a structured verdict for the fix-and-retry loop.
+  Needs an elevated session; belongs on a VM with a snapshot.
+- **Deterministic packaging** — `<outputRoot>\<Vendor>_<App>_<Version>_<Arch>\<same stem>.intunewin`,
+  verified after the fact (`Detection.xml`, `SetupFile`, size, SHA256), with the detection script and the
+  real logo beside it. It refuses an output folder inside the package, and never deletes a foreign
+  `.intunewin` it finds there.
+- **One PSADT log per run** — `<Vendor>_<App>_<Version>_<Arch>_<Install|Uninstall|Repair>_<timestamp>.log`
+  instead of every run of every version appending to one unreadable file.
+
+### Package types
+
+The app's **native installer is always the default**. Everything else is opt-in and only on request:
+
+- **MSI / EXE** — the ordinary case, via `New-MsiPackage.ps1` or a hand-filled scaffold.
+- **WinGet** — the full `PSAppDeployToolkit.WinGet` lifecycle: the extension module self-heals into the
+  package, the Package ID is discovered with `Find-ADTWinGetPackage`, hooks use `*-ADTWinGet*`
+  (`-Scope Machine`). Never selected on its own initiative.
+- **Browser extensions** — force-install via the Edge/Chrome/Firefox policy keys (including the Firefox
+  `REG_MULTI_SZ` trap), with selective removal on uninstall.
+- **Windows features** — `Enable-WindowsOptionalFeature` and `Add-WindowsCapability`, offline source or a
+  temporary WSUS bypass that is restored afterwards, `EnablePending` handled honestly.
+- **Third-party drivers** — the trust situation is classified *before* anything is built: Microsoft-signed
+  installs silently, vendor-signed needs the signer certificate owned in exactly one place, and a
+  vendor-signed **kernel** driver is refused because `TrustedPublisher` satisfies the PnP prompt but never
+  Code Integrity — it would install and then not load. Unsigned is refused outright, with three honest
+  options and no testsigning. Staging is per-INF `pnputil`; uninstall resolves `oemNN.inf` by original name
+  instead of a remembered index.
+- **Script-only / remediation packages** — ESP-safe patterns for fix packages with no installer at all.
+
+### Deliverables
+
+- **HTML dossier — always generated**, uploaded or not. One self-contained file
+  (`Intune-Dossier.html`) built from a fixed template, never hand-assembled: the **Intune dossier** (App
+  Info, return-code map, detection rule, requirements, assignments, driver trust, and a ready-to-paste
+  **Markdown** description for the Company-Portal field) plus a **technical package report** (the three
+  hooks, PSADT cmdlets used, pre-flight and SYSTEM-test results, logo and `.intunewin` verification).
+  Bilingual with a DE/EN toggle, browser-translatable, logo embedded as a data URI.
+- **Real logo only** — finds and downloads the actual application logo (vendor source or Wikimedia
+  Commons), verifies real pixel transparency *and* looks at the image. The PSADT default `AppIcon.png` is
+  blocked by hash.
+- **Start Menu only** — creates Start Menu entries and removes stray desktop icons.
+
+### Intune
+
+- **Access as state, not as a 403** — `Test-PsadtIntuneAccess.ps1` answers before Phase 9 whether the app
+  can upload, assign groups or create policies, and for how long the credential lives. Verified / refused /
+  **unknown** are three different answers, and an offline check never overwrites what was verified before.
+- **Direct upload via Microsoft Graph** *(opt-in)* — pushes the `.intunewin` as a `win32LobApp` (app +
+  logo), self-contained raw Graph, no third-party module. Identity comes from the manifest, so Intune shows
+  the same name and version as the artifact and the dossier. Read-only dry run → confirm → upload. Fills the
+  whole App-information tab, **never deletes an older version** (new versions coexist, with optional
+  supersedence wiring), never auto-assigns categories or notes.
+- **One-time Entra bootstrap** — `New-PsadtEntraApp.ps1` signs in via **WAM**, creates the app, grants and
+  admin-consents the roles and stores the credential: a **certificate** (preferred — nothing secret at rest,
+  JWT client-assertion auth) or a DPAPI-encrypted client secret. Re-running it is normal: it finds the
+  recorded app, merges requested permissions instead of replacing them, and never prompts.
+- **Opt-in group assignment** — creates/reuses Entra security groups by a configured naming scheme and
+  assigns Required / Available / Uninstall. Least-privilege (`Group.Create` + `GroupMember.Read.All`),
+  dry run → confirm, idempotent, and it never deletes a group or another app's assignment.
+- **Certificate + firewall policies** — Custom OMA-URI profiles for `TrustedPublisher` / `TrustedPeople`
+  (the built-in template cannot reach those stores) and settings-catalog firewall-rule policies. Both
+  scripts are self-contained deliverables: they can be copied to a test client that has no skill installed.
+
+### Operations
+
+- **Troubleshooting** — decodes Intune error/HRESULT codes, maps symptoms to root causes, and triages the
+  right log (`AppWorkload.log`, the PSADT session log, `setupapi.dev.log` for drivers).
+- **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
+  disagree.
+
+## Requirements
+
+- Windows with PowerShell 5.1+ / PowerShell 7+
+- For the `npx` installer only: **Node 18+** (the skill itself never needs Node)
+- [PSAppDeployToolkit](https://psappdeploytoolkit.com/) v4.x *(installed/updated automatically from the
+  PowerShell Gallery if missing)*
+- [Microsoft Win32 Content Prep Tool](https://github.com/microsoft/Microsoft-Win32-Content-Prep-Tool)
+  *(provisioned automatically)*
+- For the **SYSTEM test loop**: an **elevated** session; the
+  [`Invoke-CommandAs`](https://github.com/mkellerman/Invoke-CommandAs) module is installed automatically
+- For the **direct Intune upload**: an Entra app with the Graph application role
+  `DeviceManagementApps.ReadWrite.All` (admin-consented) — created in one run by
+  `scripts/New-PsadtEntraApp.ps1` (WAM sign-in as Global Admin / Privileged Role Admin, device-code
+  fallback). Check what is actually in place with `scripts/Test-PsadtIntuneAccess.ps1`. Full permission
+  matrix and the manual portal route: `references/app-registration.md`.
+- For **Pester tests**: Pester 5+ (`Install-Module Pester -MinimumVersion 5.0 -Scope CurrentUser`)
+- **Optional (recommended): the [superpowers](https://github.com/obra/superpowers) plugin** — if installed,
+  the research fan-out and the reviewer gate use it. Not required: without it the skill falls back to the
+  native Agent tool and `/code-review`, and nothing in the workflow depends on the plugin.
+
+## Installation
+
+```powershell
+npx psadt-deploy-skill
+```
+
+Installs the **newest release** into `~/.claude/skills/psadt-deploy` and runs the setup doctor. Flags:
+`--dir <path>` · `--project` (into `./.claude/skills`) · `--ref <tag|branch>` · `--no-setup`. Node 18+ and
+Windows; the installer itself has zero dependencies and the package carries only `bin/` — the skill is
+fetched from GitHub at install time.
+
+### Which version you get
+
+The default is the newest **release tag**, not `main`. This skill registers an Entra application with
+admin consent and writes to an Intune tenant; installing whatever last landed on `main` is not a
+defensible default for that.
+
+```powershell
+npx psadt-deploy-skill                 # newest release (default)
+npx psadt-deploy-skill --ref v0.26.7   # pin an exact release
+npx psadt-deploy-skill --ref main      # the development branch, deliberately
+```
+
+**For managed environments:** pin a tag, read the diff between it and the next one before moving, then
+lift the pin. Releases are tagged `vX.Y.Z` and match the [Changelog](#changelog); tags exist from
+**v0.24.0** onward — earlier versions predate the current history and cannot be tagged retroactively.
+
+Re-running the installer updates an existing installation, and so does saying *"psadt update"* to Claude
+Code. What counts as an update depends on what you installed: on a **pinned release** it is the next
+release tag — unreleased work on `main` is deliberately invisible, because that is what pinning means. On
+a **branch** installation it is the next commit, as before. Either way the update overwrites tracked
+repository files only; `config.json`, `secret.dpapi` and `tools/` are never touched.
+
+**Or clone it yourself** — the repo root *is* the skill folder:
+
+```powershell
+git clone https://github.com/pt1987/claude-code-psadt-skill.git "$env:USERPROFILE\.claude\skills\psadt-deploy"
+pwsh "$env:USERPROFILE\.claude\skills\psadt-deploy\scripts\Initialize-PsadtSkill.ps1" -Fix
+```
+
+`npx skills add pt1987/claude-code-psadt-skill` works too, since `SKILL.md` sits in the repository root.
+
+No git on the machine? The installer falls back to the GitHub tarball and Windows' own `tar.exe`, so the
+one-liner still works — including with `--ref <tag>`, which is the combination a locked-down machine
+actually needs.
+
+The skill activates automatically when you ask Claude Code to build an Intune package, or when you work in
+a folder containing `Invoke-AppDeployToolkit.ps1`.
+
+### What is deliberately not in the skill frontmatter
+
+`SKILL.md` declares `name`, `description` and `license`, and nothing else. The omissions are choices, not
+oversights:
+
+- **`paths`** would look like the right way to express "activates in a folder containing
+  `Invoke-AppDeployToolkit.ps1`". It is the opposite: the field *limits* activation to files matching the
+  globs. Setting it would switch the skill off for the most common request there is — packaging an app in
+  an empty folder, where `Invoke-AppDeployToolkit.ps1` does not exist yet because Phase 3 is what creates
+  it. The folder case is covered by the last sentence of the description instead.
+- **`allowed-tools`** grants tools up front; it does not restrict them. For a skill that installs software
+  as SYSTEM and writes to a tenant, being asked per call is the point. See [`SECURITY.md`](SECURITY.md).
+- **`metadata.version`** is ignored by Claude Code, and the version already lives in `CHANGELOG.md`,
+  `package.json` (kept in sync by a test) and on the website. A fourth place to forget on release day, for
+  no behaviour, is not worth it.
+- **`shell`** only matters for `!` command injection in `SKILL.md`, which this skill does not use — and a
+  failing `!` command aborts the *entire* skill invocation, so an `Initialize-PsadtSkill` call wired up that
+  way would be a single point of failure for every packaging request.
+- **`context: fork` / `agent`** would isolate the skill in a subagent. It orchestrates its own sub-agents
+  and needs the main context to hold the decision gates.
+
+## First-run setup
+
+`scripts/Initialize-PsadtSkill.ps1` (also reachable by saying *"psadt setup"* / *"psadt doctor"*) checks
+every prerequisite in one pass and reports **GREEN / YELLOW / RED**. Every line comes with a concrete fix
+hint, and `-Fix` applies the ones that need no decision (module installs, the tool download, the
+`language.*` defaults, `paths.intuneWinAppUtil`, and migrating a pre-0.19 config). It is idempotent — run it
+as often as you like.
+
+Only four values genuinely need you; the doctor lists them in `.Missing` and takes them via `-Set`:
+
+```powershell
+pwsh scripts/Initialize-PsadtSkill.ps1 -Fix -Set @{
+    'paths.packageRoot' = 'D:\Pakete'; 'paths.outputRoot' = 'D:\Intune'
+    'author.person'     = 'Pat Taubert'; 'author.company' = 'PHAT Consulting'
+}
+```
+
+| Setting | Purpose |
+|---|---|
+| `paths.packageRoot` / `outputRoot` | Where packages are built and where artifacts are written |
+| `paths.intuneWinAppUtil` | Content-prep tool location — filled by `-Fix` |
+| `language.script` / `dossier` | Script language (EN) vs. dossier language (DE for the Company Portal) — filled by `-Fix` |
+| `author.person` / `company` | Stamped into every package's `AppScriptAuthor` |
+| `intune.*` *(optional)* | Direct upload: tenant/client, credential reference, verified roles — written by `New-PsadtEntraApp.ps1` |
+| `intune.groups.*` *(optional)* | Opt-in group assignment (`enabled` / `create` / `membershipType` / `naming`) — guide Appendix M |
+
+### Where the setup is stored
+
+`config.json`, `secret.dpapi` and `tools/` live in the **config home** — `%LOCALAPPDATA%\psadt-deploy\`,
+overridable with `$env:PSADT_DEPLOY_HOME` — **not** in the skill folder, so they survive a `git pull`, a
+re-clone and a re-install. They are machine-local and never committed. A `config.json` from a pre-0.19
+install (beside `scripts/`) keeps working read-only; the doctor flags it and `-Fix` migrates it, renaming
+the originals to `*.migrated` rather than deleting anything.
+
+> DPAPI is bound to the Windows user profile: a re-installed OS invalidates a stored client secret. The
+> doctor and `Test-PsadtIntuneAccess.ps1` both say so, and the fix is one `New-PsadtEntraApp.ps1` run.
+
+## Project structure
+
+```
+psadt-deploy/
+├─ SKILL.md · README.md · CHANGELOG.md · SECURITY.md · LICENSE
+├─ package.json · bin/install.mjs        the npx installer (Node 18+, zero dependencies)
+├─ scripts/
+│  │  setup + config
+│  ├─ Initialize-PsadtSkill.ps1          setup doctor (Phase 0, GREEN/YELLOW/RED, -Fix/-Set)
+│  ├─ Get-PsadtConfig.ps1                config read + config-home resolver
+│  ├─ Set-PsadtConfig.ps1                config write (deep merge, DPAPI secret, -Remove)
+│  ├─ Get-PsadtModule.ps1                PSADT module (self-heal)
+│  ├─ Get-IntuneWinAppUtil.ps1           content-prep tool (self-heal)
+│  ├─ Get-WinGetModule.ps1               WinGet extension (opt-in)
+│  ├─ Update-PsadtSkill.ps1              self-update from GitHub
+│  │  per-package truth
+│  ├─ Get-PsadtPackageManifest.ps1       manifest read (+ the artifact stem)
+│  ├─ Set-PsadtPackageManifest.ps1       manifest write (merge / append)
+│  │  package generators
+│  ├─ New-MsiPackage.ps1                 MSI packages
+│  ├─ New-BrowserExtensionPackage.ps1    browser-extension force-install (opt-in)
+│  ├─ New-WindowsFeaturePackage.ps1      optional features / capabilities (opt-in)
+│  ├─ New-DriverPackage.ps1              driver packages, pnputil staging (opt-in)
+│  ├─ Get-DriverSignatureInfo.ps1        driver trust classifier (signed? kernel? deployable?)
+│  │  gates + deliverables
+│  ├─ Invoke-PsadtPreflight.ps1          pre-flight GREEN/RED gate (Phase 5, 10 checks)
+│  ├─ Invoke-PsadtSystemTest.ps1         SYSTEM test (Phase 6)
+│  ├─ Invoke-PsadtPackage.ps1            build the .intunewin (Phase 7, named + verified)
+│  ├─ New-PsadtReport.ps1                HTML dossier (Phase 8, always)
+│  │  intune / graph
+│  ├─ New-PsadtEntraApp.ps1              Entra app bootstrap (WAM)
+│  ├─ Get-GraphToken.ps1                 app-only Graph token (cert / DPAPI)
+│  ├─ Test-PsadtIntuneAccess.ps1         access verdict (roles, capabilities, expiry)
+│  ├─ Invoke-IntuneWin32Upload.ps1       direct upload (Phase 9)
+│  ├─ Invoke-IntuneAppAssignment.ps1     group assignment (Phase 10, opt-in)
+│  ├─ New-IntuneTrustedCertPolicy.ps1    Custom OMA-URI cert policy (self-contained)
+│  ├─ New-IntuneFirewallPolicy.ps1       firewall-rule policy (self-contained)
+│  ├─ _GraphCommon.ps1                   shared Graph helpers (retry, errors, token roles)
+│  └─ _GraphInteractive.ps1              shared WAM sign-in
+├─ references/
+│  ├─ 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
+│  ├─ Report-Template.html               the fixed dossier template
+│  └─ app-registration.md                THE Graph permission matrix + manual portal route
+└─ tests/                                Pester suite, 441 tests
+```
+
+Machine-local state lives outside the skill folder:
+
+```
+%LOCALAPPDATA%\psadt-deploy\             ($env:PSADT_DEPLOY_HOME overrides)
+├─ config.json                           settings incl. the optional intune.* block
+├─ secret.dpapi                          DPAPI client secret (only without cert auth)
+└─ tools/                                IntuneWinAppUtil.exe + WinGet module
+```
+
+And per package, next to `Invoke-AppDeployToolkit.ps1`:
+
+```
+psadt-package.json                       identity · gate decisions · research · results · artifacts
+```
+
+## 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.
+
+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
+against `setupapi.dev.log` on a DEV VM with a real vendor-signed and a real Microsoft-signed driver is
+still open.
+
+## Security
+
+This skill installs software as SYSTEM, researches on the open web, and writes to an Intune tenant
+through an Entra app with admin consent. [`SECURITY.md`](SECURITY.md) states that risk surface next to
+the control that already covers each part of it — the dry-run-before-execute rule, the three-valued
+access check, never-delete, role assertion before the first write, certificate before DPAPI secret,
+the config home outside the skill folder, and the self-containment rule for anything that ships to a
+test client. Each control names the file that implements it and the test that enforces it, so a review
+can check the claims rather than take them.
+
+Two deliberate non-features are explained there as well: the skill does **not** declare
+`allowed-tools` (that field pre-approves tools, it does not restrict them), and content fetched during
+research is treated as data, never as instructions — see
+[`references/research-trust.md`](references/research-trust.md).
+
+## Roadmap
+
+Designed and waiting to be built:
+
+- **Sync finished packages to a GitHub repo** — a setup option (`output.target` = `local` / `git` / `both`)
+  to push the per-app artifacts (`.intunewin`, dossier, detection, logo) to a Git repo instead of, or in
+  addition to, a local folder — versioned and shareable. Will need **Git LFS** for large `.intunewin` files
+  (GitHub's 100 MB per-file limit).
+
+Have a request? Open an issue.
+
+## Contributing
+
+Issues and pull requests are welcome. Keep `SKILL.md`, the references and the docs in **English**. The only
+non-English content is the generated end-user output (the Intune dossier and the Company-Portal app
+description), whose language follows the `language.dossier` config value — **default German**, but
+configurable per machine.
+
+Two conventions worth knowing before you send a patch: generated `.ps1` content is **7-bit ASCII** (the
+pre-flight fails on non-ASCII without a BOM), and anything that lands in a package's output folder must be
+**self-contained** — it gets copied to test clients that have no skill installed.
+
+## License
+
+[MIT](LICENSE) © Patrick Taubert, PHAT Consulting GmbH
+
+## Acknowledgements
+
+- [PSAppDeployToolkit](https://github.com/PSAppDeployToolkit/PSAppDeployToolkit)
+- [Microsoft Win32 Content Prep Tool](https://github.com/microsoft/Microsoft-Win32-Content-Prep-Tool)
+- [`Invoke-CommandAs`](https://github.com/mkellerman/Invoke-CommandAs)
+- README structure inspired by [ComposioHQ/awesome-claude-skills](https://github.com/ComposioHQ/awesome-claude-skills)
+
+## Changelog
+
+Recent releases below; the complete history is in **[CHANGELOG.md](CHANGELOG.md)** (nothing is ever removed
+from either).
+
+### 0.27.1 - 10.09.2026
+- **Fixed: das Dossier erfand Fakten über das Paket und druckte sie als Aussage.** Beim Paketieren zweier
+  echter Apps zum Test von 0.27.0 aufgefallen. Ohne `-Metadata` behauptete der Report `_Beschreibung folgt._`
+  als Company-Portal-Text — der wird unverändert nach Intune übernommen und liest sich wie ein fertiges Feld —
+  sowie `Start-ADTMsiProcess` und „Nutzerdaten bleiben erhalten" als Hook-Inhalt, für welches Paket auch immer
+  gerade berichtet wurde. Ein WinMerge-Paket, das ausschließlich `Start-ADTProcess` mit Inno-Switches aufruft,
+  wurde so viermal mit einem Cmdlet beschrieben, das es nie verwendet. Nichts kennzeichnete das als Vermutung.
+- **Hooks und Cmdlet-Liste werden jetzt per AST aus dem echten Launcher gelesen**, je `*-ADTDeployment`-Funktion.
+  Kein Launcher vorhanden: „nicht ermittelbar" statt einer plausiblen Liste. Ein explizites `-Metadata` gewinnt
+  weiterhin.
+- **Eine fehlende Beschreibung warnt und wird sichtbar markiert — und wird bei `decisions.upload = true`
+  verweigert**, in derselben Form wie das bestehende SYSTEM-Test-Gate. `-AllowMissingDescription` ist der
+  bewusste, sichtbare Ausweg.
+- **Der Header-Status wird aus den Belegen abgeleitet** statt auf „Upload-bereit · getestet" zu defaulten.
+- **SKILL.md Phase 8** sagt jetzt, dass die Beschreibung Pflicht ist; vorher stand dort nur, wie sie zu
+  formatieren wäre. Suite 474 → 484.
+### 0.27.0 - 10.09.2026
+- **Fixed: after auto-compaction, half of SKILL.md was gone.** Claude Code re-attaches only the **first
+  5000 tokens** of an invoked skill after a summary. SKILL.md was ~10 10900, so the cut fell at line 198 — the
+  middle of Phase 2. In exactly the sessions long enough to compact, the skill lost Phases 3–12, the whole
+  troubleshooting table, every anti-pattern and the reference map. The fix is **ordering, not size**: the
+  operating mode, the four gates, the conventions and Phases 0–6 now sit ahead of the cut, and Phase 6 ends
+  at byte 17 457 of a 17 500-byte budget — with a test that fails if it ever crosses back.
+- **Fixed: `--ref <tag>` returned HTTP 404 on the tarball route.** The installer built
+  `tar.gz/refs/heads/<ref>`, and `refs/heads` only resolves *branches* — so pinning worked with git and failed
+  on exactly the machines without it, which are the ones most likely to need a pinned release.
+  `Update-PsadtSkill.ps1` had the same latent bug in its archive path.
+- **Fixed: a failed install exited 127 instead of 1**, with a libuv assertion after the error message. A
+  mistyped `--ref` printed a correct explanation and then looked like a crash.
+- **Changed: the default install is the newest release tag, not `main`.** This skill registers an Entra app
+  with admin consent and writes to a tenant; installing whatever last landed on a branch is not a defensible
+  default for that. `--ref main` and `--ref v0.27.0` both remain. The update check now distinguishes a
+  release-pinned installation (counts *releases* behind) from one following a branch.
+- **Changed: the 2942-line deployment guide is now nineteen files**, one per domain, with
+  `references/README.md` as the map. Section numbering is unchanged, so every "App. L.1" and "Phase 6.2"
+  still resolves.
+- **Changed (behaviour): Phase 11 no longer re-runs Phase 6.** Phase 6 answers *does the package work* (the
+  gate, in a throwaway Sandbox); Phase 11 answers *does the delivery work* (Intune test group, real device,
+  `AppWorkload.log`). A package that passes 6 and fails 11 now tells you something.
+- **Changed: `"update skill"` is gone from the description** — un-namespaced, it made this skill answer for
+  every other updatable skill on the machine. `"psadt update"` stays.
+- **Added `SECURITY.md`** — the risk surface next to the control that covers each part of it, each naming the
+  file and the test that implement it.
+- **Added: researched content is data, never instructions** (`references/research-trust.md`) — Phase 2
+  researches on the open web and the result runs as SYSTEM. The install4j case generalised.
+- **Added three guards and CI**: rule anchors proving no binding rule was lost in the move, a two-directional
+  doc cross-reference check that also reads `scripts/`, a context-budget test, and the suite on a clean
+  Windows runner for every push. Suite 441 → 474.
+- **Added `evals/`** — 20 trigger and behaviour cases. Not yet run: `claude plugin eval` is in early access.
+### 0.26.7 - 08.09.2026
+- **Fixed: the control plane did not know MSIX exists.** L.8/L.9 landed in 0.26.5, but Gate 1's package-type list
+  never mentioned MSIX — so a `.msix` fell through to "native installer (default)", the one route that is wrong for
+  it, and nothing pointed at the new appendix. Gate 1 now carries **MSIX/AppX** with the decision attached: Intune
+  takes it **natively as a line-of-business app**, so the default is to use that and *not* build a PSADT package;
+  the wrapper is the exception, and L.8 is read first when it is used.
+- **Added `tests/SKILL.Tests.ps1`**, a coherence guard: every appendix SKILL.md points at must exist, and the Gate 1
+  decision must actually route MSIX. Research that the router cannot reach is dead weight — now a test failure.
+### 0.26.6 - 08.09.2026
+- **Fixed: the sandbox host timeout force-killed the viewer, then told you to close the window.** A timed-out run
+  was torn down like a finished one. That **orphans `vmmemWindowsSandbox`** — the Hyper-V compute service owns it,
+  so the host cannot kill it, and it keeps the work folder locked until the next run throws on it — and it removes
+  the only window through which the guest could still be shut down cleanly. The script's own comments name this
+  mechanism as the reason the *guest* must shut itself down; the timeout path did it anyway. A timeout now touches
+  nothing and explains what to close and which knob to raise.
+- **Fixed: the warning claimed 60 seconds while the code waited 180** — a literal duplicating a parameter default.
+  One declared value now feeds both.
+- **Appendix G finding 6 corrected**: "no recovery path" is now scoped to a run killed from *outside* the script.
+### 0.26.5 - 08.09.2026
+- **L.8, new: MSIX/AppX**, verified against Microsoft Learn and against the live cmdlets. MSIX is a two-step
+  model — machine-wide **staging**, then **per-user registration at logon** — and three traps follow from it:
+  **`Add-AppxPackage` as SYSTEM registers the app for the SYSTEM account and reports success** (nobody can launch
+  it), **`Get-AppxPackage` is the wrong detection cmdlet** (finds nothing right after provisioning, so Intune
+  reinstalls forever), and **de-provisioning does not remove the app from existing users** — a complete uninstall
+  needs `Remove-AppxProvisionedPackage` *and* `Remove-AppxPackage -AllUsers`. Plus signing: the certificate
+  Subject must equal the manifest Publisher (so a vendor MSIX cannot just be re-signed), self-signed certs belong
+  in `LocalMachine\TrustedPeople`, and missing timestamping is what makes an expired certificate break installs.
+  And the decision that comes first: **usually don't wrap MSIX in PSADT** — Intune takes it natively.
+- **L.9, new: App-V is not end of life.** The client and sequencer are **no longer deprecated** (fixed extended
+  support, no end date, no extra cost); only the **server components** end in **April 2026**. Also: `-Global` is
+  the device-context switch, and a package in use goes *pending* — a global task applies only after a restart.
+- **The MSIX row in L.2 was misleading and is rewritten**; L.2 gains an App-V row.
+### 0.26.4 - 08.09.2026
+- **L.7, new: Inno Setup and NSIS**, verified against vendor documentation. `/VERYSILENT` **reboots the
+  machine by itself** when a restart is needed — so `/NORESTART` is mandatory, and `/RESTARTEXITCODE=3010`
+  turns the fact into the code Intune already understands. And `Uninstall.exe /S` in NSIS **returns before
+  the uninstall has finished** (it copies itself to temp and detaches), so any verification afterwards races
+  it — `_?=<installdir>` makes it synchronous, must be last, must not be quoted.
+- **Advanced Installer wired into L.1 and L.2**, not just the new L.6 — with a measured fingerprint
+  (`AI_*` custom actions, `aicustact.dll`, `OLDPRODUCTS;AI_NEWERPRODUCTFOUND`).
+### 0.26.3 - 08.09.2026
+- **Appendix L gains three sections**, researched against vendor documentation instead of written from
+  memory: **MSP patches** (the full `/p` matrix, why `/i` and `/p` never combine, and that exit 1642 means
+  *either* "not installed" *or* "wrong patch revision" — so it must not be treated as a blanket success),
+  **WiX Burn bundles** (BundleProviderKey rather than a ProductCode for detection; `/layout` is a Burn
+  action but the bootstrapper decides whether it can be narrowed — the ADK refuses, so an offline layout is
+  always the whole kit), and **Advanced Installer projects** (the `.aip` CLI, a fresh ProductCode per build
+  changing the package identity every time, and the undocumented behaviour that relative paths resolve
+  against the .aip's own location — moving a project between drives breaks it silently).
+### 0.26.2 - 08.09.2026
+- **Fixed: a WHQL driver pack turned the pre-flight red.** `Get-DriverSignatureInfo.ps1` did not strip the
+  inline comment that WHQL packs write after `CatalogFile=` (`; for WHQL certified`), so the catalog never
+  resolved and validly signed drivers classified as `Unsigned` — 6 of 70 INF in a Dell WinPE set, all of
+  whose catalogs were Authenticode-valid and Microsoft-signed. An unquoted `;` now ends the value.
+- **Fixed: `New-MsiPackage.ps1` was the sixth script with the `-File` binder trap.** `-ProcessesToClose
+  'a','b'` arrived as one element, so the scaffold closed no processes at all — silently, while reporting
+  success. 0.25.1 had fixed the other five and missed the generator.
+- **Documented: seven findings from a three-package dependency chain** (Appendix G) and four new
+  anti-patterns (Appendix B), including `msiexec /a` against bundled payload, the `-Include` trap, 8.3
+  short names in path comparisons, and what a service's `%TEMP%` really is on Windows 11.
+### 0.26.1 - 06.09.2026
+- **Fixed: a syntax error in the template silently killed the whole dossier script.** A `
+` inside a JS
+  string literal became a real newline; JavaScript then discards the entire `<script>` block, so the
+  language toggle, all copy buttons and the condensing sticky header died at once — while all 419 tests
+  stayed green, because they only assert on rendered HTML. `tests/Report-Template.Tests.ps1` now runs
+  `node --check` on the script block plus a node-free quote-balance check, both proven against the
+  reintroduced bug.
+- **Changed: every table copies by clicking the row**, replacing the hover icon. Key/value tables give the
+  value, return codes the code, assignments the group name, the SYSTEM-test table the whole row. Clicks on
+  a row's own controls (the foldable detection script) and text selections are left alone. The Markdown
+  description keeps its own copy button.
+
+### 0.26.0 - 06.09.2026
+- **Fixed: the dossier could name a return-code type Intune does not have.** Graph accepts exactly
+  `success`, `softReboot`, `hardReboot`, `retry`, `failed` — there is no `ignored`, yet "Ignored" reached a
+  real dossier because the report rendered a caller-supplied table without validating anything (`Label` was
+  free text, `Cls` was interpolated raw into a `class` attribute). `Label` and `Cls` are now derived from
+  `Type` through a closed switch and cannot be supplied at all; an invalid type throws.
+- **Return codes are sorted and copyable.** Sorted by type in Appendix F.4 order, then numerically — the
+  order the table is verified against and typed into the portal. Each code cell has a copy icon and the
+  section a "copy table" button.
+- **New `Get-PsadtReturnCodes.ps1`: one source of truth for the dossier AND the upload.** Previously two
+  independent literals that agreed by coincidence. `Invoke-IntuneWin32Upload.ps1` gained `-ReturnCodes`, so
+  installer-specific codes finally reach the app instead of only the document, and a new manifest key
+  `research.returnCodes` records them once for both.
+- 419 tests; six new regression guards, each verified to fail on its reintroduced bug.
+
+### 0.25.2 - 06.09.2026
+- **Fixed: a sandbox run left an error dialog on the desktop.** The guest shuts itself down at the end, the
+  RDP-style client loses its session and shows a connection-lost box. The host now disposes of the viewer as
+  soon as the run reports in. The tempting fix — let the host kill the VM instead of shutting the guest down
+  — was measured and is wrong: it orphans the `vmmemWindowsSandbox` worker, which then holds the work folder
+  open for minutes and cannot be killed. Guest shuts down, host closes the window, and the wait is on the VM
+  worker rather than on the client processes.
+
+### 0.25.1 - 06.09.2026
+- **Fixed: array parameters broke under the `-File` binder.** `pwsh script.ps1 -Intents a,b` passes the
+  whole string as ONE element, so `Invoke-IntuneAppAssignment.ps1` rejected a perfectly valid comma-separated
+  intent list with a ValidateSet error naming a value nobody typed. It now splits the list itself and still
+  rejects a real typo by name. `Invoke-PsadtSandboxTest.ps1 -Paths*` had the same trap with a worse outcome —
+  only the first path was asserted and the run still reported GREEN. Six regression tests; suite at 382.
+
+### 0.25.0 - 05.09.2026
+- **New: `Get-PsadtMsiFacts.ps1` reads an MSI in one pass** — identity, signature, SHA256, features with
+  component counts, *decoded* upgrade flags, shortcuts, directories, file versions, registry rows and the
+  Icon table. For an MSI this probe **is** the research: it is what reveals an auto-updater sitting in its
+  own feature (so `ADDLOCAL` replaces post-install cleanup), a `DesktopFeature` you must not install, and
+  `MigrateFeatures` on the upgrade row — the flag that means `ADDLOCAL` alone is not enough. Five
+  regression guards, each verified to fail on its reintroduced bug.
+- **Fixed: the sandbox test left litter and put the evidence in the wrong place.** It kept one work folder
+  per app under the config home forever, and `result.json` plus the PSADT logs lived there with the
+  manifest pointing into a profile directory. Evidence now lands in
+  `<outputRoot>\<Stem>\SandboxTest\` beside the dossier — not in the package folder, which is what
+  IntuneWinAppUtil packs — the logs are recorded in `artifacts.logs[]`, and the scratch is removed.
+  `-KeepWorkFolder` keeps it, and a failed run keeps it automatically.
+- **Fixed: the test suite wrote into the real config home.** It now redirects `PSADT_DEPLOY_HOME` to a temp
+  directory, with a test that asserts it.
+- **Measured:** PuTTY 0.85 packaged with these lessons applied took **13 min 45 s end to end** — versus 75
+  minutes for the Notepad++ run that produced them. The largest single factor: the sandbox test costs zero
+  wall-clock time when started as soon as pre-flight goes GREEN, because packaging and the dossier do not
+  depend on its verdict.
+
+### 0.24.0 - 05.09.2026
+- **New: `Invoke-PsadtSandboxTest.ps1` runs the whole Phase 6 loop in a throwaway Windows Sandbox** —
+  Install, detection, Uninstall, detection, Reinstall, Repair, final Uninstall, every action as
+  `NT AUTHORITY\SYSTEM` via a scheduled task. **No elevation on the host, and the host is never touched**,
+  so the SYSTEM test stops being the step that gets deferred to "a DEV VM later". Every action starts from
+  a machine that has never seen the app, so a pass cannot be an artefact of the previous run. The verdict
+  is keyed on the detection script; package-specific facts go in via `-PathsPresentAfterInstall` /
+  `-PathsAbsentAfterInstall` / `-PathsAbsentAfterUninstall`. Verified end to end on Notepad++ 8.9.8 x64:
+  GREEN, all seven steps, 5 min 58 s.
+- **Why it is a script and not a snippet:** a hand-rolled version hit three bugs that each destroyed a full
+  VM run and each present as a timeout or a null-reference minutes after launch — `echo %ERRORLEVEL%>file`
+  silently becoming the `0>` stdin redirection (empty file, never a number), file existence read as
+  completion, and `[string]$null` still being `$null` in Windows PowerShell 5.1 (an empty detection output
+  is the *normal* result, so the harness crashed because the package was clean). All three now have
+  regression guards that were each verified to fail on the reintroduced bug.
+- Phase 6 in SKILL.md and the guide now lead with the sandbox route; the per-action route stays for apps a
+  VM cannot host. New anti-patterns cover hand-rolled harnesses, debugging through a long job instead of a
+  two-second local check, and "speeding up" the test by disabling Defender or dropping Uninstall/Repair.
+
+### 0.23.1 - 04.09.2026
+- **Fixed: two generators were broken since 0.21.0.** `New-BrowserExtensionPackage.ps1` and
+  `New-WindowsFeaturePackage.ps1` died at run time — the per-run `LogName` change had wedged a statement
+  into the template `Replace(...)` chain, which PowerShell parses as a property assignment with an empty
+  name. Valid syntax, so neither the parse check nor the source-inspecting tests could see it; it surfaced
+  the first time the whole chain ran against a real package. A guard in all four generator test suites now
+  fails on a broken chain, and the guard itself was verified against a broken and a good sample.
+
+### 0.23.0 - 04.09.2026
+- **`npx psadt-deploy-skill`.** One line installs or updates the skill into `~/.claude/skills/psadt-deploy`
+  and runs the setup doctor. Flags `--dir`, `--project`, `--ref`, `--no-setup`. Cloning to exactly the right
+  path by hand was the first thing a new user could get wrong.
+- **Zero dependencies** (Node 18's `fetch` + the `tar.exe` Windows ships). Three acquisition routes:
+  update an existing clone, else `git clone --depth 1`, else the branch tarball — because plenty of managed
+  machines have no git. The npm package ships only `bin/`; the skill comes from GitHub at install time, so
+  a new skill version needs no republish.
+- **The installer never writes the config itself** — it spawns `Set-PsadtConfig.ps1` and
+  `Initialize-PsadtSkill.ps1 -Fix`, because a second config-home implementation in JavaScript would drift
+  from `Get-PsadtConfig`. `Update-PsadtSkill.ps1` now tracks `package.json` and `bin/` so the archive
+  update route stops dropping them. Suite 307 → 326 tests.
+
+### 0.22.0 - 04.09.2026
+- **Third-party drivers.** New `scripts/Get-DriverSignatureInfo.ps1` classifies a driver folder before
+  anything is built — Microsoft-signed / vendor-signed / unsigned — by checking the **catalog** signature
+  rather than the `.sys` (a dual-signed `.sys` reports only its primary signature). New
+  `scripts/New-DriverPackage.ps1` builds the package: pnputil staging per INF, uninstall that resolves
+  `oemNN.inf` by original name instead of a remembered index, `Get-WindowsDriver` detection.
+- **The rule that saves the most time:** a vendor-signed *kernel* driver is RED, not a warning. With Secure
+  Boot on, only Microsoft Dev-Portal-signed kernel drivers load — importing the signer certificate removes
+  the "install device software?" prompt but does nothing for Code Integrity, so the driver installs and
+  then never loads. Unsigned drivers are refused outright, with three honest options and no testsigning.
+- Pre-flight gained a `DriverTrust` check that fires for **any** package shipping an `.inf` (a vendor
+  installer staging a driver is the case nobody declares), the dossier has a driver-trust row, and
+  `New-IntuneTrustedCertPolicy.ps1` is now fully self-contained like the firewall script.
+- New guide **Appendix Q** with the decision tree, pnputil exit codes and the installer-bundled-driver
+  case. Suite 251 → 307 tests.
+
+### 0.21.0 - 04.09.2026
+- **Every package gets a manifest** (`psadt-package.json`): identity, gate decisions, research findings,
+  every phase result and the produced artifacts, in one file per app. The generators write it, every phase
+  script reads and updates it — so an app's version, name and test evidence stop living in someone's head.
+- **The `.intunewin` is named after the app.** New: `<outputRoot>\<Vendor>_<App>_<Version>_<Arch>\<same
+  stem>.intunewin`, produced by the new `scripts/Invoke-PsadtPackage.ps1`. Until now every package came out
+  as `Invoke-AppDeployToolkit.intunewin` — that name reached Intune, and concurrent uploads collided in one
+  shared temp folder. The new script also verifies the archive before calling it a deliverable and refuses
+  an output folder inside the package (which made the tool pack its own previous output).
+- **One PSADT log per run** instead of one ever-growing file:
+  `<Vendor>_<App>_<Version>_<Arch>_<Install|Uninstall|Repair>_<timestamp>.log`. PSADT appends to a fixed
+  name by default, so by the third attempt a failed install was unreadable.
+- **Pre-flight gained two checks:** a missing or incomplete manifest is RED, a pre-0.21 launcher without a
+  per-run log name is a WARN. Report and upload both take their identity from the manifest.
+- Guide: the missing `Phase 6 / 9 / 10` sections now exist, and Appendix E is numbered by phase.
+  Suite 173 → 251 tests.
+
+### 0.20.0 - 04.09.2026
+- **Intune access is state, not a 403.** New `scripts/Test-PsadtIntuneAccess.ps1` answers *before* Phase 9
+  whether the configured app can actually upload, assign groups or create policies — and for how long the
+  credential lives. `TokenOk` and every capability are three-valued: verified / refused / **unknown**,
+  because Graph tokens are opaque by contract and "we could not tell" is not "not permitted". An offline run
+  never overwrites what was verified earlier.
+- **The scripts assert the role they need before their first write** instead of discovering it from a 403
+  mid-upload. Group assignment requires *both* group roles and names the missing half.
+- **`New-PsadtEntraApp.ps1` is re-runnable.** It finds the app by the recorded `clientId`, **merges**
+  requested permissions instead of replacing them (a run without `-IncludeConfigurationManagement` used to
+  silently revoke that role), never prompts, persists what it learned, and only sets `uploadEnabled` once
+  consent is really in place. Older client secrets are counted, never deleted.
+- **Auth failures say what to do:** expired/invalid client secret, unknown app or tenant, Conditional Access
+  block — and an undecryptable DPAPI secret now explains that DPAPI is bound to the Windows user profile.
+- `references/app-registration.md` is now the single permission matrix (app roles → capabilities → how to
+  grant), referenced from the guide instead of duplicated. Suite 128 → 173 tests.
+
+### 0.19.0 - 04.09.2026
+- **Setup doctor: `scripts/Initialize-PsadtSkill.ps1`.** One idempotent script replaces the Phase 0 prose
+  wizard and reports GREEN/YELLOW/RED over 13 prerequisite checks, each with a concrete fix hint. `-Fix`
+  installs the modules, downloads the content-prep tool, fills the EN/DE + tool-path defaults and migrates an
+  old setup; `-Set @{...}` persists your values first; `-Json` / `-JsonPath` for other tooling. `.Missing`
+  lists only the four values a human has to supply (`paths.packageRoot`, `paths.outputRoot`, `author.person`,
+  `author.company`) — never a key the doctor could fill itself.
+- **Config, secret and tools moved to a per-user config home** (`%LOCALAPPDATA%\psadt-deploy\`, override
+  `$env:PSADT_DEPLOY_HOME`) instead of the skill folder, so a `git pull`, re-clone or re-install no longer
+  takes the whole setup with it — and scripts started from an output folder still find their config.
+  `Get-PsadtConfig.ps1` is the single resolver and now returns `.Home` / `.DefaultHome` / `.LegacyInUse`. An
+  old config beside `scripts/` keeps working read-only until `-Fix` migrates it (originals renamed
+  `*.migrated`, nothing deleted).
+- **`Set-PsadtConfig.ps1 -Remove`** deletes dotted keys, so switching credential type can clean up the
+  stale one. **Fixed:** `New-PsadtEntraApp.ps1` reported `<skill>\config.json` even when the config lived
+  elsewhere. Suite 120 → 128 tests.
+
+
+<details>
+<summary><strong>Earlier releases (0.18.1 and older)</strong></summary>
+
+### 0.18.1 - 03.09.2026
+- **Upload: `-MaxRunTimeMinutes`.** `Invoke-IntuneWin32Upload.ps1` can now set
+  `installExperience.maxRunTimeInMinutes` (1–1440); `0` (default) omits the field and keeps the service default
+  of 60 min. Raise it for long-running installs (OS in-place upgrades, large suites) so the IME does not kill them.
+
+### 0.18.0 - 01.07.2026
+- **HanseMerkur corporate design + editorial report redesign.** The dossier/report template is re-themed to the
+  HanseMerkur CD (green brand family on a light mint canvas; Metric font stack with Segoe fallback and no
+  web-font fetch → no CORS console errors on a local `file://` open) and relaid out as an "editorial
+  data-report": flat hairline sections, auto-numbered headings (`01…13`), an at-a-glance KPI band under the hero
+  (version · pre-flight · min OS · arch), and a wider 1600px layout. The detection script is folded behind a
+  collapsed `<details>` (the rule summary stays visible). German report text now uses real umlauts. Fixed the
+  sticky-header flicker (Chrome/Edge scroll-anchoring vs. the condensing hero → `overflow-anchor: none`,
+  Playwright-verified) and removed the redundant hero status pill.
+
+### 0.17.0 - 01.07.2026
+- **install4j fingerprint + behavioral silent-switch verification.** Appendix L.1 now recognises install4j
+  (Java) installers (`com/install4j/runtime`, `exe4j`, `i4jparams.conf`, bundled `jre\`) and records that `/S`
+  is NOT its switch (it hangs on the language dialog) — the unattended switch is `-q`, run elevated. New BINDING
+  rule: a single string match is a hint, not proof; confirm the engine by its definitive fingerprint AND run the
+  silent switch once (timeout+kill, expect exit 0, no dialog) before packaging. Appendix L.3 adds the
+  trademark-sign gotcha (`Name(R)` breaks `-match 'Name'` → tolerant regex); Appendix B adds anti-patterns 13–15.
+  (Driven by an Aperio install4j installer misidentified as NSIS, where `/S` hung on the language dialog.)
+
+### 0.16.0 - 29.06.2026
+- **Dossier auto-sync convention (BINDING)** + report header layout fix. Any change to the package scripts
+  (launcher, Extensions, detection, version/changelog, return codes, re-packaging) now requires regenerating
+  `Intune-Dossier.html` in the same pass; a stale dossier is a defect. The `.pill-lg` status badge caps at 230px
+  and wraps so a long status no longer overlaps the hero title.
+
+### 0.15.2 - 15.06.2026
+- **Follow-up doc fix.** A contradiction sweep after 0.15.1 caught one more stale "Phase 7.5" in
+  `New-PsadtReport.ps1` help (upload is Phase 9); corrected. No other live stale references remain.
+
+### 0.15.1 - 15.06.2026
+- **Generator hardening from a self-review (correctness + security).** All three generators now single-quote-escape
+  values embedded in `$adtSession` literals, so an apostrophe in the App name/vendor/author (e.g. "Bob's App",
+  "L'Oreal") no longer produces an unparseable package; the MSI `-AdditionalArgumentList` / `ProcessesToClose`
+  literals are escaped too (also closing a SYSTEM code-injection path). Detection exit-code drift fixed:
+  `New-MsiPackage.ps1` + the WinGet example now `exit 0` for "not installed" (a non-zero exit reads as a detection
+  error), and a new **pre-flight Detection check** WARNs on a non-zero exit in `Detect*.ps1`. The WSUS bypass in
+  `New-WindowsFeaturePackage.ps1` now saves all prior state before writing and runs inside the `try/finally`, so a
+  partial failure can't leave `UseWUServer=0` permanently. Added input guards (`$Name` path-traversal, `__TOKEN__`
+  leak), MSI `-Author` config fallback + `-InstallerPath` validation. Stale refs fixed (SKILL.md "A-M"->"A-P",
+  `New-PsadtEntraApp.ps1` "Phase 7.5"->"Phase 9").
+
+### 0.15.0 - 15.06.2026
+- **Windows-feature packages (optional features + capabilities / FoD).** New `scripts/New-WindowsFeaturePackage.ps1`
+  — one-call generator that enables Windows **Optional Features** (`Enable-WindowsOptionalFeature`: NetFx3,
+  Hyper-V, WSL, TelnetClient, …) and **Capabilities / Features on Demand** (`Add-WindowsCapability`: RSAT.*,
+  OpenSSH, …) from one typed list, multiple per package. Uninstall reverts (disable/remove); Repair re-enables
+  (idempotent). Reboot surfaces **3010** via `$adtSession.SetExitCode(3010)` (`-NoRestart`); detection treats
+  `EnablePending` as not-yet-done. Content comes from a bundled `-Source` (offline SxS) else Windows Update
+  behind a **temporary** WSUS bypass (`RepairContentServerSource=2`, `UseWUServer=0`) whose exact prior state is
+  restored. Guide **Appendix P**, SKILL.md Gate-1/anti-patterns/ref-lookup. Pre-flight GREEN; helper logic
+  verified against an in-memory registry sim; ASCII-clean.
+
+### 0.14.0 - 15.06.2026
+- **Browser-extension force-install packages (Edge / Chrome / Firefox).** New
+  `scripts/New-BrowserExtensionPackage.ps1` — one-call generator for force-installing browser extensions via
+  enterprise **policy registry keys** (policy-only, no installer, ESP-safe). Multiple extensions per package.
+  Chromium helper computes the **next free `ExtensionInstallForcelist` index** (never hard-codes `1`), dedupes by
+  ID and removes only its own entry (coexistence); Firefox merges into the single `ExtensionSettings` JSON written
+  as **`REG_MULTI_SZ`** (single-line `REG_SZ` is silently ignored — Mozilla bug 1750233). Guide **Appendix O**,
+  SKILL.md Gate-1/anti-patterns/ref-lookup. Pre-flight GREEN; helpers validated against a scratch registry hive;
+  ASCII-clean.
+
+### 0.13.1 - 15.06.2026
+- **Firewall policy body fixed against the live template (verified 201).** `New-IntuneFirewallPolicy.ps1`
+  produced a body Graph rejected (400). Corrected via the **msgraph skill** (not guessed): the group id needs
+  the `{firewallrulename}` token, the program path is the direct child `..._app_filepath`, action values are
+  `_action_type_1`/`_0`, and a template-based policy requires `settingInstanceTemplateReference` per instance +
+  `settingValueTemplateReference` per simple/choice value (profiles collection: instance ref only — a per-value
+  ref is a duplicate). Confirmed by a live **201 Create**; tests assert the references. Mirrored into the
+  MxManagementCenter Output deliverable.
+
+### 0.13.0 - 15.06.2026
+- **Self-contained firewall deliverable (copy-to-client safe).** `scripts/New-IntuneFirewallPolicy.ps1` is now
+  fully self-contained — no dot-sourcing of `_GraphCommon`/`_GraphInteractive`, no skill path; WAM sign-in +
+  policy body builder + console helpers are embedded. It runs on a test client that does **not** have the skill
+  installed (`-Interactive` WAM, or `-GraphToken`). Fixes the "Skill script not found … -SkillRoot" failure when
+  the deliverable was copied to another machine. New **binding SKILL.md convention "Self-contained deliverables"**
+  + a Pester test that enforces it (no dot-source / no skill path / embeds WAM). Test-first per writing-skills.
+
+### 0.12.0 - 15.06.2026
+- **Interactive WAM sign-in for the Intune policy scripts.** `New-IntuneFirewallPolicy.ps1` and
+  `New-IntuneTrustedCertPolicy.ps1` gain `-Interactive` (+ `-TenantId`): delegated sign-in via **WAM**
+  (Windows Web Account Manager) when there is no app registration — **no device code**. The WAM machinery
+  (`Initialize-MsalBroker` / `Get-WamToken` / new `Get-InteractiveGraphToken`) was extracted from
+  `New-PsadtEntraApp.ps1` into a shared `scripts/_GraphInteractive.ps1` (one implementation, no copy-paste
+  drift); the bootstrap now consumes it. The MxManagementCenter firewall deliverable became a thin wrapper
+  over the generic script.
+
+### 0.11.0 - 15.06.2026
+- **Intune firewall-rules policy + app config-management permission.** New `scripts/New-IntuneFirewallPolicy.ps1`
+  (Endpoint Security "Windows Firewall Rules" policy, one program-scoped rule; dry-run / `-Execute` / manual
+  portal fallback) + Pester test. Suppresses the first-run Windows Firewall prompt for apps that listen inbound.
+  New `New-PsadtEntraApp.ps1 -IncludeConfigurationManagement` consents `DeviceManagementConfiguration.ReadWrite.All`
+  (needed by the firewall and trusted-cert policies for `-Execute`).
+
+### 0.10.0 - 15.06.2026
+- **Certificate store deployment (driver-trust / TrustedPublisher).** New `scripts/New-IntuneTrustedCertPolicy.ps1` —
+  a Custom OMA-URI profile that places a certificate into a Windows machine store via the
+  `RootCATrustedCertificates` CSP (the policy-based way to suppress the Windows "install device software?"
+  driver-trust prompt). Guide Appendix N, dossier "Treiber-Zertifikat" row, SKILL.md convention + Pester test.
+
+### 0.9.2 - 12.06.2026
+- **Reconciled a diverged install copy back into the repo.** Fixed `Invoke-PsadtSystemTest.ps1` crashing at
+  param binding under the WinPS 5.1 re-exec (`$SkillRoot` default is now fail-safe, so the SYSTEM Install/
+  Uninstall gate works on a pwsh-7 host). Added per-field copy buttons + a `file://`-safe clipboard to the
+  HTML dossier (`Report-Template.html`, token set unchanged). Added `scripts/New-MsiPackage.ps1` (reusable
+  MSI package generator, `$PSScriptRoot`-relative, ASCII-only) + its Pester test.
+
+### 0.9.1 - 12.06.2026
+- **Applicability/portability drift cleanup** (docs + instructions; no script logic changed). Removed the
+  phantom `test.maxIterations` / `test.endState` config keys from SKILL.md Phase 6 (the cap is a hard count of
+  5 the orchestrator owns); fixed stale "Phase 7.5" -> **Phase 9** in SKILL.md + `app-registration.md`; fixed
+  the README project tree (report **Phase 8**, added the 3 missing scripts `Invoke-PsadtPreflight`,
+  `Invoke-IntuneAppAssignment`, `_GraphCommon`).
+- **`superpowers` downgraded from hard `REQUIRED` to optional/preferred.** The Researcher/Reviewer roles now
+  prefer `superpowers:*` if installed and otherwise fall back to the native Agent tool / `/code-review`; the
+  Requirements list documents it as an optional (recommended) enhancement. The workflow no longer depends on it.
+
+### 0.9.0 - 11.06.2026
+- **Audit cleanup** (quality / content / applicability+compatibility / tests). Highlights: shared
+  `scripts/_GraphCommon.ps1` (de-duplicates the 3 Graph scripts) + **28 new Pester tests** for the previously
+  untested upload/assignment/Entra-app/token scripts (suite now 74); fixed an `Invoke-WithRetry` precedence
+  bug (retried every error 6x) and PS7-fragile throttling reads; the HTML report no longer shows synthetic
+  "passed" rows when no pre-flight/SYSTEM-test results are supplied (neutral "not run") and derives the PSADT
+  version from the installed module; GUID `ValidatePattern` on the MSI codes.
+- **Phase numbering unified** across SKILL.md + guide into one integer scheme **0-12**; every Phase/Appendix
+  cross-reference re-verified. Anti-pattern list trimmed; SYSTEM-test prerequisites, `/beta` drift caveat,
+  rollback step, logging convention, and config help added. Guide `$adtSession` template `1.0.0`->`0.1` +
+  author-from-config; intro appendix index -> A-M.
+
+### 0.8.1 - 11.06.2026
+- **Docs consistency.** Fixed a stale cross-reference in SKILL.md (the guide range said **Appendix A-J** but
+  the guide now runs through **M** — K/L were added in 0.7.0 and M in 0.8.0 without updating it). Restored the
+  **0.5.3** entry that was missing from this README changelog mirror (it was present in `CHANGELOG.md`).
+
+### 0.8.0 - 11.06.2026
+- **Opt-in Entra group assignment, wired end-to-end.** New Phase 10 + `Invoke-IntuneAppAssignment.ps1`:
+  create/reuse Entra security groups by a configured naming scheme (`intune.groups`) and assign the uploaded
+  app (Required / Available / Uninstall). Read-only dry-run → confirm → execute; idempotent; never deletes a
+  group or another app's assignment; ambiguous/duplicate names skipped. Least-privilege roles
+  (`Group.Create` + `GroupMember.Read.All`) via `New-PsadtEntraApp.ps1 -IncludeGroupManagement`. Full
+  reference in **guide Appendix M** (config schema, naming tokens, version-independent default vs `%version%`
+  opt-in, permission model).
+- **Upload min-OS fix.** `-MinWindowsRelease` is now a `ValidateSet` of backend-accepted release IDs
+  (`1607..2004`) — `21H2`/`22H2` are server-rejected and used to kill the upload mid-flight with a Graph
+  `BadRequest`. Fails fast at param binding instead; set a higher minimum in the portal. Guide **H.11**.
+
+### 0.7.5 - 10.06.2026
+- **Honest exit codes + detection (correctness fix).** Removed the dangerous "always `exit 0`" guidance from
+  guide Appendix K — a blanket `exit 0` (or a detection tag written in a `finally`) reports GREEN on failure.
+  New **K.7**: the exit code reflects whether the fix could RUN (couldn't-run -> non-zero; the 64-bit relaunch
+  propagates the child's exit code), detection reflects the real END-STATE (tag only on success), with a
+  per-package decision table; "never block enrollment" is now an explicit ESP-assignment + return-code-mapping
+  choice, not a masked exit code. SKILL.md anti-pattern added.
+
+### 0.7.0 - 10.06.2026
+- **Value-adding extensions.** New `scripts/Invoke-PsadtPreflight.ps1` turns the Phase-5 Reviewer gate into one
+  deterministic `GREEN/RED` tool (encoding/parse/v3-scan/top-level/structure/GUID-to-`-FilePath`), with a Pester
+  suite. New guide **Appendix K** (script-only remediation / fix packages, ESP-safe — the debloat/Cisco pattern)
+  and **Appendix L** (installer technologies + silent switches, a lookup consulted before web research). Expanded
+  error-code catalogue (MSI 1603/1605/1619/1638/1639…, PSADT 60001/60008 + ranges) in guide Appendix A and the
+  SKILL.md troubleshooting table. SKILL.md rewired to point at the pre-flight script and the new appendices.
+
+### 0.6.2 - 10.06.2026
+- **Audit & harden.** Agent-based audit + source-level verification (discarded ~8 false positives). Fixes: the
+  guide's broken `New-ADTTemplate` "Extended scaffold" (passing app metadata params that v4.1.x rejects);
+  the Graph uploader leaving its extracted work dir (with the AES keys in `Detection.xml`) in `%TEMP%` (now
+  `try/finally` cleanup); the report `Notes` default `&middot;` double-escape; the fallback initials-SVG logo
+  now XML-escapes + base64-encodes (no markup injection, with a regression test). Robustness: `Invoke-Graph`
+  429/5xx retry with `Retry-After`; malformed-`config.json` safety in four scripts; WinGet 2-byte header read;
+  symmetric temp cleanup in self-update. Graph request shapes left untouched.
+
+### 0.6.1 - 10.06.2026
+- **Report header flicker fixed** (`references/Report-Template.html`): at widths where the content height met
+  the viewport edge, the vertical scrollbar toggled on/off and the header's `vw`-based `clamp()` padding and
+  `h1` font-size reflowed on every toggle — a wild flicker loop. Reserving the scrollbar gutter
+  (`html { overflow-y: scroll; scrollbar-gutter: stable; }`) keeps the width constant and breaks the loop.
+
+### 0.6.0 - 10.06.2026
+- **SKILL.md slimmed to a control plane** (733 → 244 lines, ~67% fewer tokens) via progressive disclosure:
+  the long inline code moved into the reference guide (new **Appendix I** WinGet + **Appendix J** app-logo),
+  loaded on demand. Intake restructured into **4 decision gates** (researchable facts become stated
+  assumptions, not questions); explicit **sub-agent roles** (Researcher×3 / Builder / Reviewer) with GREEN
+  handoff gates; a single **blockade protocol** for errors. No binding rule or behaviour dropped.
+
+### 0.5.3 - 09.06.2026
+- **Guide code-fences are now English/ASCII.** Anglicized every German comment, string literal and placeholder
+  living **inside** PowerShell/text code fences in the guide (and the inline-code placeholders in the Appendix
+  F.1 table) — snippets get copied verbatim into deployment scripts, where the binding rule is English + 7-bit
+  ASCII. German explanatory **prose** and the **F.2 Company-Portal dossier template** deliberately stay German
+  (legitimate `language.dossier` end-user text). No script/tooling code changed.
+
+### 0.5.2 - 08.06.2026
+- **HTML package report is now always generated** (upload or not) by `scripts/New-PsadtReport.ps1` from the
+  fixed template `references/Report-Template.html`. One self-contained, **bilingual (DE/EN toggle)** document
+  combining the Intune dossier + a technical package report; Fluent-2 styled, sticky shrink header, logo
+  embedded as a data URI, description preview rendered from its Markdown source. New Pester test
+  `tests/New-PsadtReport.Tests.ps1`.
+
+### 0.5.1 - 06.06.2026
+- Self-update now decides by **commit** (git `HEAD` vs `origin/main`, or the GitHub commits-API sha vs a
+  recorded `tooling.skillCommit`) instead of the CHANGELOG version — no more CDN lag / circular version reads.
+- README project-structure tree compacted so it renders without horizontal scroll.
+
+### 0.5.0 - 06.06.2026
+- **Skill self-update** — `scripts/Update-PsadtSkill.ps1` checks GitHub for a newer version, shows what's new,
+  and updates in place on confirmation (`git pull` for a clone, else branch-zip overwrite of tracked files
+  only; `config.json` / `secret.dpapi` / `tools/` preserved). Triggers: *"update skill"*, *"/update-skill"*,
+  *"psadt update"*.
+
+### 0.4.0 - 06.06.2026
+- **WinGet packaging support** (strictly opt-in, never the default) + **certificate-based auth** for the Phase 9
+  upload (no secret at rest) + MSI icon-table logo fallback + device-code first-poll fix. Contributed by
+  **@joakim-i** (PR #4), reviewed and hardened before merge. See [CHANGELOG.md](CHANGELOG.md).
+
+### 0.3.2 - 06.06.2026
+- **Test-before-upload is now a binding gate:** Install + Uninstall must pass the Phase 6 SYSTEM test before
+  any Phase 9 upload. If it can't be run (no elevation / VM), stop before upload and hand back the command.
+
+### 0.3.1 - 06.06.2026
+- `Invoke-IntuneWin32Upload.ps1` gains **`-DetectionScriptPath`** (PowerShell-script detection rule) for
+  EXE / non-MSI installers without a ProductCode (e.g. Vivaldi). Verified live by uploading Vivaldi 8.0.4033.44.
+- Lesson: a *detection* script rule accepts only `ruleType,enforceSignatureCheck,runAs32Bit,scriptContent`
+  (guide Appendix H.2).
+
+### 0.3.0 - 06.06.2026
+- **Direct upload** (`scripts/Invoke-IntuneWin32Upload.ps1`, Phase 9): self-contained raw-Graph
+  `win32LobApp` upload (parse `.intunewin` → token → probe → idempotency → create/update → content → SAS
+  block-blob upload via HttpClient → commit → activate → categories → supersedence). Read-only dry-run by
+  default; `-Execute` to write.
+- **WAM Entra-app bootstrap** (`scripts/New-PsadtEntraApp.ps1`): interactive Windows-broker sign-in (device
+  code fallback), creates the app + admin consent + secret, DPAPI-stored.
+- **App-only token helper** (`scripts/Get-GraphToken.ps1`).
+- **Coexistence-safe versioning:** never deletes an older version; new versions coexist; optional
+  supersedence wiring. **Logo guard:** refuses the PSADT default `AppIcon.png`. Fills the full
+  App-information tab; never auto-assigns category/notes/groups.
+- Fixed the Repair `-FilePath`→`-ProductCode` example; reference guide gains **Appendix H**.
+
+### 0.2.0 - 05.06.2026
+- **Automated SYSTEM test loop** (`scripts/Invoke-PsadtSystemTest.ps1`, Phase 6): install → uninstall →
+  reinstall the package as the SYSTEM account via `Invoke-CommandAs`, with agent-driven auto-fix until
+  green or a max-iteration cap. Opt-in; elevated session required.
+- Phase 8 now prefers `Invoke-CommandAs -AsSystem` for SYSTEM-context testing (PsExec kept as a fallback).
+
+### 0.1.0 - 04.06.2026
+- Initial release: guided PSADT v4 → Intune Win32 lifecycle (intake, autonomous research, scaffolding, all
+  three deployment types, pre-flight checks, packaging, dossier + logo, guided testing, troubleshooting).
+- First-run setup writing a machine-local `config.json` (paths, language, author).
+- Self-healing prerequisites: PSAppDeployToolkit module (PSGallery) and `IntuneWinAppUtil.exe`
+  (auto-download + version check).
+- HTML dossier document with a Markdown app-description block (the Intune description field is
+  Markdown-only).
+- English skill + reference guide; MIT licensed.
+
+</details>