Bump the Gallery manifest in step with the release version

[TheAbider]

What happened

v1.122.1 published to GitHub Releases but not to the PowerShell Gallery.

RackStack.psd1 was not in the version-sensitive file list, so its ModuleVersion stayed on 1.122.0 while the rest of the tree moved to 1.122.1. The Gallery publish step in ci.yml refuses to push a manifest whose version disagrees with Header.ps1 — that guard is correct and it did its job:

PSGallery publish: RackStack.psd1 ModuleVersion (1.122.0) does not match
Header.ps1 version (1.122.1). Bump the manifest.

The problem is where it fires. That step runs in the release job, so by the time it failed the GitHub release had already been created, signed, attested, and tagged. The steps behind it — winget submission, Chocolatey publish, and the retention rule — were skipped.

Re-running does not help: those steps are gated on steps.releasecheck.outputs.exists == 'false', and v1.122.1 now exists, so they would skip.

Fix

Releasing v1.122.2, which is self-healing — the retention rule collapses all 1.122.x releases to the newest, so this ends with a single release that is correct on every channel.

• RackStack.psd1 bumped to 1.122.2 in step with every other version touchpoint.
• New Run-Tests section 205 asserts that 00-Initialization.ps1, Header.ps1, RackStack.ps1, the Run-Tests synopsis, RackStack.psd1, and the changelog all agree on the version. A mismatch now costs a red check on the pull request instead of a half-published release. Verified against the exact failing state (init 1.122.2 + psd1 1.122.0) to confirm it catches the regression rather than passing vacuously.
• RackStack.psd1 added to section 174's documentation-freshness list instead of duplicating the count-derivation logic. That immediately caught the manifest description advertising 176 CLI actions against a live 201 — a stale number that ships to the Gallery listing.

local/release-touchpoints.md and local/Validate-Release.ps1 (both untracked) were updated to match, so the checklist and the local gate no longer disagree with what CI enforces.

Verification

• 5424/5424 structural tests pass, 0 failures
• PSScriptAnalyzer: 0 findings
• Pre-release validation: 38 passed, including RackStack.psd1 ModuleVersion matches (1.122.2)
• Monolithic rebuilt and parse-checked, UTF-8 BOMs intact

The two remaining Validate-Release failures (stats footer, no empty version sections) are pre-existing and unrelated — both are stale expectations of a changelog convention abandoned around v1.98, and they fail identically on v1.122.0.

Contents

This carries everything in v1.122.1: the self-update integrity fix and the antivirus documentation.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!