docs: correct distribution-channel statuses

README.md

@@ -107,9 +107,9 @@ choco install rackstack
 Install-Module RackStack
 ```
 
-The package-manager installs all pull the same code-signed `RackStack.exe` from the GitHub release. Updates come through the package manager (`winget upgrade`, `scoop update`, `choco upgrade`).
+The package-manager installs all pull the same `RackStack.exe` from the GitHub release. Updates come through the package manager (`winget upgrade`, `scoop update`, `choco upgrade`).
 
-> Scoop and PowerShell Gallery are live now. winget and Chocolatey publish automatically on each release — the first submission of each is pending review by the respective registry. See [`dist/`](dist/) for distribution details.
+> **Channel status:** PowerShell Gallery and Scoop are live now. Chocolatey is submitted and in community moderation review. winget is awaiting its one-time first submission to `microsoft/winget-pkgs`. See [`dist/`](dist/) for per-channel details.
 
 ### Download & Run
 

dist/README.md

@@ -8,9 +8,9 @@ and submission scaffolding.
 |---|---|---|
 | [GitHub Releases](https://github.com/TheAbider/RackStack/releases/latest) | ✅ Live (every release) | Download `RackStack.exe`, run as Administrator |
 | [PowerShell Gallery](https://www.powershellgallery.com/packages/RackStack) | ✅ Live (every release) | `Install-Module RackStack` |
-| [winget](https://github.com/microsoft/winget-pkgs) | ⏳ Pending first submission | `winget install TheAbider.RackStack` |
-| [Scoop](https://scoop.sh/) | ⏳ Pending bucket creation | `scoop bucket add rackstack https://github.com/TheAbider/scoop-bucket; scoop install rackstack` |
-| [Chocolatey](https://community.chocolatey.org/packages) | ⏳ Pending first submission | `choco install rackstack` |
+| [Scoop](https://scoop.sh/) | ✅ Live — bucket published | `scoop bucket add rackstack https://github.com/TheAbider/scoop-bucket; scoop install rackstack` |
+| [Chocolatey](https://community.chocolatey.org/packages/rackstack) | ⏳ Submitted — in community moderation review | `choco install rackstack` |
+| [winget](https://github.com/microsoft/winget-pkgs) | ⏳ First-submission manifests ready (`dist/winget/1.99.1/`); awaiting the one-time PR to winget-pkgs | `winget install TheAbider.RackStack` |
 
 ## winget
 

dist/scoop/README.md

@@ -1,26 +1,35 @@
 # Scoop manifest
 
-`rackstack.json` is the Scoop package manifest. It can be served two ways:
+`rackstack.json` here is a reference **template** (version `0.0.0`,
+zeroed hash). The **live** manifest users actually install from lives in
+the dedicated bucket repo with real version + hash values — see below.
 
-## Option A: Custom bucket (recommended, single-maintainer-friendly)
+## Live: custom bucket — ✅ published
 
-1. Create a new public repo at `https://github.com/TheAbider/scoop-bucket`.
-2. Copy `rackstack.json` from this directory into the new repo's root or `bucket/` directory.
-3. Update the `version`, `url`, and `hash` fields to match the current release (or rely on the embedded `checkver` / `autoupdate` blocks to do that automatically via scoop maintainer tools).
-4. Users install via:
-   ```powershell
-   scoop bucket add rackstack https://github.com/TheAbider/scoop-bucket
-   scoop install rackstack
-   scoop update rackstack    # picks up new releases via autoupdate
-   ```
+The bucket is live at **https://github.com/TheAbider/scoop-bucket**.
+Users install with:
 
-## Option B: Submit to ScoopInstaller/Extras
-
-The official `extras` bucket maintained by the Scoop community. Submission via PR to https://github.com/ScoopInstaller/Extras. Pros: discovered by default `scoop search`. Cons: subject to community review and the bucket maintainers' ongoing approval. The `checkver` block in this manifest is already in the format that the Extras bucket's auto-update bot understands.
-
-## Automation
+```powershell
+scoop bucket add rackstack https://github.com/TheAbider/scoop-bucket
+scoop install rackstack
+scoop update rackstack    # picks up new releases
+```
 
-Once the bucket repo exists, a workflow can keep the manifest version + hash in sync with new GitHub releases. The simplest path is the official `MCOfficer/scoop-updater` action which runs `scoop checkver` on a schedule and opens PRs against the bucket. Manual maintenance also works for low-frequency releases.
+When a new RackStack version ships, update the bucket repo's
+`rackstack.json` — bump the `version`, `url`, and `hash` to the new
+release (the EXE SHA-256 is in that release's `release-hashes.txt`).
+The manifest's embedded `checkver` / `autoupdate` blocks let Scoop's
+maintainer tooling do this automatically if a `scoop-updater` workflow
+is added to the bucket repo later.
+
+## Optional: submit to ScoopInstaller/Extras
+
+The official `extras` bucket maintained by the Scoop community.
+Submission via PR to https://github.com/ScoopInstaller/Extras. Pro:
+discoverable by default `scoop search` without adding the custom
+bucket. Con: subject to community review. The `checkver` block in this
+manifest is already in the format the Extras auto-update bot understands.
+Not required — the custom bucket above already works.
 
 ## Verification