Prepare 2.1.0 release notes: fold all session work into the release

Updates the manifest ReleaseNotes and CHANGELOG so the 2.1.0 entry covers the
full release: the -CheckCapabilities implementation, the E2E test suite, the
clean analyzer gate and the removed dead parameters now appear alongside the
correctness fixes. Release date set to today; compare links aligned to the
repository's vX.Y.Z-postN tag scheme.

Author: DeltaGa

AppxBackup.psd1

@@ -193,15 +193,17 @@ Key Features:
 
             # ReleaseNotes of this module
             ReleaseNotes = @'
-Version 2.1.0 (July 27, 2026)
+Version 2.1.0 (July 28, 2026)
 =============================
 
 RELEASE SUMMARY:
 Correctness release. Six defects are fixed in which a guard compared a boolean
 result against $null and therefore never ran, including one that could hang a
-backup indefinitely and one that corrupted every captured tool output. The
-module gains its first automated test suite, a static-analysis configuration
-and a CI pipeline.
+backup indefinitely and two that corrupted or discarded captured tool output.
+The module gains its first automated test suite, a static-analysis gate that
+now runs clean, end-to-end packaging tests against the real MakeAppx, and a CI
+pipeline. Test-AppxBackupCompatibility -CheckCapabilities, previously accepted
+but ignored, is now implemented.
 
 FIXED:
 
@@ -213,6 +215,12 @@ Process execution
   invoked with a 1800 second timeout. Verified: a 3s timeout previously ran a
   30s process to completion and reported success, and now aborts at 3s.
 - Invoke-ProcessSafely never detected a failed Process.Start().
+- Invoke-ProcessSafely discarded almost all captured tool output. Output was
+  collected through PowerShell eventing, whose handlers are not pumped while
+  the pipeline blocks in WaitForExit; against MakeAppx, which emits 36 lines,
+  one line survived, so packaging failures produced no usable diagnosis. Both
+  streams are now read with StreamReader.ReadToEndAsync. This also removed a
+  fixed 1-2 second sleep per invocation.
 - Captured stdout and stderr were prefixed with the capture buffer's own
   capacity ("16384" and "4096"). The buffers were built from an Int64 supplied
   by ConvertFrom-Json, and StringBuilder has (Int32) and (String) overloads but
@@ -238,6 +246,28 @@ Diagnostics
 - Write-AppxLog: removed a dead preference guard and corrected an empty-string
   check against $null.
 
+ADDED:
+
+- Test-AppxBackupCompatibility -CheckCapabilities is now implemented. Declared
+  capabilities are classified against Config/CapabilityClassification.json into
+  restricted (Microsoft-gated), device (consent at first use) and general, with
+  restricted entries producing a warning. The classification lives in
+  configuration so it can track new Windows capabilities without a code change.
+- tests/: 73 Pester tests covering path validation, process execution, tool
+  discovery, configuration loading and the manifest/loader/disk contract.
+  Written in the Pester 5 and 6 compatible subset. Every defect above has a
+  regression test.
+- End-to-end packaging tests tagged E2E that build a synthetic package through
+  the real Windows SDK MakeAppx, including a negative case asserting the
+  tool's own error text surfaces. Excluded from the default run; opt in with
+  build.ps1 -Task Test -IncludeE2E.
+- build.ps1: single Build/Analyze/Test entry point shared by contributors
+  and CI, with NUnit and CSV output under -CI.
+- PSScriptAnalyzerSettings.psd1: correctness-scoped rule set, now reporting
+  zero findings; CI blocks on any new warning or error.
+- .github/workflows/ci.yml: Windows CI across PowerShell 7.4 and 7.5.
+- .gitignore and CHANGELOG.md.
+
 CHANGED:
 
 - Aliases are exported module members instead of being created with
@@ -251,19 +281,13 @@ CHANGED:
   PowerShell 5.1 and could never satisfy PowerShellVersion 7.4.
 - AppxBackup.psd1 and Write-AppxLog.ps1 contain non-ASCII characters and now
   carry a UTF-8 BOM so they are read correctly by ANSI-defaulting hosts.
-
-ADDED:
-
-- tests/: 71 Pester tests covering path validation, process execution, tool
-  discovery, configuration loading and the manifest/loader/disk contract.
-  Written in the Pester 5 and 6 compatible subset. Every defect above has a
-  regression test.
-- build.ps1: single Build/Analyze/Test entry point shared by contributors
-  and CI, with NUnit and CSV output under -CI.
-- PSScriptAnalyzerSettings.psd1: correctness-scoped rule set; each exclusion
-  documents why the rule does not apply to this project.
-- .github/workflows/ci.yml: Windows CI across PowerShell 7.4 and 7.5.
-- .gitignore and CHANGELOG.md.
+- Invoke-ProcessSafely no longer accepts -AsyncWaitMilliseconds. It configured
+  the sleep that compensated for the event-handler drain, which no longer
+  exists. No caller passed it.
+- Removed three private parameters that were accepted and ignored:
+  -ValidateSchema (Get-AppxManifestData), -CreateBundle
+  (New-AppxPackageInternal) and -OutputDirectory (New-AppxBackupManifest).
+  No public surface change.
 
 COMPATIBILITY:
 - Public contract unchanged: the same 8 functions and 4 aliases.

CHANGELOG.md

@@ -10,37 +10,7 @@ Releases before 2.1.0 were recorded only in the `ReleaseNotes` field of
 
 ## [Unreleased]
 
-### Added
-
-- `Test-AppxBackupCompatibility -CheckCapabilities` is now implemented. The
-  package's declared capabilities are classified against
-  `Config/CapabilityClassification.json` into restricted (gated by Microsoft, and
-  the entries most likely to make a sideloaded restore behave differently from the
-  original), device (user consent at first use) and general. Restricted
-  capabilities add a warning, and the result object gains
-  `DeclaredCapabilities`, `RestrictedCapabilities`, `DeviceCapabilities` and
-  `CapabilitiesChecked`. The classification lives in configuration so it can track
-  new Windows capabilities without a code change.
-- End-to-end packaging tests under `tests/`, tagged `E2E`. They build a synthetic
-  but valid package through the real Windows SDK MakeAppx — including a negative
-  case asserting that a failed run surfaces the tool's own error text — and are
-  excluded from the default run. Run them with `build.ps1 -Task Test -IncludeE2E`;
-  they skip cleanly without the SDK. CI runs them as a separate step on
-  windows-latest, which ships the SDK.
-
-### Changed
-
-- The analyzer gate is now clean and CI blocks on warnings, not just errors. The
-  22 remaining pre-existing warnings were resolved: genuinely dead variables
-  removed, discarded call results made explicit with `$null`, safe-fallback
-  catches given non-throwing acknowledgements, and the logger's deliberate silent
-  catches suppressed at function level with justification.
-- Removed three private parameters that were accepted and ignored:
-  `-ValidateSchema` (`Get-AppxManifestData`), `-CreateBundle`
-  (`New-AppxPackageInternal`) and `-OutputDirectory` (`New-AppxBackupManifest`).
-  No public surface change.
-
-## [2.1.0] - 2026-07-27
+## [2.1.0] - 2026-07-28
 
 A correctness release. Six defects shared one root cause: a guard compared the
 result of a boolean-returning call against `$null`. Because `[bool]` is never
@@ -124,10 +94,25 @@ tests, a static-analysis configuration, and CI.
 
 ### Added
 
+- `Test-AppxBackupCompatibility -CheckCapabilities` is now implemented. The
+  package's declared capabilities are classified against
+  `Config/CapabilityClassification.json` into restricted (gated by Microsoft, and
+  the entries most likely to make a sideloaded restore behave differently from the
+  original), device (user consent at first use) and general. Restricted
+  capabilities add a warning, and the result object gains
+  `DeclaredCapabilities`, `RestrictedCapabilities`, `DeviceCapabilities` and
+  `CapabilitiesChecked`. The classification lives in configuration so it can track
+  new Windows capabilities without a code change.
 - `tests/` — 73 Pester tests covering path validation, external process execution,
   SDK discovery, configuration loading, and the manifest/loader/disk agreement that
   defines the public surface. Written in the subset shared by Pester 5 and 6. Every
   defect listed above has a regression test that fails against the old behaviour.
+- End-to-end packaging tests under `tests/`, tagged `E2E`. They build a synthetic
+  but valid package through the real Windows SDK MakeAppx — including a negative
+  case asserting that a failed run surfaces the tool's own error text — and are
+  excluded from the default run. Run them with `build.ps1 -Task Test -IncludeE2E`;
+  they skip cleanly without the SDK. CI runs them as a separate step on
+  windows-latest, which ships the SDK.
 - `build.ps1` — one entry point for `Build`, `Analyze` and `Test`, used by both
   contributors and CI so that local and CI results mean the same thing. `-CI`
   produces NUnit test results and a CSV of analyzer findings, and sets the exit code.
@@ -138,16 +123,18 @@ tests, a static-analysis configuration, and CI.
   artefacts produced by running the module in place.
 - This changelog.
 
+- Removed three private parameters that were accepted and ignored:
+  `-ValidateSchema` (`Get-AppxManifestData`), `-CreateBundle`
+  (`New-AppxPackageInternal`) and `-OutputDirectory` (`New-AppxBackupManifest`).
+  No public surface change.
+- The analyzer gate is now clean and CI blocks on warnings, not just errors. The
+  pre-existing warnings were resolved: genuinely dead variables removed,
+  discarded call results made explicit with `$null`, safe-fallback catches given
+  non-throwing acknowledgements, and the logger's deliberate silent catches
+  suppressed at function level with justification.
+
 ### Known issues
 
-- PSScriptAnalyzer reports 35 warnings that predate this release: unused variables
-  and parameters, and deliberately silent catch blocks in the logger. CI blocks on
-  errors and reports warnings without failing. See "Recommended next steps" in
-  `README.md`.
-- Four declared parameters are accepted but ignored: `-CheckCapabilities`
-  (`Test-AppxBackupCompatibility`), `-ValidateSchema` (`Get-AppxManifestData`),
-  `-CreateBundle` (`New-AppxPackageInternal`) and `-OutputDirectory`
-  (`New-AppxBackupManifest`). Only the first is on a public command.
 - PSScriptAnalyzer 1.25 raises an internal `NullReferenceException` while inspecting
   `AppxBackup.psm1` through an absolute path. Analysis still completes and returns
   the full finding set; `build.ps1` reports the condition instead of failing on it.
@@ -176,8 +163,8 @@ tests, a static-analysis configuration, and CI.
 - Initial 2.x line: ZIP-based dependency packaging (`.appxpack`) with installation
   orchestration, native certificate management, and MSIX support.
 
-[Unreleased]: https://github.com/DeltaGa/AppxBackup.Module/compare/v2.1.0...HEAD
-[2.1.0]: https://github.com/DeltaGa/AppxBackup.Module/compare/v2.0.2...v2.1.0
-[2.0.2]: https://github.com/DeltaGa/AppxBackup.Module/compare/v2.0.1...v2.0.2
-[2.0.1]: https://github.com/DeltaGa/AppxBackup.Module/compare/v2.0.0...v2.0.1
+[Unreleased]: https://github.com/DeltaGa/AppxBackup.Module/compare/v2.1.0-post1...HEAD
+[2.1.0]: https://github.com/DeltaGa/AppxBackup.Module/compare/v2.0.2-post1...v2.1.0-post1
+[2.0.2]: https://github.com/DeltaGa/AppxBackup.Module/compare/v2.0.1-post2...v2.0.2-post1
+[2.0.1]: https://github.com/DeltaGa/AppxBackup.Module/compare/v2.0.0...v2.0.1-post2
 [2.0.0]: https://github.com/DeltaGa/AppxBackup.Module/releases/tag/v2.0.0