samartomar · Sep 24, 2026 · Sep 24, 2026
diff --git a/docs/guide.md b/docs/guide.md
@@ -87,6 +87,19 @@ someone who actually needs it; when that happens, this paragraph is what changes
 is built by GitHub Actions from a tagged commit, and the workflow runs the full test
 suite before it builds — a release that skips the gate is not a release.
 
+### With Scoop
+
+```powershell
+scoop bucket add flow https://github.com/samartomar/scoop-flow
+scoop install flow/flow
+```
+
+The same zip, from Flow's own [bucket](https://github.com/samartomar/scoop-flow), checked
+against the SHA-256 each release publishes beside it. `scoop update flow` takes a newer
+one, which the bucket picks up within four hours of a release. Say `flow/flow`, with the
+bucket in front: Scoop's main bucket has a different `flow`, Facebook's JavaScript type
+checker.
+
 ### From a clone — to change it
 
 ```bash

diff --git a/packaging/PUBLISHING.md b/packaging/PUBLISHING.md
@@ -13,7 +13,10 @@ The files are written and committed:
 | `packaging/winget/SamarTomar.Flow.installer.yaml` | winget installer manifest |
 | `packaging/winget/SamarTomar.Flow.locale.en-US.yaml` | winget en-US description |
 
-Nothing here has been submitted yet. **The manifests are ready to send whenever they carry
+**Submitted on 2026-09-24, as v0.6.1:** Scoop through Flow's own bucket,
+[`samartomar/scoop-flow`](https://github.com/samartomar/scoop-flow), and winget as
+[microsoft/winget-pkgs#440220](https://github.com/microsoft/winget-pkgs/pull/440220).
+**The manifests are ready to send whenever they carry
 a real checksum** rather than the literal string `FILL-ME-SHA256`, which holds the place
 between a version bump and that version's release (step 5). The first was v0.6.0's,
 filled on 2026-09-23 from the `.sha256` the release published and checked against a
@@ -78,71 +81,62 @@ zip. Don't re-run it. Check that it took before submitting
 anything: `git diff` should show those three changed lines and no remaining
 `FILL-ME-SHA256`.
 
-## 2. Scoop: where the manifest lives
+## 2. Scoop: Flow's own bucket
 
-The manifest is finished; the question is which repository it sits in, and there are two
-answers with a real trade between them.
-
-**Your own bucket.** Create `samartomar/scoop-flow`, put the manifest at `bucket/flow.json`
-(Scoop looks in a `bucket/` subdirectory first, then the repository root), and push. Users
-then run:
+**Flow has its own bucket, [`samartomar/scoop-flow`](https://github.com/samartomar/scoop-flow)**,
+made on 2026-09-24 from Scoop's `BucketTemplate`, with this manifest at `bucket/flow.json`.
+Users run:
 
 ```powershell
 scoop bucket add flow https://github.com/samartomar/scoop-flow
 scoop install flow/flow
 ```
 
-**Or submit it to `ScoopInstaller/Extras`.** Fork it, add `bucket/flow.json`, open a pull
-request. Users then run `scoop install extras/flow` with no bucket to add, because
-`extras` is one of the buckets Scoop ships knowing about.
-
-The trade in one sentence: your own bucket ships the moment you push and nobody can tell
-you no, but nobody finds it either unless you hand them the `scoop bucket add` line, while
-`extras` is already on every Scoop install and costs you a review you do not control plus
-a manifest maintained to somebody else's house rules.
-
-Either way the `checkver` and `autoupdate` blocks are what keep it current. `checkver`
-watches this repository's releases; `autoupdate` rewrites the URL for the new version and
-reads the hash out of the `.sha256` asset rather than downloading the zip to compute it.
-In your own bucket, that is driven by the Scoop bucket template's
-`.\bin\checkver.ps1 flow -Update`; in `extras`, their automation runs it for you.
+`ScoopInstaller/Extras` was not asked, for two reasons found while submitting. Scoop's
+main bucket already has a `flow`, Facebook's JavaScript type checker, so Extras would
+need another name; that is also why the install above says `flow/flow`. And Extras takes a
+pull request only after its maintainers have approved a request issue. An own bucket
+ships the moment it is pushed. The price is that nobody finds it without the `scoop bucket
+add` line, which the guide and the bucket's README carry, and the `scoop-bucket` topic,
+which lets scoop.sh index it.
 
-## 3. winget: submitting
+The bucket keeps itself current. Its Excavator workflow runs every four hours: `checkver`
+watches this repository's releases, and `autoupdate` rewrites the URL for the new version
+and reads the hash from the `.sha256` asset rather than downloading the zip to compute
+it. So a release needs nothing done there. The bucket's own `.\bin\checkver.ps1 flow
+-Update` is the same run by hand.
 
-Both tools below open the pull request against `microsoft/winget-pkgs` for you, where the
-files belong at `manifests/s/SamarTomar/Flow/0.6.1/`. Both need a GitHub token with
-`public_repo`, and both will fork the repository under your account the first time.
+## 3. winget: submitted
 
-**wingetcreate** takes the prepared directory as it stands:
+**v0.6.1 is [microsoft/winget-pkgs#440220](https://github.com/microsoft/winget-pkgs/pull/440220)**,
+opened on 2026-09-24 from a fork under the owner's account, with the three files at
+`manifests/s/SamarTomar/Flow/0.6.1/`. Two things changed on the way in:
+- The moniker is `flow-dictation`. `flow` belongs to MadrasCheck.flow, and monikers are
+  unique. The command on PATH is still `flow`.
+- The manifests moved to schema 1.12.0, which the pull request template asks for.
 
-```powershell
-wingetcreate submit --token <github-token> packaging\winget
-```
+They were sent without this directory's explanatory comments, and `winget validate`
+passed on the exact files sent.
 
-It validates the three files first, so a `FILL-ME-SHA256` that was not replaced fails here
-rather than in front of a reviewer. That failure is expected and is the whole reason the
-placeholder is a word rather than a plausible-looking string of hex.
+Microsoft's bot asks the owner to accept its CLA on the pull request, by replying
+`@microsoft-github-policy-service agree`. Validation then installs the package on a
+clean VM, and a first package from a new publisher is reviewed by a person.
 
-For the *next* version, the shorter path is to let it build the manifests from the release:
+**For the next version**, wingetcreate builds the update from the release. It needs a
+GitHub token with `public_repo`:
 
 ```powershell
 wingetcreate update SamarTomar.Flow --version 0.6.2 --urls https://github.com/samartomar/flow/releases/download/v0.6.2/flow-windows-x64.zip --submit --token <github-token>
 ```
 
-**komac** does the same job and computes the checksum itself, from the URL these prepared
-files name, so the placeholder never has to be filled on this path:
+komac does the same job and computes the checksum itself, from the URL:
 
 ```powershell
-komac update SamarTomar.Flow --version 0.6.1 --urls https://github.com/samartomar/flow/releases/download/v0.6.1/flow-windows-x64.zip --submit
+komac update SamarTomar.Flow --version 0.6.2 --urls https://github.com/samartomar/flow/releases/download/v0.6.2/flow-windows-x64.zip --submit
 ```
 
-To send the prepared files verbatim instead of regenerating them, komac takes the
-directory: `komac submit packaging\winget`. Its flags move between major versions more
-than wingetcreate's do, so check `komac --help` if it argues.
-
-After either submission the pull request runs Microsoft's validation, which installs the
-package on a clean VM. A portable zip has little to fail on, but the run is not instant
-and a first submission from a new publisher is reviewed by a person.
+Its flags move between major versions more than wingetcreate's do, so check
+`komac --help` if it argues.
 
 ## 4. The binary is unsigned, and that does not change here
 

diff --git a/packaging/winget/SamarTomar.Flow.installer.yaml b/packaging/winget/SamarTomar.Flow.installer.yaml
@@ -1,4 +1,4 @@
-# yaml-language-server: $schema=https://aka.ms/winget-manifest.installer.1.6.0.schema.json
+# yaml-language-server: $schema=https://aka.ms/winget-manifest.installer.1.12.0.schema.json
 
 # What winget downloads and what it does with it.
 #
@@ -32,4 +32,4 @@ Installers:
     InstallerUrl: https://github.com/samartomar/flow/releases/download/v0.6.1/flow-windows-x64.zip
     InstallerSha256: d2fa70e54318b8766b721b6465059f1a9d83888d3e35469c46ddf193782713d1
 ManifestType: installer
-ManifestVersion: 1.6.0
+ManifestVersion: 1.12.0
diff --git a/packaging/winget/SamarTomar.Flow.locale.en-US.yaml b/packaging/winget/SamarTomar.Flow.locale.en-US.yaml
@@ -1,4 +1,4 @@
-# yaml-language-server: $schema=https://aka.ms/winget-manifest.defaultLocale.1.6.0.schema.json
+# yaml-language-server: $schema=https://aka.ms/winget-manifest.defaultLocale.1.12.0.schema.json
 
 # The text a stranger reads in `winget show SamarTomar.Flow` and in the Store listing that
 # mirrors this repository. Every claim below is one the README already makes, written in
@@ -17,22 +17,25 @@ LicenseUrl: https://github.com/samartomar/flow/blob/main/LICENSE
 Copyright: Copyright (c) 2026 Samar Tomar
 ShortDescription: Local English dictation with a talk-to-it refine loop
 Description: |-
-  Dictate into whatever window you were working in, fix the text by talking to it, then
-  send. Click the pill or press ctrl+alt+space and talk; the draft floats above it and
-  refreshes about once a second. Talk to the draft to correct it - "change Tuesday to
-  Wednesday", "delete the last sentence" - or press Edit and type. Send pastes it back
-  into the window you came from.
+  Hold ctrl+win (or the pill), talk, and let go: the words paste into the window you were
+  working in. Said it wrong? Hold again and say "change Tuesday to Thursday" or "scratch
+  that", and Flow fixes what it just pasted. Tap the pill to change mode: Type pastes;
+  Refine turns what you said into a prompt for your project, written by the agent CLI you
+  already use; Ask puts a question to it and shows the answer above the pill. Flow Home is
+  one window for the speech models, the microphone, a tuning to your voice, a history if
+  you choose to keep one, and the settings.
 
   Speech recognition runs on the machine with faster-whisper, so no audio leaves it and
-  there is no API key. English only. An agent CLI - codex or claude, on PATH and already
-  signed in - is optional and adds semantic rewrites, the prompt polish and converse mode;
-  without one, everything else works and startup says so.
+  there is no API key. English only. The agent CLI - codex or claude, on PATH and already
+  signed in - is optional: without one, dictation and spoken corrections still work.
 
-  The models are not in the download. They are fetched to the Hugging Face cache on the
-  first decode, the same way a source install fetches them, and the startup line names the
-  path. The build is unsigned, so the first launch shows the Windows SmartScreen panel and
-  takes More info then Run anyway, once, per machine.
-Moniker: flow
+  The speech models are not in the download. They are fetched to the Hugging Face cache
+  the first time Flow needs them, with progress in Flow Home. The build is unsigned, so the
+  first launch shows the Windows SmartScreen panel and takes More info, then Run anyway,
+  once per machine.
+# `flow` is MadrasCheck.flow's moniker in winget, and monikers are unique there. The
+# command this package puts on PATH is still `flow` (the installer manifest's alias).
+Moniker: flow-dictation
 Tags:
   - dictation
   - speech-to-text
@@ -42,4 +45,4 @@ Tags:
   - voice
   - hotkey
 ManifestType: defaultLocale
-ManifestVersion: 1.6.0
+ManifestVersion: 1.12.0
diff --git a/packaging/winget/SamarTomar.Flow.yaml b/packaging/winget/SamarTomar.Flow.yaml
@@ -1,4 +1,4 @@
-# yaml-language-server: $schema=https://aka.ms/winget-manifest.version.1.6.0.schema.json
+# yaml-language-server: $schema=https://aka.ms/winget-manifest.version.1.12.0.schema.json
 
 # The version manifest: the smallest of the three, and the one that says which locale is
 # authoritative. A winget submission is this file plus the installer and the defaultLocale
@@ -8,4 +8,4 @@ PackageIdentifier: SamarTomar.Flow
 PackageVersion: 0.6.1
 DefaultLocale: en-US
 ManifestType: version
-ManifestVersion: 1.6.0
+ManifestVersion: 1.12.0