gflow-cli 0.83.1__tar.gz → 0.84.0__tar.gz

{gflow_cli-0.83.1 → gflow_cli-0.84.0}/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "gflow",
-  "version": "0.83.1",
+  "version": "0.84.0",
   "description": "Reusable development and operations workflows for gflow-cli",
   "author": {
     "name": "Flavio Oliva",

{gflow_cli-0.83.1 → gflow_cli-0.84.0}/AGENTS.md

@@ -136,7 +136,7 @@ the five other mirror axes), which no command here can check and no CI gate can
   drifts, which is the exact failure this row exists to prevent.
 - **Locale-Invariance Discipline for UI Automation**: **Never** write text-label string selectors (`has-text(...)` or multi-locale text lists) for DOM elements, overlays, announcements, menus, tabs, or buttons. All DOM selectors in `src/gflow_cli/api/transports/` must be 100% language-agnostic, anchoring exclusively on structural properties: **Tier 1 Anchors** — e.g. hyperlinks (`a[href*='changelog']`), icon ligatures (`button:has(i.google-symbols:text('close'))`), ARIA roles (`[role='banner']`, `button[data-dismiss]`), and hierarchical DOM relationships (`[role='dialog']:has(a[href*='changelog']) button`). Relying on translated display labels or maintaining multi-locale text cascades is strictly forbidden as an anti-pattern hack.
 
-  **One measured exception: a format token that is not a word.** Flow's upscale download
+  **First measured exception: a format token that is not a word.** Flow's upscale download
   menu gives its items no attribute or icon, and their order changes, but each label carries
   a resolution token (`2K`, `1080p`) that measured identical in English and Portuguese while
   the words around it were translated (#922, `scripts/dev/spike_upscale_menu_anchors.py`).
@@ -144,6 +144,13 @@ the five other mirror axes), which no command here can check and no CI gate can
   for any further exception: no structural anchor exists, the token is measured on 2+
   locales, and a miss raises exit 23 rather than clicking the wrong item.
 
+  **A second, on the same bar: the duration radio's number.** The settings pane's
+  duration radios carry only Angular instance counters, and their unit is translated
+  (`8s` in English and Portuguese, `8 giây` in Vietnamese) while the number is not (#963,
+  [spike](docs/superpowers/spikes/2026-10-10-duration-locale-and-notice-only-cookie-bar.md)).
+  `migrated_composer._duration` matches the number and refuses a `4K`/`480p` sibling; a
+  miss raises exit 11.
+
 - **Host-Membership Discipline**: say which host Flow **served**; never use host
   membership to assert a **capability**. "This account is migrated, therefore X is
   unavailable" is an inference the evidence does not support, and **"X is labs-only" is

{gflow_cli-0.83.1 → gflow_cli-0.84.0}/CHANGELOG.md

@@ -7,6 +7,57 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.84.0] — 2026-10-12
+
+### Added
+
+- **`gflow run --project ID` generates a batch into an existing Flow project (#970).** Every
+  run used to create a new project titled `gflow-cli run`, so a user who keeps their
+  images in one project had to fall back to one `gflow image t2i --project` call per
+  prompt. `--project` (or a top-level `"project"` key in the config; the CLI wins) now
+  runs every row in that project and creates none, and a title already in the local
+  catalog is kept, as with `t2i --project`. `gflow run` has no MCP twin yet, so
+  there is no MCP option to mirror.
+- **`gflow image t2i` takes `--project` with several prompts (#971).** A multi-prompt run
+  (several positional prompts, `--prompts-file` or `--stdin`) used to reject
+  `--project` as single-prompt only; it now runs every prompt in that project and
+  creates none, on the same path as `gflow run --project`. `--reference-entity` stays
+  single-prompt only. The MCP image tool takes one prompt, so there is nothing to
+  mirror.
+
+## [0.83.2] — 2026-10-11
+
+### Fixed
+
+- **`--duration` failed before submit on a Flow account whose UI is not in English
+  (#963).** On `flow.google.com` the duration radio was matched on its exact English
+  label (`8s`), so a Vietnamese pane reading `8 giây` matched nothing and every run with
+  `--duration` stopped with exit 11, before any credit was spent. The radio is now matched
+  on its number, refusing a `4K`/`480p` sibling that shares the leading digit. CLI and MCP
+  share this transport, so both are fixed.
+
+- **A notice-only cookie bar blocked every run on `flow.google.com`, at exit 23.** Some
+  languages are served a consent bar with only an *OK, got it* button and no reject
+  option; the driver looked only for reject, so the bar stayed over the settings control.
+  It now clicks reject where the bar offers one and acknowledges the notice only when it
+  does not. Found while live-checking #963 under a Vietnamese UI.
+
+- **`gflow image upscale` on `flow.google.com` failed with *Element is not attached to
+  the DOM* (#957).** The image tile and the download button were held as element handles
+  resolved once, and Flow re-renders the grid after it first appears, so the click landed
+  on a detached node. They are now Playwright locators, re-resolved on every action. Video
+  upscale opens its download menu through the same helper, so it shares the fix; the MCP
+  tools call the same transport. Image upscale was verified live on the CLI and over MCP.
+
+- **`gflow auth status` reported a migrated account as not signed in to Flow on hosts
+  without Google Chrome (PR #962, by @mohaidoss).** For a `flow.google.com` account, the migrated-host probe opened
+  the profile with a hard-coded `channel="chrome"`. Playwright resolves that only to
+  `/opt/google/chrome/chrome` on Linux. On a host with just the bundled Chromium the launch
+  raised, the probe logged `auth_migrated_fallback_probe_error`, and status printed
+  *"Signed in to Google, but not to the Flow app"*, even though generation, which picks its
+  channel with `channel_for_profile`, ran fine on the same profile. The probe now opens the
+  profile with that same resolver and runs the #477 engine-downgrade guard first.
+
 ## [0.83.1] — 2026-10-08
 
 ### Fixed
@@ -5977,7 +6028,9 @@ shell-script template that branches on these codes.
 
 First skeleton. Not functional end-to-end yet.
 
-[Unreleased]: https://github.com/ffroliva/gflow-cli/compare/v0.83.1...HEAD
+[Unreleased]: https://github.com/ffroliva/gflow-cli/compare/v0.84.0...HEAD
+[0.84.0]: https://github.com/ffroliva/gflow-cli/compare/v0.83.2...v0.84.0
+[0.83.2]: https://github.com/ffroliva/gflow-cli/compare/v0.83.1...v0.83.2
 [0.83.1]: https://github.com/ffroliva/gflow-cli/compare/v0.83.0...v0.83.1
 [0.83.0]: https://github.com/ffroliva/gflow-cli/compare/v0.82.1...v0.83.0
 [0.82.1]: https://github.com/ffroliva/gflow-cli/compare/v0.82.0...v0.82.1

{gflow_cli-0.83.1 → gflow_cli-0.84.0}/KNOWN_ISSUES.md

@@ -396,8 +396,8 @@ has not landed yet stay nameless until the next sync sweep.
 - **Status:** Open · **Severity:** Low (a re-run regenerates; nothing is lost) · **Affected:** every `gflow run --config` with `"ref"` rows (`batch:N` or a local file)
 - **Tracked:** [#913](https://github.com/ffroliva/gflow-cli/issues/913)
 
-A run with `"ref": "batch:N"` rows has no resume: a re-run creates a new project and
-regenerates every row, parents included, and one early failure skips the whole chain under
+A run with `"ref": "batch:N"` rows has no resume: a re-run creates a new project (or, with
+`--project`, reuses that one) and regenerates every row, parents included, and one early failure skips the whole chain under
 it. The handle that makes in-place referencing work (Flow's reply for the parent) exists
 only within the run that generated it. A local-file `ref` is uploaded again into the
 re-run's new project for the same reason.
@@ -416,6 +416,12 @@ re-run's new project for the same reason.
 
 **Workaround:** omit `--duration` and accept Flow's default clip length.
 
+**Not this issue if your Flow UI is not in English.** Before v0.83.2, a translated duration
+unit (`8 giây` in Vietnamese) also raised exit 11 on `flow.google.com`, because the radio
+was matched on its English label ([#963](https://github.com/ffroliva/gflow-cli/issues/963)).
+Upgrade first (`gflow update`). The locale refutation below applies to the Portuguese
+labs cohort it was measured on.
+
 **What actually happens today.** gflow accepts `--duration 4`, `6` or `8` on the
 Veo 3.1 models and `10` on `omni-flash` only — the CLI no longer refuses a
 duration it cannot know your account supports. What it still cannot do is tell

{gflow_cli-0.83.1 → gflow_cli-0.84.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: gflow-cli
-Version: 0.83.1
+Version: 0.84.0
 Summary: CLI and MCP server for Google Flow — drive Veo text-to-video, image-to-video and Imagen image generation from the terminal.
 Project-URL: Homepage, https://github.com/ffroliva/gflow-cli
 Project-URL: Documentation, https://ffroliva.github.io/gflow-cli/

{gflow_cli-0.83.1 → gflow_cli-0.84.0}/docker/Dockerfile

@@ -45,7 +45,7 @@ RUN apt-get update && apt-get install -y --no-install-recommends \
 # Deliberately NOT pinned: google-chrome-stable. Chrome's apt repo keeps only the current
 # build, so a pinned version stops resolving within weeks. The trade-off is that this
 # layer caches indefinitely and a rebuild is what picks up a newer Chrome.
-ARG GFLOW_VERSION=0.83.1
+ARG GFLOW_VERSION=0.84.0
 RUN pip install --no-cache-dir "gflow-cli==${GFLOW_VERSION}"
 
 VOLUME ["/data"]

{gflow_cli-0.83.1 → gflow_cli-0.84.0}/docs/ACCOUNT_SAFETY.md

@@ -57,8 +57,8 @@ prompts*, and is a different mechanism from the ±25% per-interaction jitter abo
 
 **One project per run, not one per prompt.** Repeated `project.createProject`
 calls between generations add to the bot-like signature, so multi-prompt runs
-create a single shared project, and `--project` lets repeated single-prompt runs
-reuse a standing one.
+create a single shared project, and `--project` lets repeated runs reuse a standing
+one — single-prompt `t2i`/`i2i`, multi-prompt `t2i`, and `gflow run` then create none.
 
 **Each account gets its own isolated browser profile** under `GFLOW_CLI_HOME`.
 The tool never touches your everyday Chrome profile, and profiles do not share
@@ -91,7 +91,7 @@ pacing is defensible; a stealth feature that fails silently in six months is not
 | Knob | When to reach for it |
 |---|---|
 | `--jitter 10-30` / [`GFLOW_CLI_JITTER_RANGE`](CONFIGURATION.md#gflow_cli_jitter_range) | After a 403, or before a large batch. Widens the between-submission pause. `--jitter 0` disables pacing entirely (don't) |
-| `--project <id>` | Repeated single-prompt runs — avoids project churn |
+| `--project <id>` | Repeated runs (`t2i`, `i2i`, multi-prompt `t2i`, `gflow run`) — avoids project churn |
 | [`GFLOW_CLI_BROWSER_ENGINE=patchright`](CONFIGURATION.md#gflow_cli_browser_engine) | Opt-in patched Playwright that avoids the `Runtime.enable` CDP leak, for stronger reCAPTCHA-Enterprise evasion on the **headed** path. Install separately (`pip install patchright`). Not a headless unlock |
 | `--profile <name>` | Spread work across profiles; a profile that has been driven hard is the "hottest" |
 

{gflow_cli-0.83.1/website → gflow_cli-0.84.0}/docs/DEBUGGING.md

@@ -342,7 +342,8 @@ Practical guidance:
   between generations) adds to the bot-like signature. For repeated
   single-prompt runs (`t2i`, `i2i`), pass `--project` to reuse a standing
   project. Multi-prompt runs already create only **one** shared project per
-  run (never one per prompt).
+  run (never one per prompt), and `t2i` / `gflow run` take `--project` to
+  create none.
 
 ## Common failure modes
 

{gflow_cli-0.83.1 → gflow_cli-0.84.0}/docs/INDEX.md

@@ -171,7 +171,7 @@ Slash commands for Claude Code, stored in `.claude/commands/gflow/`. All prefixe
 **"A command failed — where is the incident bundle and what's in it?"** → [DEBUGGING § Automatic incident bundles](DEBUGGING.md#automatic-incident-bundles) (layout, triggers, review-before-sharing); privacy boundaries: [SECURITY § Automatic incident bundles](SECURITY.md#automatic-incident-bundles-gflow_cli_incident_capture-default-on); disable via [CONFIGURATION § GFLOW_CLI_INCIDENT_CAPTURE](CONFIGURATION.md#gflow_cli_incident_capture)
 **"Flow's UI broke a selector — how do I diagnose it?"** → [DEBUGGING § Inspecting Flow's live UI](DEBUGGING.md#inspecting-flows-live-ui)
 **"What does each `ui_automation.*` log event mean?"** → [DEBUGGING § Listener & HTTP-layer debugging](DEBUGGING.md#listener--http-layer-debugging)
-**What was actually live-verified for the latest release?** → latest: [LIVE_VERIFICATION_v0.83.1](LIVE_VERIFICATION_v0.83.1.md) (**2026-10-08, 0 credits.** #958: the default image model `nano2` runs Nano Banana 2.1 on flow.google.com — e2e failed on develop and passed after the fix; CLI and MCP twins each wrote a JPEG; 2.1 measured as replacing 2 on two accounts) · previous: [LIVE_VERIFICATION_v0.83.0](LIVE_VERIFICATION_v0.83.0.md) (**2026-10-06/07.** #948: a billed flow.google.com video run no longer exits 7 — t2v, i2v and r2v e2e passed after the fix, reproduced before it; `data download` e2e 2 passed after a 302 regression was caught and fixed; #922: image and video upscale e2e passed, CLI and MCP image twins wrote the same JPEG, MCP video wrote 1920x1080, a 1080p export measured 0 credits) · previous: [LIVE_VERIFICATION_v0.82.1](LIVE_VERIFICATION_v0.82.1.md) (**2026-10-02.** A reCAPTCHA mint failure typed with a live-measured retry flag (#915, e2e 2 passed, $0); a busy catalog no longer fails a successful generation (#900, real SQLite, no Flow surface); a video's workflow id recorded (#898, 1 veo-lite clip)) · previous: [LIVE_VERIFICATION_v0.82.0](LIVE_VERIFICATION_v0.82.0.md) (**2026-10-01.** `"ref": "batch:N"` and local-file refs on `gflow run` verified by a BDD e2e on flow.google.com: in place, no re-upload, lineage recorded; 1 veo-lite clip for the #926 e2e) · previous: [LIVE_VERIFICATION_v0.81.0](LIVE_VERIFICATION_v0.81.0.md) (**2026-09-30, 3 veo-lite clips.** The off-screen generation browser (#923) measured unchanged for image and video, window placement read back from Chrome, focus-steal measured and documented; #919 verified at merge) · previous: [LIVE_VERIFICATION_v0.80.0](LIVE_VERIFICATION_v0.80.0.md) (**2026-09-29, 0 Veo credits.** `--resolution` 360p/720p proven by driving the real settings pane on `omni_flash` and refusing the credit-spending submit, on the CLI transport **and** the MCP twin; `nano2-lite` e2e 2 passed; #891 measured before/after — `gflow run` `[nano2, imagen4]` went from exit 1 `RecaptchaError` with a lost results table to exit 36 naming the model, plus 3 e2e (fresh, warm, MCP) with a spy asserting zero client mints; #896 `e2e_data` 2 passed, its failure path offline-only. Named blockers: rendered resolution (needs a billed clip), the `/about` re-check arm, labs-served accounts.) · previous: [LIVE_VERIFICATION_v0.79.1](LIVE_VERIFICATION_v0.79.1.md) (**the signed-media download survives a dropped connection, verified 2026-09-22 at $0.** All three download sites route through one new shared helper, and that helper was driven through a real Flow clip route and a real signed CDN transfer by `pytest -m e2e_data` — 2 passed in 20.74 s, `ftyp` magic, byte length equal to the size Flow reports, and **no `url=` on any log event**. The retry itself could not wait for an organic reset — 20/20 clean here against the reporter's 2-in-6 — so it was **measured against a real TCP RST with an A/B control**: with `max_retries` the transfer recovers on a second connection, with it disabled the identical fault kills the call, and three attempts at a 5 s timeout finish in 1.57 s rather than ~15 s, proving the backoff shares one budget. **Two sites are NOT live-verified and name their blockers:** the composer call site needs a billed generation and `gflow credits` answers 401 on this account (#795), so no credits were spent; and the labs download cannot be reached at all from here (HTTP 308, 6/6 profiles). Offline: 21 new tests, full sweep 2143 passed.) · earlier: [LIVE_VERIFICATION_v0.79.0](LIVE_VERIFICATION_v0.79.0.md) (**the migrated host stops echoing a model it never observed, verified 2026-09-18 at $0.** `model_name_type` is `null` on `flow.google.com` in a real `image t2i --json`, with every sibling field populated — which is what makes the null a result rather than an empty envelope; the first read of it was flat rather than into `images[]` and returned `None` for everything, and that instrument error was discarded rather than reported. Both surfaces ran: `test_e2e_t2i_runs_on_a_moved_account` and `test_e2e_mcp_i2i_runs_on_the_migrated_host`, 2 passed in 86 s. **`gflow data download` was tested on an image and failed** — 45 s, then a message blaming the project, the trash and your prompt; recovery is video-only and the release notes now say so (#877). **#803 is NOT live-verified and names its blocker:** reaching those raise sites needs a non-JSON or token-less aisandbox reply, and the labs route refuses first with a 404 — itself a misleading error, filed as #875. Offline: 4 new unit tests, 1775 passed.) · previous: [LIVE_VERIFICATION_v0.78.0](LIVE_VERIFICATION_v0.78.0.md) (**generating with no project on `flow.google.com` — and video from a start frame — verified 2026-09-17.** The release exists because labs.google's `project.createProject` is retired — 404 *"Flow RPCs have been deprecated and disabled"* with a labs token, 401 without, 0 successes in 12 across four profiles — and gflow reported the 401 as an expired login. Creation and rename are driven on flow.google.com and read back from Flow's own `jHPbke` / `o8DA4` replies; the CLI and the MCP twin are each exercised separately, and both video paths reach a real submit that is aborted before Flow can bill it. Two failures are recorded and re-tested rather than explained away — one MCP image reply that did not reproduce under a four-run A/B, and a Chrome launch starved by a concurrent coverage run that passed in 36 s alone. The 3:4 image aspect is re-measured on the live radiogroup, five radios where 2026-09-08 saw four. Three items are NOT verified and each names its blocker: no labs-served account, no entitled `/about` account, no non-`en` locale. **#860 is the one thing here that cost credits, deliberately:** the only proof that a start frame binds is a real generation, so ten i2v clips were generated and downloaded on a live migrated account — `migrated.frame_uploaded` → `frame_bound` → `submit_observed` → `download`, the middle event being the one that could not fire before this release. **#859 is recorded as UNOBSERVED, not verified** — its dismissal ran on every one of those runs and no promo modal ever appeared, so the $0 route-intercepted e2e is what covers it. `gflow docs` (#861) is verified from the built wheel, which is its whole contract: 127 topics, `docs/FILE.md:LINE` search hits, no network and no checkout.) · previous: [LIVE_VERIFICATION_v0.77.1](LIVE_VERIFICATION_v0.77.1.md) (**a four-fix patch release, verified 2026-09-17 at ZERO cost.** The headline is #846: the published package could not run a single interactive command on a clean Windows install, because `ConsoleRenderer(colors=True)` needs `colorama` and nothing declared it. Verified as a controlled A/B on a fresh Python 3.13 venv — `SystemError` before, exit 33 after — plus an arm with stderr piped that shows why the AUTO/JSON split hid this from every CI job, and the MCP twin run separately. #848's import probe is exercised against a **deliberately broken venv** and an intact one, including the contract that a probe which cannot run reports nothing rather than reporting breakage. #852 is re-measured on the release head: 40 000 base64-shaped chars fall from 12.07 s to 0.020 ms with identical output on Workspace and custom domains. **#849 is a NAMED BLOCKER, not an omission** — its end-to-end behaviour needs a fresh interactive Google sign-in, which no agent can perform; its live A/B is recorded on PR #851 and its e2e file re-ran 4/4 here. **Seven live e2e failures are recorded rather than hidden**, and controlled: the release changes exactly four source files and none of them is a failing test's module.) · previous: [LIVE_VERIFICATION_v0.77.0](LIVE_VERIFICATION_v0.77.0.md) (**the migrated-host login lockout (#791), verified as a controlled A/B on a real Google **Workspace** account at ZERO cost — same profile, same cookies untouched between arms, so the only variable is the code: exit 8 with the Chrome marker rolled back and `channel_for_profile` collapsed to `None`, then exit 0 with the marker intact and the account recorded. The refusal path is measured too — of 10 local profiles, 5 reproduce #791 and exactly one carries both required cookies: 4 refusals, 1 upgrade, 0 false positives. v0.76.0 recorded this fix as **withdrawn**; the approach that shipped is a different one, server-attested on the landing URL rather than on client-rendered DOM. An earlier revision gated auth on an `@gmail.com`-only pattern that silently declined every custom domain — the account used here is one, which is why this is its verification. **#796 is reproduced and prevented**, not merely reported: it was filed as *'not yet reproduced end-to-end'*. **Two rows are named blockers, not omissions:** the MCP Registry publish (#841) cannot be rehearsed before a real tag push, so this release is its first exercise; and the migrated-host generation e2e cannot run here at all — every account bounces to `/about`, A/B-controlled against `develop` so it is not mistaken for a regression.) · previous: [LIVE_VERIFICATION_v0.76.0](LIVE_VERIFICATION_v0.76.0.md) (**a diagnostics-and-distribution release, verified 2026-09-16 at ZERO cost — no Veo credits, no image generation, no Flow submit.** The decisive arm is #833's **negative** control, run first-hand on two real accounts rather than relayed: `flow-pinhole-unavailable-screen` is **0** on both `ffroliva` and `denon82` while `aisandbox-root` is **1**, so the guard does not fire on accounts that HAVE Flow access and the zero is a real absence rather than a page that never booted — a guard with only a positive arm is indistinguishable from one that is permanently on. Both accounts settled at **`/about`**, which is the state that broke this release's *withdrawn* #791 oracle, and the exit-39 signal reads a component that only exists on the unavailable screen, so `/about` cannot mimic it. mcpservers.org is verified with a **404 negative control** because the listing 403s to `curl` and a naive check would have called the link dead. **#791 is NOT in this release and was withdrawn rather than deferred**: a fix passed eight council dimensions and was then refuted by a five-day-old spike nobody had routed to it — Flow's `/about` hop is decided client-side with zero requests to Flow, and *"the backend grants access while the frontend declines to open it"* (#756), so the probe would have reported authenticated users as logged out, reintroducing #791 as its own cure; the e2e caught it by going red on a live account whose state moved mid-session. **Two rows are blocked by the platform rather than by effort:** the Docker sign-in needs a WSL-integrated Docker host, and the MCP Registry publish cannot be observed until this very tag reaches `main`, since both triggers resolve the workflow from the default branch.) · previous: [LIVE_VERIFICATION_v0.75.0](LIVE_VERIFICATION_v0.75.0.md) (**a distribution-and-hardening release, verified 2026-09-15 on `ffroliva` at ZERO cost — no Veo credits, no image generation, no Flow submit.** The `gflow serve` token fix is an **A/B against the released 0.74.0 wheel from PyPI**, not a diff read: the token was *set* in both arms, so the probe measures whether it is checked — before, `no token 200/200` with 13 tools listed and `wrong 200/200`; after, `401/401` with zero tools and `WWW-Authenticate: Bearer realm="gflow"`, while the correct token still gets 200. Loopback DNS-rebinding was re-confirmed at **421**/**403** because the fix forwards the bind host and getting that wrong would silently disable protection that works today — and an earlier draft of the accompanying advisory claimed that protection was *disabled*, a false claim caught by measuring rather than re-reading. #813's guard is verified against a **real wheel in a real venv installed without extras**, the arm first proving it is in that state (`av present: False  PIL present: False`); the decisive row is that a **nonexistent** manifest still exits **20** on the dependency error rather than file-not-found, which is what shows the guard precedes the manifest read and not merely the generation. The Rich escape fix is verified on the **console render separated from the structlog JSON** — matching the JSON line would have been a false pass, since `--json` was never affected — with a **neutered control** through the same Rich version reproducing the bug exactly: `UNESCAPED -> pip install 'gflow-cli'` against `ESCAPED -> pip install 'gflow-cli[chain]'`. Also: `gflow-cli.exe` exists in the built wheel so `uvx gflow-cli` resolves at all, and the wheel carries 138 entries with **zero** ZIP duplicates. **Three items recorded as NOT verified rather than omitted:** a successful multi-link `chain` run spends Veo credits and stays outstanding e2e debt on #813 — what changed is the refusal path, which *is* verified; `gflow credits` against a working balance is impossible here because the account still returns 401, pre-existing **#795** and unrelated to this release; and the SSE arm of the token fix was exercised on loopback only, a deliberate scope limit, since binding a LAN address to test it would put an authenticated daemon on a live network for the run. **Two rows are blocked by the platform rather than by effort:** the PyPI metadata and the MCP Registry listing are both unobservable until this release is uploaded — PyPI renders the last artefact's metadata, and `mcp-publisher` reads its ownership token out of the *published* README.) · previous: [LIVE_VERIFICATION_v0.74.0](LIVE_VERIFICATION_v0.74.0.md) (**the migrated driver's run-unique uploads and its Frames-picker confirm, plus the `credits` remediation, verified 2026-09-14 on `ffroliva` at ZERO cost — every arm is a read or an upload-and-stop.** The confirm branch is the interesting one: this cohort's picker closes on its own, so the branch would never execute against live Flow by accident, and the e2e drives `FRAME_COMMIT_GRACE_S` to **0.001** so the grace expires before Flow can auto-close and **every** run enters it — the difference between a named blocker and an unrun claim. A *genuinely stuck* picker still cannot be produced here and stays `Refs #792`, verifier the reporter. #795 was verified on the cohort it is for, because this account is now in it — `auth status` green, `credits user` exit **3** with `detail` `credits endpoint returned 401` and `route: credits`, where v0.73.2 printed the class-default *"SAPISID cookie missing… re-run `gflow auth login`"*, advice that is wrong in every word there and that can roll a profile's strategy marker back and start the #791 spiral; the `credits list --json` envelope carries the per-profile `remediation_hint` that used to be dropped. **Two items recorded as NOT verified rather than omitted:** #799's exit-25 raise site needs an account in the agent-only cohort — the maintainer's accounts are served `flow.google.com` but still have the recoverable agent chip, so the state is structurally unreachable on them, a named blocker and #799 stays open; and neither `r2v` nor `i2i` had its own attach path driven to completion — `r2v` was not attempted (its e2e spends Veo credits), while `i2i` **was** attempted twice and failed both times at exit 23, before reaching the code under test, because the `--project` UUID came from `gflow project list` (the aisandbox catalog) and those ids 404 on `flow.google.com` — a harness error, recorded rather than dropped, which left a side finding: gflow reports Flow's own `/404?reason=project` as `UiSelectorDriftError`, blaming our selectors for Flow's 404. **#791 is not fixed and was not attempted blind** — all nine local profiles were probed at $0 and none is in the #791 state (SAPISID + a live `flow.google.com` session + no labs NextAuth token); four print its exact symptom string and none of them is it, because that string is also what a stale profile says.) · previous: [LIVE_VERIFICATION_v0.73.2](LIVE_VERIFICATION_v0.73.2.md) (**the blank incident bundle, reproduced and then cured by a committed e2e test, 2026-09-12 on `ffroliva` at ZERO cost — every arm fails before submit.** The decisive layer is an **A/B run through the same instrument**, not an inspection: on `develop` the new test FAILS in 46.3 s and prints the bundle it got — `tag_counts.div = 0`, `title.length = 0`, `host_category = "other"`, a 4,254-byte screenshot — which is field-for-field the signature [#792](https://github.com/ffroliva/gflow-cli/issues/792) reported from a different account, a different OS and a different command; on the fix it PASSES in 37.8 s with `div` **25**, `title.length` **81**, `host_category` **`flow_app`**, `route` `/404` and a 38.4 KB screenshot. Both arms exit **23** on the same `.settings-trigger-button` drift at `flow.google.com/404?reason=project`, so the arms differ only in what was *captured*, never in what failed. **The reporter's own bundle contained the refutation of their diagnosis**: viewport 1280x720 is `client.py`'s client-owned page, not the 1920x1080 a stray transport tab would have — it was always the driven page, photographed one navigation too late, and the portrait correlation had no mechanism behind it. The existing quality benchmark could not have caught this: it captures deliberately on a **healthy** page, so it graded only bundles that were never at risk. **Recorded as NOT verified rather than omitted:** #796's `PROFILE_MARKER_MISSING` is offline-only because its live trigger is a cookie-store **decryption** failure, which does not occur on Windows/DPAPI — it is the macOS Keychain path of [#768](https://github.com/ffroliva/gflow-cli/issues/768), a **named external blocker**, and the issue stays open; a synthetic attempt to force it failed informatively, since a corrupt store raises `sqlite3.DatabaseError`, bypasses the marker gate and still prints "check network connectivity" — the same misdirection from a different trigger, untouched here. #795's remediation string is unit-asserted only, and the *other* half of #795 — `credits` being labs-only on migrated accounts — is **not fixed**.) · previous: [LIVE_VERIFICATION_v0.73.1](LIVE_VERIFICATION_v0.73.1.md) (**Google's `glue` consent bar covering the migrated composer, measured and then cured, 2026-09-11 on `ci-probe` for one image generation and no Veo credits.** The premise was nearly rejected: both prior sightings of that selector in this repo are labs.google, and the 2026-09-10 spike had read 159 DOM samples on this exact host and project and watched the click land 3/3 — it simply never looked for a cookie bar. Seventeen hours later the bar was up: `position: fixed`, `z-index: 1000`, spanning y 547-655 of a 655 px viewport, with `elementFromPoint` over the settings trigger AND over the image submit both returning `span#glue-cookie-notification-bar-1-label` in **0 of 5** rendered samples hit-testable. **The control arm is what makes it a cure rather than a coincidence**: the same probe re-run through the driver's own `_dismiss_cookie_bar` restored both controls to **4/4**, one attempt, no error. A full `gflow image t2i` then ran end to end on the merged code — `status: ok`, a 807,761-byte `ffd8ffe0` JPEG that Pillow reads as 1376x768 RGB, matching the requested 16:9 and the reply's own dimensions, with `migrated.editor_ready` at 2.0 s and **no** `cookie_bar_not_dismissed`. A side finding the control arm produced by accident: the bar's buttons are `__accept` then `__reject` in DOM order, so anything taking "the first button" accepts cookies for the operator — the shipped fix anchors on reject. **Three items recorded as NOT verified rather than omitted:** the cure against a live bar outside the browser, because this release's own control arm consumed the consent on the only profile that had it; **prevalence**, because the second profile never reached an editor (both arms redirected to `/about`) so it is one account blocked and one already-consented, and KNOWN_ISSUES says so rather than generalising from n=1; and the video path live, which shares the identical function on the identical control but spends Veo credits.) · previous: [LIVE_VERIFICATION_v0.73.0](LIVE_VERIFICATION_v0.73.0.md) (**four error paths that stopped lying about what went wrong, verified 2026-09-10 on `ci-probe` and `denon82` at $0 — no run below reaches a Veo submit.** The decisive arm is an **A/B**, not an inspection: the pre-fix run printed an `accounts.google.com` challenge URL together with the OAuth `state` and `client_id`, and the identical command after the fix gave the same exit 38 and the same landing named with **five secret matches down to zero** — reading the post-fix output alone would only have shown that *these* secrets were absent. A second arm **falsified a claim already written into PR #775's body**: it said the change fixed the RED canary, and the live run showed `denon82` had moved to `accounts.google.com` mid-run, a landing the classifier excluded **by design**, with a unit test encoding the wrong reason — the offline suite was green throughout and could not have caught it. #776's happy path is verified by a real `gflow image t2i` (exit 0, 367 135-byte JPEG, `image_settings_applied` and `prompt_typed` both present, so **three of the four converted click sites** clicked successfully through the new helper); its **failure** path is real Chromium driving a page we wrote, which proves the mechanism and explicitly **not** that Flow still produces that state. **Three items recorded as NOT verified rather than omitted:** the `/about` redirect stopped reproducing (**0/5**, reported as *unmeasured* rather than argued into a retry flag), the `/fx/api/auth/*` landing moved before the run reached it, and #764's *success* path — an external contribution whose error boundary this release verifies but whose auto-selection needs an account currently behind a Google password challenge. The fourth converted click site is the **video** submit, unrun because it spends Veo credits, named rather than implied.) · previous: [LIVE_VERIFICATION_v0.72.0](LIVE_VERIFICATION_v0.72.0.md) (**auto-closing `gflow auth login`, verified 2026-09-09 on a migrated account at $0 across six runs.** Four paths: auto-close fires (`probe=in_context` at `elapsed_s` **84.8**, reproduced 3x), a manual close still verifies from disk (exit 0, never exit 12), `--browser auto` selects and completes, and a window closed **mid-2FA** is noticed in **2 s** (exit 8) where it previously ran the full 600 s deadline with the session endpoint touched **zero** times. **Two runs were discarded rather than counted**, and that is the useful part: the first returned exit 0 at `elapsed_s: 0.2` because a throwaway profile had survived the previous session and nobody signed in — a cached session reading as a clean pass — and three attempts at the manual-close path all returned exit 0 while being the *auto-close* path in disguise, separable only by an **absent** `probe=in_context`. The manual path was obtained by widening the poll interval for one run so the competing branch could not fire; the 2FA path by killing the profile's own Chrome, because hand-timing lost every race on a host that completes passkey sign-in in ~15 s. **Recorded as NOT verified rather than omitted:** the migrated-host image slice (#692) was **re-run this cycle** — CLI `t2i` PASSED first-hand on a moved account, while the queued-MCP `i2i` twin failed with a typed non-retryable exit 27 whose **cause is unknown** — some dialog opened after the file was chosen and no `maseQ` left the page, on an account that has ALREADY consented, so the message's "most likely the one-time upload-terms dialog" does not fit; no incident bundle was written, so nothing names the dialog, and it is filed for a spike rather than guessed; the subprocess fallback is unit-tested only; and the OAuth-callback *mechanism* behind the poll fix is **inferred, not proven** — a host-only gate does not exclude NextAuth's callback, since it runs on the app's own origin, yet all four sign-ins passed under it, so #769 carries the spike that would settle it.) · previous: [LIVE_VERIFICATION_v0.71.1](LIVE_VERIFICATION_v0.71.1.md) (**two migrated-host error paths stopped blaming the wrong thing, 2026-09-08, $0 across three profiles.** The agent-mode recovery landed earlier in this same release (#749) and worked, but its first cut collapsed three outcomes into one message — chip clicked / chip found but click blocked / chip clicked and mode still on — so a modal eating the click sent users to toggle a chip that was never the problem, and genuine selector drift *after* the mode was left was filed under an account setting the driver had already changed. Verified by an e2e that drives the account INTO agent mode and carries its own neutered-selector control; run **twice**, because review fixes landed after the first run and it no longer covered the code. **The larger find:** an account's FIRST upload on this host is blocked by Flow's one-time *"Rights to use this image"* dialog, which renders *after* the file chooser hands the file over — so `_dismiss_dialog` never sees it and the driver spent 60 s waiting for a request the page had already declined to make, then advised re-encoding the image. Six runs on `ci-probe` close the chain: guard fires while the dialog is up → owner-authorised accept → uploads (`media_id 8914400f`) → fresh session uploads clean with `dialog: None`. The order was forced, because the dialog is one-off and accepting it destroys the failing state — so the guard was written and verified BEFORE anything was clicked, and its firing branch is now unrepeatable here. `maseQ` is confirmed **not** renamed (six uploads, three profiles), killing #719's top hypothesis. Also: Flow's queue listing is on **`Zzl0ze`**, not the `jwpduf`/`as29s` progress polls, and two `abra_r2v_8s` records sat at status 6 for ~20 h unseen by any CLI command (#741). Three documents are corrected rather than patched — a KNOWN_ISSUES entry that told #719's reader this dialog did not affect gflow-cli, and a v0.71.0 host label calling `ci-probe` *labs* when it is migrated, which helped a credit-based theory survive four runs. Recorded as NOT verified: #719's second failure shape — an upload request that leaves the page and is never answered, ~1 run in 4 — which is unfixed and keeps #719 open.) · previous: [LIVE_VERIFICATION_v0.71.0](LIVE_VERIFICATION_v0.71.0.md) (**`gflow character create --voice` verified end to end for the first time, 2026-09-07 on profile `ffroliva`.** Before this release a repo-wide grep for `--voice` across `tests/e2e/` matched **nothing** — every voice test was a unit test of the hardcoded `VOICES` constant and the one that looked live parsed a fixture, so a voice that silently failed to attach was invisible to the whole suite while the command exited 0. A live create + `character show` read-back settles a contradiction between two of our own documents: `sent='Charon' stored='Charon' identical=True`, so the Capitalized canonical form round-trips and `CHARACTER_RECON.md`'s "preset id is the lowercased name" does not describe today's wire. Both docs also now record that `personalityNotes` is **Agent-scoped** per Flow's own editor copy, not a control on the audio engine. **A claim that was in the code is overturned:** the `_unported_form` entity guard said the submit "never produces a reply" and that the backend refuses — in fact `MZZa6b` replies with a null payload and the generation is **accepted and queued** (Flow types it `abra_r2v_8s` and renders it); the failure is the *observer*, which waits out `SUBMIT_REPLY_BUDGET_S` (60 s, calibrated on 4.0–4.6 s replies against an idle queue) and exits 9 while the video is still rendering. The guard stays until the observer is fixed, because a timeout reported on a healthy generation is worse than an explicit refusal. Also verified: credit shortfall reports exit **37** with `_raise_if_out_of_credits` called from **both** give-up paths — and it is *short for the selected model*, not empty (the measured account held **50** and asked for `veo-quality`, which costs **100**); the "+ New project" CTA anchored structurally on `add` (Tier-1 matches **1** where every previous entry matched **0**, control 47 ligature nodes) after this same release first asserted the control did not exist and a $0 run disproved it in one click; and the incident-bundle DOM dump de-blinded — it queried `i.google-symbols` only, so **every bundle a migrated user sent carried an empty ligature list**, which is why #727 and #731 stayed invisible. One item recorded as NOT verified rather than omitted: whether a bound character's **voice reaches rendered audio** (#738) — attachment is proven, application is not, because no entity-bound generation has yet returned a file to measure. The blocker is no longer credits or account access but retrieval, and the measurement is pre-calibrated: plate-bound takes of one character gave **88 / 103 / 118 Hz** against a **4.3 Hz** engine noise floor, so an applied Algenib should sit near its sample's **163.3 Hz**.) · previous: [LIVE_VERIFICATION_v0.70.0](LIVE_VERIFICATION_v0.70.0.md) (**reference-to-video on the migrated `flow.google.com` host, verified 2026-09-06 on profile `denon82`.** Three r2v runs bound their references every time; the decisive one is semantic rather than structural — two hand-drawn reference images went in and the clip came back carrying the same marker strokes, face and paper texture, which is what separates "Flow bound the reference" from "Flow accepted and ignored it". A four-beat, two-character piece was then produced end to end and joined with the concat filter: 19.000s, 1280x576, `clip_qa` **ok**, A/V **+0.000s**, both actors recognisable across every cut from one face plate plus the canon repeated verbatim. Also verified as exit-code corrections on the real CLI: `-o <existing directory>` now exits **2 in 0.8s** instead of exit 1 after ~2 min **and a billed, orphaned clip**; `character create` on a moved account exits **36 immediately** instead of a bare `RuntimeError` exit 1 after a 20s wait. Four items recorded as NOT verified rather than omitted: #692's original failure could not be reproduced [the reporter's own re-run was on a build without the fix, so it shows the failure is intermittent, not that the fix works]; Flow CHARACTER entities were never exercised because `character create` cannot run on any account available here; `image`/`scene`/`movie`/`extend` all exit 36 on the migrated host and no unmoved account exists here; and the sign-in-interstitial fidelity question from #699 has no bundle evidence either way.) · previous: [LIVE_VERIFICATION_v0.68.0](LIVE_VERIFICATION_v0.68.0.md) (`gflow update` self-upgrading a real `uv tool` and a real `pipx` install from their own running `gflow.exe` to the PyPI release, Windows 11, zero credits — see its own row below) · previous: [LIVE_VERIFICATION_v0.67.0](LIVE_VERIFICATION_v0.67.0.md) (the migrated `flow.google.com` driver — see its own row below) · previous: [LIVE_VERIFICATION_v0.64.0](LIVE_VERIFICATION_v0.64.0.md) (**#626 `--model omni-flash --end-frame` — first+last interpolation on Omni 1.1 Flash, verified 2026-09-02.** The guard this release removes was evidence-gated, so it was retired on evidence: a route-aborted submit capture on **two distinct Google accounts** (`ffroliva`, `denon82`) fired `video:batchAsyncGenerateVideoStartAndEndImage` with `startImage` AND `endImage` non-null at **zero credits**, ruling out a single-account artifact. The decisive layer is semantic, not structural: the paid 4s generation's **last frame IS the supplied end image** and its first frame is the start image — two visibly different subjects — which is the only check that distinguishes "Flow bound the end frame" from "Flow accepted and ignored it", and which layers 1–4 would pass either way. Render: 4.01s / 720×1280 / h264+aac / 2.4 MB, `MEDIA_GENERATION_STATUS_SUCCESSFUL`. The static capability table is **deleted**, not corrected — it went stale silently once and would again; a post-submit route check (`_assert_i2v_route`) now fails a run whose end frame Flow dropped back to the `StartImage` route, catching a rollback on any account without anyone re-reading a support page. One item is recorded as NOT verified rather than omitted: `--duration 10` + end frame is **submit-verified only** (`duration_set seconds=10` on the correct route with both images bound), because the status poll returned HTTP 401 mid-run and a retry 401'd at `project.create` before submitting — [#561](https://github.com/ffroliva/gflow-cli/issues/561), pre-existing, so verification was stopped rather than spending further credits on an environmental fault.) · previous: [LIVE_VERIFICATION_v0.63.0](LIVE_VERIFICATION_v0.63.0.md) (**`gflow video extend` — continuing a clip past Flow's 8s ceiling, verified 2026-09-01 on profile `ffroliva`, 20 Veo credits.** The decisive observation is that segment 2's `source_media_id` **is** segment 1's `media_id` (`0c9364f3…` seeded from `b9458021…`, then `648f9291…` seeded from `0c9364f3…`) — tail-only chaining, which no mock can establish; had it re-seeded from the source, the output would have been two divergent continuations of the same moment instead of one continuous shot. `extend_model_resolved` logged `candidate_count=99` against `SERVICE_TIER_INTERMEDIATE`, proving the key came from the live capability listing rather than a constant, and plan cost matched actual spend (`20 credits total, balance 875` → `Extended — 2/2 segment(s), 20 credits`). Render: 23.02s / 1280×720 / 24fps / h264+aac. **The run found a defect the offline suite is structurally incapable of seeing:** an extend segment carries **7.000000s** of content, not the 8 Flow advertises and bills, so server-side concat pads every internal seam with a frozen frame and digital silence (15s at −75.1 dB against −29 neighbours, reproduced on a second independent render) — filed in KNOWN_ISSUES with the three questions that must be answered before any clamp, and the reason `--extend N` on t2v/i2v was deliberately NOT shipped. Seven items are recorded as NOT verified rather than omitted: portrait `9:16`, `--aspect` against a mismatched source, chains longer than 2 segments, `--resume-from` against a live partial scene, the insufficient-credits refusal, a live Ctrl+C, and `OperationKind.EXTEND` rows.) · previous: [LIVE_VERIFICATION_v0.62.1](LIVE_VERIFICATION_v0.62.1.md) (**#604 `--model omni-flash` selects again after Flow's `Omni Flash` → `Omni 1.1 Flash` rename, verified 2026-08-30 on profile `ffroliva` at ZERO Veo credits.** The production `_select_video_model` was driven against the real picker: the shipped selector resolves verbatim — `model_selected model=omni_flash via="[role='menuitem']:has-text('Omni'):has-text('Flash'):not(:has-text('[Lower Priority]'))"` — and all six cases came back as expected: the four offered tiers SELECT, a tier Flow does not offer REFUSES, and a deliberately ambiguous selector REFUSES rather than resolving `.first`. Selection happens before submit, so the whole matrix is free. The transport's own refusal diagnostic read the live menu back as `Omni 1.1 Flash / Veo 3.1 - Lite / Fast / Quality`, independently corroborating the fixture. Four items are recorded as NOT verified rather than omitted: the rename *direction* [the `Omni Flash` baseline is a different account, locale and date], an actual `Omni ... [Lower Priority]` entry [Flow has never offered one], a full credit-spending generation on omni-flash, and #539's absence question, which stays open.) · previous: [LIVE_VERIFICATION_v0.62.0](LIVE_VERIFICATION_v0.62.0.md) (**#595 `auto` ≡ `classic` for images, verified 2026-08-28 on profile `ci-probe` — an account Flow had moved to the agentic cohort the day before — at ZERO Veo credits.** With no flags and no env vars the run logged `ui_driver.ui_mode.attempt_exit_agent` → `ui_driver.bound mode=classic ui_mode=classic` and generated a real 768x1376 JPEG (exit 0); the day before, the identical command on the same account bound `auto`→`agentic` and failed. The same log independently closed **#183**: `mode_switch_trigger` and `image_mode_tab`, the selectors it reported as unfindable, both matched. #591 was proven against the real 500-row catalog — **0** occurrences of the string `"None"`, 31 proper JSON `null`s, over a catalog holding 119 NULL-bearing rows. #592 shows exactly one `client.account_locale_cached` per command. Three items are recorded as NOT verified rather than omitted: the exit-28 abort on a *pinned* agentic account, the #597 batch inter-prompt guard, and any fresh announcement modal — the last two because all three accounts have already acked the current changelog, so no modal can be raised until Google ships the next one.) · previous: [LIVE_VERIFICATION_v0.61.0](LIVE_VERIFICATION_v0.61.0.md) (**#539 video-model refusal + #586 image-model refusal and server-side attribution, verified 2026-08-26/27 on profile `denon82`, ONE Veo generation total** — the video fix was proven by a **zero-credit A/B against the stashed pre-fix source running on live Flow**: the old code returned SELECTED for `veo-lite-lp`, a model Flow does not offer to this account, and for a deliberately ambiguous selector matching 3 entries; the new code refuses both with exit 18 naming what Flow offered. Model selection happens before submit, so refusals cost nothing and the A/B was free. The happy path still generates: `--model omni-flash` → exit 0, a real 2.2 MB `ftypisom` mp4, catalog recording `omni_flash`. Two items are recorded as NOT verified rather than omitted: three of #584's four navigation-settle sites were never exercised [no bearer refresh occurred in these runs], and #582's canary self-re-exec has its first real exercise tonight. Also falsified: #539's recorded note that the video picker uses a different trigger — the two constants are byte-identical strings, and the repeated empty menu captures were the capture's own fault.) · previous: [LIVE_VERIFICATION_v0.60.0](LIVE_VERIFICATION_v0.60.0.md)
+**What was actually live-verified for the latest release?** → latest: [LIVE_VERIFICATION_v0.84.0](LIVE_VERIFICATION_v0.84.0.md) (**2026-10-12, 0 credits.** #970: `gflow run --project` generates every row into an existing project — e2e passed on our account and the contributor's; #971: multi-prompt `t2i --project` — new e2e passed; no MCP twin for either) · previous: [LIVE_VERIFICATION_v0.83.2](LIVE_VERIFICATION_v0.83.2.md) (**2026-10-11, 0 credits.** #963: `--duration` binds in a Vietnamese pane — locale e2e failed on develop and passed after the fix, and a notice-only cookie bar is now acknowledged; #957: image upscale e2e passed on the CLI and over MCP; #962: `auth status` probe uses the profile's channel, unverified on a host without Chrome) · previous: [LIVE_VERIFICATION_v0.83.1](LIVE_VERIFICATION_v0.83.1.md) (**2026-10-08, 0 credits.** #958: the default image model `nano2` runs Nano Banana 2.1 on flow.google.com — e2e failed on develop and passed after the fix; CLI and MCP twins each wrote a JPEG; 2.1 measured as replacing 2 on two accounts) · previous: [LIVE_VERIFICATION_v0.83.0](LIVE_VERIFICATION_v0.83.0.md) (**2026-10-06/07.** #948: a billed flow.google.com video run no longer exits 7 — t2v, i2v and r2v e2e passed after the fix, reproduced before it; `data download` e2e 2 passed after a 302 regression was caught and fixed; #922: image and video upscale e2e passed, CLI and MCP image twins wrote the same JPEG, MCP video wrote 1920x1080, a 1080p export measured 0 credits) · previous: [LIVE_VERIFICATION_v0.82.1](LIVE_VERIFICATION_v0.82.1.md) (**2026-10-02.** A reCAPTCHA mint failure typed with a live-measured retry flag (#915, e2e 2 passed, $0); a busy catalog no longer fails a successful generation (#900, real SQLite, no Flow surface); a video's workflow id recorded (#898, 1 veo-lite clip)) · previous: [LIVE_VERIFICATION_v0.82.0](LIVE_VERIFICATION_v0.82.0.md) (**2026-10-01.** `"ref": "batch:N"` and local-file refs on `gflow run` verified by a BDD e2e on flow.google.com: in place, no re-upload, lineage recorded; 1 veo-lite clip for the #926 e2e) · previous: [LIVE_VERIFICATION_v0.81.0](LIVE_VERIFICATION_v0.81.0.md) (**2026-09-30, 3 veo-lite clips.** The off-screen generation browser (#923) measured unchanged for image and video, window placement read back from Chrome, focus-steal measured and documented; #919 verified at merge) · previous: [LIVE_VERIFICATION_v0.80.0](LIVE_VERIFICATION_v0.80.0.md) (**2026-09-29, 0 Veo credits.** `--resolution` 360p/720p proven by driving the real settings pane on `omni_flash` and refusing the credit-spending submit, on the CLI transport **and** the MCP twin; `nano2-lite` e2e 2 passed; #891 measured before/after — `gflow run` `[nano2, imagen4]` went from exit 1 `RecaptchaError` with a lost results table to exit 36 naming the model, plus 3 e2e (fresh, warm, MCP) with a spy asserting zero client mints; #896 `e2e_data` 2 passed, its failure path offline-only. Named blockers: rendered resolution (needs a billed clip), the `/about` re-check arm, labs-served accounts.) · previous: [LIVE_VERIFICATION_v0.79.1](LIVE_VERIFICATION_v0.79.1.md) (**the signed-media download survives a dropped connection, verified 2026-09-22 at $0.** All three download sites route through one new shared helper, and that helper was driven through a real Flow clip route and a real signed CDN transfer by `pytest -m e2e_data` — 2 passed in 20.74 s, `ftyp` magic, byte length equal to the size Flow reports, and **no `url=` on any log event**. The retry itself could not wait for an organic reset — 20/20 clean here against the reporter's 2-in-6 — so it was **measured against a real TCP RST with an A/B control**: with `max_retries` the transfer recovers on a second connection, with it disabled the identical fault kills the call, and three attempts at a 5 s timeout finish in 1.57 s rather than ~15 s, proving the backoff shares one budget. **Two sites are NOT live-verified and name their blockers:** the composer call site needs a billed generation and `gflow credits` answers 401 on this account (#795), so no credits were spent; and the labs download cannot be reached at all from here (HTTP 308, 6/6 profiles). Offline: 21 new tests, full sweep 2143 passed.) · earlier: [LIVE_VERIFICATION_v0.79.0](LIVE_VERIFICATION_v0.79.0.md) (**the migrated host stops echoing a model it never observed, verified 2026-09-18 at $0.** `model_name_type` is `null` on `flow.google.com` in a real `image t2i --json`, with every sibling field populated — which is what makes the null a result rather than an empty envelope; the first read of it was flat rather than into `images[]` and returned `None` for everything, and that instrument error was discarded rather than reported. Both surfaces ran: `test_e2e_t2i_runs_on_a_moved_account` and `test_e2e_mcp_i2i_runs_on_the_migrated_host`, 2 passed in 86 s. **`gflow data download` was tested on an image and failed** — 45 s, then a message blaming the project, the trash and your prompt; recovery is video-only and the release notes now say so (#877). **#803 is NOT live-verified and names its blocker:** reaching those raise sites needs a non-JSON or token-less aisandbox reply, and the labs route refuses first with a 404 — itself a misleading error, filed as #875. Offline: 4 new unit tests, 1775 passed.) · previous: [LIVE_VERIFICATION_v0.78.0](LIVE_VERIFICATION_v0.78.0.md) (**generating with no project on `flow.google.com` — and video from a start frame — verified 2026-09-17.** The release exists because labs.google's `project.createProject` is retired — 404 *"Flow RPCs have been deprecated and disabled"* with a labs token, 401 without, 0 successes in 12 across four profiles — and gflow reported the 401 as an expired login. Creation and rename are driven on flow.google.com and read back from Flow's own `jHPbke` / `o8DA4` replies; the CLI and the MCP twin are each exercised separately, and both video paths reach a real submit that is aborted before Flow can bill it. Two failures are recorded and re-tested rather than explained away — one MCP image reply that did not reproduce under a four-run A/B, and a Chrome launch starved by a concurrent coverage run that passed in 36 s alone. The 3:4 image aspect is re-measured on the live radiogroup, five radios where 2026-09-08 saw four. Three items are NOT verified and each names its blocker: no labs-served account, no entitled `/about` account, no non-`en` locale. **#860 is the one thing here that cost credits, deliberately:** the only proof that a start frame binds is a real generation, so ten i2v clips were generated and downloaded on a live migrated account — `migrated.frame_uploaded` → `frame_bound` → `submit_observed` → `download`, the middle event being the one that could not fire before this release. **#859 is recorded as UNOBSERVED, not verified** — its dismissal ran on every one of those runs and no promo modal ever appeared, so the $0 route-intercepted e2e is what covers it. `gflow docs` (#861) is verified from the built wheel, which is its whole contract: 127 topics, `docs/FILE.md:LINE` search hits, no network and no checkout.) · previous: [LIVE_VERIFICATION_v0.77.1](LIVE_VERIFICATION_v0.77.1.md) (**a four-fix patch release, verified 2026-09-17 at ZERO cost.** The headline is #846: the published package could not run a single interactive command on a clean Windows install, because `ConsoleRenderer(colors=True)` needs `colorama` and nothing declared it. Verified as a controlled A/B on a fresh Python 3.13 venv — `SystemError` before, exit 33 after — plus an arm with stderr piped that shows why the AUTO/JSON split hid this from every CI job, and the MCP twin run separately. #848's import probe is exercised against a **deliberately broken venv** and an intact one, including the contract that a probe which cannot run reports nothing rather than reporting breakage. #852 is re-measured on the release head: 40 000 base64-shaped chars fall from 12.07 s to 0.020 ms with identical output on Workspace and custom domains. **#849 is a NAMED BLOCKER, not an omission** — its end-to-end behaviour needs a fresh interactive Google sign-in, which no agent can perform; its live A/B is recorded on PR #851 and its e2e file re-ran 4/4 here. **Seven live e2e failures are recorded rather than hidden**, and controlled: the release changes exactly four source files and none of them is a failing test's module.) · previous: [LIVE_VERIFICATION_v0.77.0](LIVE_VERIFICATION_v0.77.0.md) (**the migrated-host login lockout (#791), verified as a controlled A/B on a real Google **Workspace** account at ZERO cost — same profile, same cookies untouched between arms, so the only variable is the code: exit 8 with the Chrome marker rolled back and `channel_for_profile` collapsed to `None`, then exit 0 with the marker intact and the account recorded. The refusal path is measured too — of 10 local profiles, 5 reproduce #791 and exactly one carries both required cookies: 4 refusals, 1 upgrade, 0 false positives. v0.76.0 recorded this fix as **withdrawn**; the approach that shipped is a different one, server-attested on the landing URL rather than on client-rendered DOM. An earlier revision gated auth on an `@gmail.com`-only pattern that silently declined every custom domain — the account used here is one, which is why this is its verification. **#796 is reproduced and prevented**, not merely reported: it was filed as *'not yet reproduced end-to-end'*. **Two rows are named blockers, not omissions:** the MCP Registry publish (#841) cannot be rehearsed before a real tag push, so this release is its first exercise; and the migrated-host generation e2e cannot run here at all — every account bounces to `/about`, A/B-controlled against `develop` so it is not mistaken for a regression.) · previous: [LIVE_VERIFICATION_v0.76.0](LIVE_VERIFICATION_v0.76.0.md) (**a diagnostics-and-distribution release, verified 2026-09-16 at ZERO cost — no Veo credits, no image generation, no Flow submit.** The decisive arm is #833's **negative** control, run first-hand on two real accounts rather than relayed: `flow-pinhole-unavailable-screen` is **0** on both `ffroliva` and `denon82` while `aisandbox-root` is **1**, so the guard does not fire on accounts that HAVE Flow access and the zero is a real absence rather than a page that never booted — a guard with only a positive arm is indistinguishable from one that is permanently on. Both accounts settled at **`/about`**, which is the state that broke this release's *withdrawn* #791 oracle, and the exit-39 signal reads a component that only exists on the unavailable screen, so `/about` cannot mimic it. mcpservers.org is verified with a **404 negative control** because the listing 403s to `curl` and a naive check would have called the link dead. **#791 is NOT in this release and was withdrawn rather than deferred**: a fix passed eight council dimensions and was then refuted by a five-day-old spike nobody had routed to it — Flow's `/about` hop is decided client-side with zero requests to Flow, and *"the backend grants access while the frontend declines to open it"* (#756), so the probe would have reported authenticated users as logged out, reintroducing #791 as its own cure; the e2e caught it by going red on a live account whose state moved mid-session. **Two rows are blocked by the platform rather than by effort:** the Docker sign-in needs a WSL-integrated Docker host, and the MCP Registry publish cannot be observed until this very tag reaches `main`, since both triggers resolve the workflow from the default branch.) · previous: [LIVE_VERIFICATION_v0.75.0](LIVE_VERIFICATION_v0.75.0.md) (**a distribution-and-hardening release, verified 2026-09-15 on `ffroliva` at ZERO cost — no Veo credits, no image generation, no Flow submit.** The `gflow serve` token fix is an **A/B against the released 0.74.0 wheel from PyPI**, not a diff read: the token was *set* in both arms, so the probe measures whether it is checked — before, `no token 200/200` with 13 tools listed and `wrong 200/200`; after, `401/401` with zero tools and `WWW-Authenticate: Bearer realm="gflow"`, while the correct token still gets 200. Loopback DNS-rebinding was re-confirmed at **421**/**403** because the fix forwards the bind host and getting that wrong would silently disable protection that works today — and an earlier draft of the accompanying advisory claimed that protection was *disabled*, a false claim caught by measuring rather than re-reading. #813's guard is verified against a **real wheel in a real venv installed without extras**, the arm first proving it is in that state (`av present: False  PIL present: False`); the decisive row is that a **nonexistent** manifest still exits **20** on the dependency error rather than file-not-found, which is what shows the guard precedes the manifest read and not merely the generation. The Rich escape fix is verified on the **console render separated from the structlog JSON** — matching the JSON line would have been a false pass, since `--json` was never affected — with a **neutered control** through the same Rich version reproducing the bug exactly: `UNESCAPED -> pip install 'gflow-cli'` against `ESCAPED -> pip install 'gflow-cli[chain]'`. Also: `gflow-cli.exe` exists in the built wheel so `uvx gflow-cli` resolves at all, and the wheel carries 138 entries with **zero** ZIP duplicates. **Three items recorded as NOT verified rather than omitted:** a successful multi-link `chain` run spends Veo credits and stays outstanding e2e debt on #813 — what changed is the refusal path, which *is* verified; `gflow credits` against a working balance is impossible here because the account still returns 401, pre-existing **#795** and unrelated to this release; and the SSE arm of the token fix was exercised on loopback only, a deliberate scope limit, since binding a LAN address to test it would put an authenticated daemon on a live network for the run. **Two rows are blocked by the platform rather than by effort:** the PyPI metadata and the MCP Registry listing are both unobservable until this release is uploaded — PyPI renders the last artefact's metadata, and `mcp-publisher` reads its ownership token out of the *published* README.) · previous: [LIVE_VERIFICATION_v0.74.0](LIVE_VERIFICATION_v0.74.0.md) (**the migrated driver's run-unique uploads and its Frames-picker confirm, plus the `credits` remediation, verified 2026-09-14 on `ffroliva` at ZERO cost — every arm is a read or an upload-and-stop.** The confirm branch is the interesting one: this cohort's picker closes on its own, so the branch would never execute against live Flow by accident, and the e2e drives `FRAME_COMMIT_GRACE_S` to **0.001** so the grace expires before Flow can auto-close and **every** run enters it — the difference between a named blocker and an unrun claim. A *genuinely stuck* picker still cannot be produced here and stays `Refs #792`, verifier the reporter. #795 was verified on the cohort it is for, because this account is now in it — `auth status` green, `credits user` exit **3** with `detail` `credits endpoint returned 401` and `route: credits`, where v0.73.2 printed the class-default *"SAPISID cookie missing… re-run `gflow auth login`"*, advice that is wrong in every word there and that can roll a profile's strategy marker back and start the #791 spiral; the `credits list --json` envelope carries the per-profile `remediation_hint` that used to be dropped. **Two items recorded as NOT verified rather than omitted:** #799's exit-25 raise site needs an account in the agent-only cohort — the maintainer's accounts are served `flow.google.com` but still have the recoverable agent chip, so the state is structurally unreachable on them, a named blocker and #799 stays open; and neither `r2v` nor `i2i` had its own attach path driven to completion — `r2v` was not attempted (its e2e spends Veo credits), while `i2i` **was** attempted twice and failed both times at exit 23, before reaching the code under test, because the `--project` UUID came from `gflow project list` (the aisandbox catalog) and those ids 404 on `flow.google.com` — a harness error, recorded rather than dropped, which left a side finding: gflow reports Flow's own `/404?reason=project` as `UiSelectorDriftError`, blaming our selectors for Flow's 404. **#791 is not fixed and was not attempted blind** — all nine local profiles were probed at $0 and none is in the #791 state (SAPISID + a live `flow.google.com` session + no labs NextAuth token); four print its exact symptom string and none of them is it, because that string is also what a stale profile says.) · previous: [LIVE_VERIFICATION_v0.73.2](LIVE_VERIFICATION_v0.73.2.md) (**the blank incident bundle, reproduced and then cured by a committed e2e test, 2026-09-12 on `ffroliva` at ZERO cost — every arm fails before submit.** The decisive layer is an **A/B run through the same instrument**, not an inspection: on `develop` the new test FAILS in 46.3 s and prints the bundle it got — `tag_counts.div = 0`, `title.length = 0`, `host_category = "other"`, a 4,254-byte screenshot — which is field-for-field the signature [#792](https://github.com/ffroliva/gflow-cli/issues/792) reported from a different account, a different OS and a different command; on the fix it PASSES in 37.8 s with `div` **25**, `title.length` **81**, `host_category` **`flow_app`**, `route` `/404` and a 38.4 KB screenshot. Both arms exit **23** on the same `.settings-trigger-button` drift at `flow.google.com/404?reason=project`, so the arms differ only in what was *captured*, never in what failed. **The reporter's own bundle contained the refutation of their diagnosis**: viewport 1280x720 is `client.py`'s client-owned page, not the 1920x1080 a stray transport tab would have — it was always the driven page, photographed one navigation too late, and the portrait correlation had no mechanism behind it. The existing quality benchmark could not have caught this: it captures deliberately on a **healthy** page, so it graded only bundles that were never at risk. **Recorded as NOT verified rather than omitted:** #796's `PROFILE_MARKER_MISSING` is offline-only because its live trigger is a cookie-store **decryption** failure, which does not occur on Windows/DPAPI — it is the macOS Keychain path of [#768](https://github.com/ffroliva/gflow-cli/issues/768), a **named external blocker**, and the issue stays open; a synthetic attempt to force it failed informatively, since a corrupt store raises `sqlite3.DatabaseError`, bypasses the marker gate and still prints "check network connectivity" — the same misdirection from a different trigger, untouched here. #795's remediation string is unit-asserted only, and the *other* half of #795 — `credits` being labs-only on migrated accounts — is **not fixed**.) · previous: [LIVE_VERIFICATION_v0.73.1](LIVE_VERIFICATION_v0.73.1.md) (**Google's `glue` consent bar covering the migrated composer, measured and then cured, 2026-09-11 on `ci-probe` for one image generation and no Veo credits.** The premise was nearly rejected: both prior sightings of that selector in this repo are labs.google, and the 2026-09-10 spike had read 159 DOM samples on this exact host and project and watched the click land 3/3 — it simply never looked for a cookie bar. Seventeen hours later the bar was up: `position: fixed`, `z-index: 1000`, spanning y 547-655 of a 655 px viewport, with `elementFromPoint` over the settings trigger AND over the image submit both returning `span#glue-cookie-notification-bar-1-label` in **0 of 5** rendered samples hit-testable. **The control arm is what makes it a cure rather than a coincidence**: the same probe re-run through the driver's own `_dismiss_cookie_bar` restored both controls to **4/4**, one attempt, no error. A full `gflow image t2i` then ran end to end on the merged code — `status: ok`, a 807,761-byte `ffd8ffe0` JPEG that Pillow reads as 1376x768 RGB, matching the requested 16:9 and the reply's own dimensions, with `migrated.editor_ready` at 2.0 s and **no** `cookie_bar_not_dismissed`. A side finding the control arm produced by accident: the bar's buttons are `__accept` then `__reject` in DOM order, so anything taking "the first button" accepts cookies for the operator — the shipped fix anchors on reject. **Three items recorded as NOT verified rather than omitted:** the cure against a live bar outside the browser, because this release's own control arm consumed the consent on the only profile that had it; **prevalence**, because the second profile never reached an editor (both arms redirected to `/about`) so it is one account blocked and one already-consented, and KNOWN_ISSUES says so rather than generalising from n=1; and the video path live, which shares the identical function on the identical control but spends Veo credits.) · previous: [LIVE_VERIFICATION_v0.73.0](LIVE_VERIFICATION_v0.73.0.md) (**four error paths that stopped lying about what went wrong, verified 2026-09-10 on `ci-probe` and `denon82` at $0 — no run below reaches a Veo submit.** The decisive arm is an **A/B**, not an inspection: the pre-fix run printed an `accounts.google.com` challenge URL together with the OAuth `state` and `client_id`, and the identical command after the fix gave the same exit 38 and the same landing named with **five secret matches down to zero** — reading the post-fix output alone would only have shown that *these* secrets were absent. A second arm **falsified a claim already written into PR #775's body**: it said the change fixed the RED canary, and the live run showed `denon82` had moved to `accounts.google.com` mid-run, a landing the classifier excluded **by design**, with a unit test encoding the wrong reason — the offline suite was green throughout and could not have caught it. #776's happy path is verified by a real `gflow image t2i` (exit 0, 367 135-byte JPEG, `image_settings_applied` and `prompt_typed` both present, so **three of the four converted click sites** clicked successfully through the new helper); its **failure** path is real Chromium driving a page we wrote, which proves the mechanism and explicitly **not** that Flow still produces that state. **Three items recorded as NOT verified rather than omitted:** the `/about` redirect stopped reproducing (**0/5**, reported as *unmeasured* rather than argued into a retry flag), the `/fx/api/auth/*` landing moved before the run reached it, and #764's *success* path — an external contribution whose error boundary this release verifies but whose auto-selection needs an account currently behind a Google password challenge. The fourth converted click site is the **video** submit, unrun because it spends Veo credits, named rather than implied.) · previous: [LIVE_VERIFICATION_v0.72.0](LIVE_VERIFICATION_v0.72.0.md) (**auto-closing `gflow auth login`, verified 2026-09-09 on a migrated account at $0 across six runs.** Four paths: auto-close fires (`probe=in_context` at `elapsed_s` **84.8**, reproduced 3x), a manual close still verifies from disk (exit 0, never exit 12), `--browser auto` selects and completes, and a window closed **mid-2FA** is noticed in **2 s** (exit 8) where it previously ran the full 600 s deadline with the session endpoint touched **zero** times. **Two runs were discarded rather than counted**, and that is the useful part: the first returned exit 0 at `elapsed_s: 0.2` because a throwaway profile had survived the previous session and nobody signed in — a cached session reading as a clean pass — and three attempts at the manual-close path all returned exit 0 while being the *auto-close* path in disguise, separable only by an **absent** `probe=in_context`. The manual path was obtained by widening the poll interval for one run so the competing branch could not fire; the 2FA path by killing the profile's own Chrome, because hand-timing lost every race on a host that completes passkey sign-in in ~15 s. **Recorded as NOT verified rather than omitted:** the migrated-host image slice (#692) was **re-run this cycle** — CLI `t2i` PASSED first-hand on a moved account, while the queued-MCP `i2i` twin failed with a typed non-retryable exit 27 whose **cause is unknown** — some dialog opened after the file was chosen and no `maseQ` left the page, on an account that has ALREADY consented, so the message's "most likely the one-time upload-terms dialog" does not fit; no incident bundle was written, so nothing names the dialog, and it is filed for a spike rather than guessed; the subprocess fallback is unit-tested only; and the OAuth-callback *mechanism* behind the poll fix is **inferred, not proven** — a host-only gate does not exclude NextAuth's callback, since it runs on the app's own origin, yet all four sign-ins passed under it, so #769 carries the spike that would settle it.) · previous: [LIVE_VERIFICATION_v0.71.1](LIVE_VERIFICATION_v0.71.1.md) (**two migrated-host error paths stopped blaming the wrong thing, 2026-09-08, $0 across three profiles.** The agent-mode recovery landed earlier in this same release (#749) and worked, but its first cut collapsed three outcomes into one message — chip clicked / chip found but click blocked / chip clicked and mode still on — so a modal eating the click sent users to toggle a chip that was never the problem, and genuine selector drift *after* the mode was left was filed under an account setting the driver had already changed. Verified by an e2e that drives the account INTO agent mode and carries its own neutered-selector control; run **twice**, because review fixes landed after the first run and it no longer covered the code. **The larger find:** an account's FIRST upload on this host is blocked by Flow's one-time *"Rights to use this image"* dialog, which renders *after* the file chooser hands the file over — so `_dismiss_dialog` never sees it and the driver spent 60 s waiting for a request the page had already declined to make, then advised re-encoding the image. Six runs on `ci-probe` close the chain: guard fires while the dialog is up → owner-authorised accept → uploads (`media_id 8914400f`) → fresh session uploads clean with `dialog: None`. The order was forced, because the dialog is one-off and accepting it destroys the failing state — so the guard was written and verified BEFORE anything was clicked, and its firing branch is now unrepeatable here. `maseQ` is confirmed **not** renamed (six uploads, three profiles), killing #719's top hypothesis. Also: Flow's queue listing is on **`Zzl0ze`**, not the `jwpduf`/`as29s` progress polls, and two `abra_r2v_8s` records sat at status 6 for ~20 h unseen by any CLI command (#741). Three documents are corrected rather than patched — a KNOWN_ISSUES entry that told #719's reader this dialog did not affect gflow-cli, and a v0.71.0 host label calling `ci-probe` *labs* when it is migrated, which helped a credit-based theory survive four runs. Recorded as NOT verified: #719's second failure shape — an upload request that leaves the page and is never answered, ~1 run in 4 — which is unfixed and keeps #719 open.) · previous: [LIVE_VERIFICATION_v0.71.0](LIVE_VERIFICATION_v0.71.0.md) (**`gflow character create --voice` verified end to end for the first time, 2026-09-07 on profile `ffroliva`.** Before this release a repo-wide grep for `--voice` across `tests/e2e/` matched **nothing** — every voice test was a unit test of the hardcoded `VOICES` constant and the one that looked live parsed a fixture, so a voice that silently failed to attach was invisible to the whole suite while the command exited 0. A live create + `character show` read-back settles a contradiction between two of our own documents: `sent='Charon' stored='Charon' identical=True`, so the Capitalized canonical form round-trips and `CHARACTER_RECON.md`'s "preset id is the lowercased name" does not describe today's wire. Both docs also now record that `personalityNotes` is **Agent-scoped** per Flow's own editor copy, not a control on the audio engine. **A claim that was in the code is overturned:** the `_unported_form` entity guard said the submit "never produces a reply" and that the backend refuses — in fact `MZZa6b` replies with a null payload and the generation is **accepted and queued** (Flow types it `abra_r2v_8s` and renders it); the failure is the *observer*, which waits out `SUBMIT_REPLY_BUDGET_S` (60 s, calibrated on 4.0–4.6 s replies against an idle queue) and exits 9 while the video is still rendering. The guard stays until the observer is fixed, because a timeout reported on a healthy generation is worse than an explicit refusal. Also verified: credit shortfall reports exit **37** with `_raise_if_out_of_credits` called from **both** give-up paths — and it is *short for the selected model*, not empty (the measured account held **50** and asked for `veo-quality`, which costs **100**); the "+ New project" CTA anchored structurally on `add` (Tier-1 matches **1** where every previous entry matched **0**, control 47 ligature nodes) after this same release first asserted the control did not exist and a $0 run disproved it in one click; and the incident-bundle DOM dump de-blinded — it queried `i.google-symbols` only, so **every bundle a migrated user sent carried an empty ligature list**, which is why #727 and #731 stayed invisible. One item recorded as NOT verified rather than omitted: whether a bound character's **voice reaches rendered audio** (#738) — attachment is proven, application is not, because no entity-bound generation has yet returned a file to measure. The blocker is no longer credits or account access but retrieval, and the measurement is pre-calibrated: plate-bound takes of one character gave **88 / 103 / 118 Hz** against a **4.3 Hz** engine noise floor, so an applied Algenib should sit near its sample's **163.3 Hz**.) · previous: [LIVE_VERIFICATION_v0.70.0](LIVE_VERIFICATION_v0.70.0.md) (**reference-to-video on the migrated `flow.google.com` host, verified 2026-09-06 on profile `denon82`.** Three r2v runs bound their references every time; the decisive one is semantic rather than structural — two hand-drawn reference images went in and the clip came back carrying the same marker strokes, face and paper texture, which is what separates "Flow bound the reference" from "Flow accepted and ignored it". A four-beat, two-character piece was then produced end to end and joined with the concat filter: 19.000s, 1280x576, `clip_qa` **ok**, A/V **+0.000s**, both actors recognisable across every cut from one face plate plus the canon repeated verbatim. Also verified as exit-code corrections on the real CLI: `-o <existing directory>` now exits **2 in 0.8s** instead of exit 1 after ~2 min **and a billed, orphaned clip**; `character create` on a moved account exits **36 immediately** instead of a bare `RuntimeError` exit 1 after a 20s wait. Four items recorded as NOT verified rather than omitted: #692's original failure could not be reproduced [the reporter's own re-run was on a build without the fix, so it shows the failure is intermittent, not that the fix works]; Flow CHARACTER entities were never exercised because `character create` cannot run on any account available here; `image`/`scene`/`movie`/`extend` all exit 36 on the migrated host and no unmoved account exists here; and the sign-in-interstitial fidelity question from #699 has no bundle evidence either way.) · previous: [LIVE_VERIFICATION_v0.68.0](LIVE_VERIFICATION_v0.68.0.md) (`gflow update` self-upgrading a real `uv tool` and a real `pipx` install from their own running `gflow.exe` to the PyPI release, Windows 11, zero credits — see its own row below) · previous: [LIVE_VERIFICATION_v0.67.0](LIVE_VERIFICATION_v0.67.0.md) (the migrated `flow.google.com` driver — see its own row below) · previous: [LIVE_VERIFICATION_v0.64.0](LIVE_VERIFICATION_v0.64.0.md) (**#626 `--model omni-flash --end-frame` — first+last interpolation on Omni 1.1 Flash, verified 2026-09-02.** The guard this release removes was evidence-gated, so it was retired on evidence: a route-aborted submit capture on **two distinct Google accounts** (`ffroliva`, `denon82`) fired `video:batchAsyncGenerateVideoStartAndEndImage` with `startImage` AND `endImage` non-null at **zero credits**, ruling out a single-account artifact. The decisive layer is semantic, not structural: the paid 4s generation's **last frame IS the supplied end image** and its first frame is the start image — two visibly different subjects — which is the only check that distinguishes "Flow bound the end frame" from "Flow accepted and ignored it", and which layers 1–4 would pass either way. Render: 4.01s / 720×1280 / h264+aac / 2.4 MB, `MEDIA_GENERATION_STATUS_SUCCESSFUL`. The static capability table is **deleted**, not corrected — it went stale silently once and would again; a post-submit route check (`_assert_i2v_route`) now fails a run whose end frame Flow dropped back to the `StartImage` route, catching a rollback on any account without anyone re-reading a support page. One item is recorded as NOT verified rather than omitted: `--duration 10` + end frame is **submit-verified only** (`duration_set seconds=10` on the correct route with both images bound), because the status poll returned HTTP 401 mid-run and a retry 401'd at `project.create` before submitting — [#561](https://github.com/ffroliva/gflow-cli/issues/561), pre-existing, so verification was stopped rather than spending further credits on an environmental fault.) · previous: [LIVE_VERIFICATION_v0.63.0](LIVE_VERIFICATION_v0.63.0.md) (**`gflow video extend` — continuing a clip past Flow's 8s ceiling, verified 2026-09-01 on profile `ffroliva`, 20 Veo credits.** The decisive observation is that segment 2's `source_media_id` **is** segment 1's `media_id` (`0c9364f3…` seeded from `b9458021…`, then `648f9291…` seeded from `0c9364f3…`) — tail-only chaining, which no mock can establish; had it re-seeded from the source, the output would have been two divergent continuations of the same moment instead of one continuous shot. `extend_model_resolved` logged `candidate_count=99` against `SERVICE_TIER_INTERMEDIATE`, proving the key came from the live capability listing rather than a constant, and plan cost matched actual spend (`20 credits total, balance 875` → `Extended — 2/2 segment(s), 20 credits`). Render: 23.02s / 1280×720 / 24fps / h264+aac. **The run found a defect the offline suite is structurally incapable of seeing:** an extend segment carries **7.000000s** of content, not the 8 Flow advertises and bills, so server-side concat pads every internal seam with a frozen frame and digital silence (15s at −75.1 dB against −29 neighbours, reproduced on a second independent render) — filed in KNOWN_ISSUES with the three questions that must be answered before any clamp, and the reason `--extend N` on t2v/i2v was deliberately NOT shipped. Seven items are recorded as NOT verified rather than omitted: portrait `9:16`, `--aspect` against a mismatched source, chains longer than 2 segments, `--resume-from` against a live partial scene, the insufficient-credits refusal, a live Ctrl+C, and `OperationKind.EXTEND` rows.) · previous: [LIVE_VERIFICATION_v0.62.1](LIVE_VERIFICATION_v0.62.1.md) (**#604 `--model omni-flash` selects again after Flow's `Omni Flash` → `Omni 1.1 Flash` rename, verified 2026-08-30 on profile `ffroliva` at ZERO Veo credits.** The production `_select_video_model` was driven against the real picker: the shipped selector resolves verbatim — `model_selected model=omni_flash via="[role='menuitem']:has-text('Omni'):has-text('Flash'):not(:has-text('[Lower Priority]'))"` — and all six cases came back as expected: the four offered tiers SELECT, a tier Flow does not offer REFUSES, and a deliberately ambiguous selector REFUSES rather than resolving `.first`. Selection happens before submit, so the whole matrix is free. The transport's own refusal diagnostic read the live menu back as `Omni 1.1 Flash / Veo 3.1 - Lite / Fast / Quality`, independently corroborating the fixture. Four items are recorded as NOT verified rather than omitted: the rename *direction* [the `Omni Flash` baseline is a different account, locale and date], an actual `Omni ... [Lower Priority]` entry [Flow has never offered one], a full credit-spending generation on omni-flash, and #539's absence question, which stays open.) · previous: [LIVE_VERIFICATION_v0.62.0](LIVE_VERIFICATION_v0.62.0.md) (**#595 `auto` ≡ `classic` for images, verified 2026-08-28 on profile `ci-probe` — an account Flow had moved to the agentic cohort the day before — at ZERO Veo credits.** With no flags and no env vars the run logged `ui_driver.ui_mode.attempt_exit_agent` → `ui_driver.bound mode=classic ui_mode=classic` and generated a real 768x1376 JPEG (exit 0); the day before, the identical command on the same account bound `auto`→`agentic` and failed. The same log independently closed **#183**: `mode_switch_trigger` and `image_mode_tab`, the selectors it reported as unfindable, both matched. #591 was proven against the real 500-row catalog — **0** occurrences of the string `"None"`, 31 proper JSON `null`s, over a catalog holding 119 NULL-bearing rows. #592 shows exactly one `client.account_locale_cached` per command. Three items are recorded as NOT verified rather than omitted: the exit-28 abort on a *pinned* agentic account, the #597 batch inter-prompt guard, and any fresh announcement modal — the last two because all three accounts have already acked the current changelog, so no modal can be raised until Google ships the next one.) · previous: [LIVE_VERIFICATION_v0.61.0](LIVE_VERIFICATION_v0.61.0.md) (**#539 video-model refusal + #586 image-model refusal and server-side attribution, verified 2026-08-26/27 on profile `denon82`, ONE Veo generation total** — the video fix was proven by a **zero-credit A/B against the stashed pre-fix source running on live Flow**: the old code returned SELECTED for `veo-lite-lp`, a model Flow does not offer to this account, and for a deliberately ambiguous selector matching 3 entries; the new code refuses both with exit 18 naming what Flow offered. Model selection happens before submit, so refusals cost nothing and the A/B was free. The happy path still generates: `--model omni-flash` → exit 0, a real 2.2 MB `ftypisom` mp4, catalog recording `omni_flash`. Two items are recorded as NOT verified rather than omitted: three of #584's four navigation-settle sites were never exercised [no bearer refresh occurred in these runs], and #582's canary self-re-exec has its first real exercise tonight. Also falsified: #539's recorded note that the video picker uses a different trigger — the two constants are byte-identical strings, and the repeated empty menu captures were the capture's own fault.) · previous: [LIVE_VERIFICATION_v0.60.0](LIVE_VERIFICATION_v0.60.0.md)
 **"Was the playwright upper bound raised, and on what evidence?"** → [LIVE_VERIFICATION_playwright_1.61](LIVE_VERIFICATION_playwright_1.61.md) (**`>=1.59.0,<1.60.0` → `>=1.61.0,<1.62.0` verified 2026-08-05, 1 Imagen + 1 Veo credit** — the 2026-08-03 regression that motivated the bound does NOT reproduce on 1.61.0: a live `i2v` drove the full chain with `image_uploaded status=200` → `frame_attached` → `generate_captured status=200` with `startImage` parsed, where **1.62.0 hung silently at exactly that upload step**; live `i2i` local-ref attach passed outright [96.7s]. **1.62.0 stays excluded** — never root-caused. Also found, A/B-proven pre-existing on BOTH 1.59.0 and 1.61.0: Flow dropped the duration-tab UI, so **`--duration` is currently broken for i2v** — `UiSelectorDriftError` fires correctly [refusing rather than silently accepting Flow's default, #288] but the selector needs re-deriving; that is why the i2v proof was driven via the CLI without `--duration`, and Flow's own server-side `PUBLIC_ERROR_VIDEO_GENERATION_TIMED_OUT` means no finished mp4 is claimed).
 **"Where is the reverse-engineered wire protocol for a feature?"** → the `*_RECON.md` design docs: [CHARACTER_RECON](CHARACTER_RECON.md) (Flow character entity protocol), [IMAGE_UPSCALE_RECON](IMAGE_UPSCALE_RECON.md) (`/v1/flow/upsampleImage` wire). Naming convention: one `<FEATURE>_RECON.md` per reverse-engineered surface, kept as the durable spec after the feature ships. Pre-capture research recons: [ASSET_TAGGING_RECON](ASSET_TAGGING_RECON.md) (`@`-mention asset tagging — shipped in v0.40.0, see [LIVE_VERIFICATION_v0.40.0](LIVE_VERIFICATION_v0.40.0.md)).
 **"What was live-verified for v0.66.1?"** → [LIVE_VERIFICATION_v0.66.1](LIVE_VERIFICATION_v0.66.1.md) — **the two migrated-origin fixes, verified 2026-09-03 on profile `ffroliva` at ZERO credits, on BOTH sides of what was then read as a flapping rollout** (superseded 2026-09-04: the handoff is a one-way per-account flag and exit 36 is non-retryable since). On a real `flow.google.com` load `get_ui_driver` raised `FlowHostMigratedError` in **0 ms** (was ~36 s: ~8 s detect window + ~24 s crop cascade + 4 s URL settle), exit 36, `retryable: true` (then; `false` since 2026-09-04), `ui_driver.migrated_host_bail` logged; `await_url_settled` returned `null` in **0 ms** (measured 4018 ms before); and the locale was recovered as `en` from `html lang=en-GB` where the URL gave `null`. The no-regression half is the stronger evidence: minutes later the same command landed on the OLD host and completed **exit 0** with a real 768x1376 JPEG in 42.2 s, proving the host guard is scoped and does not short-circuit the working path. Three items recorded as NOT verified rather than omitted: driving the migrated frontend (still impossible, #639 stays open), the pt-BR recovery live (measured `html lang=pt` on `denon82` but exercised live only on `en-GB`), and the `en-GB`→`en` region reduction against a locale where region is load-bearing (`zh-Hans`/`zh-Hant`) — only two locales observed.

{gflow_cli-0.83.1 → gflow_cli-0.84.0}/docs/LIVE_VERIFICATION_v0.83.1.md

@@ -54,9 +54,9 @@
 
 | Evidence | Result |
 |---|---|
-| Signed tag | pending |
-| Release workflow | pending |
-| GitHub Release | pending |
-| PyPI | pending |
-| Clean install | pending |
-| Release PR | pending |
+| Signed tag | `v0.83.1` (SSH signature) on `a841e716` |
+| Release workflow | [run 37809384940](https://github.com/ffroliva/gflow-cli/actions/runs/37809384940): `build-and-publish` success, `mcp-registry / publish` success |
+| GitHub Release | https://github.com/ffroliva/gflow-cli/releases/tag/v0.83.1 (not a prerelease) |
+| PyPI | `gflow-cli 0.83.1` served by pypi.org/pypi/gflow-cli/json |
+| Clean install | `uvx --refresh --from gflow-cli==0.83.1 gflow --version` → `gflow, version 0.83.1` (first attempt hit PyPI index lag, "unsatisfiable"; resolved on retry) |
+| Release PR | #960 merged into `main` (`d0dc678c`, merge commit) after `ProfileLease (macos-latest)` twice got no runner (0 steps) and passed on attempt 3; back-merged into `develop` (`7e1eeacb`) |

gflow_cli-0.84.0/docs/LIVE_VERIFICATION_v0.83.2.md

@@ -0,0 +1,70 @@
+# Live verification — v0.83.2
+
+> Evidence for this release, gathered on 2026-10-10/11 (PRs #962, #964, #965). Each row is a
+> run someone watched, not an inference. Where a check could not be run, the blocker is
+> named.
+
+## Environment
+
+| | |
+|---|---|
+| Profile | `denon82` (real-browser Chrome strategy) |
+| Host Flow served | `flow.google.com` (classic composer) |
+| UI locale | `pt` by default; forced to `vi` with `?hl=vi` + `Accept-Language: vi` for #963, read back from `document.documentElement.lang` |
+| Transport | `ui_automation` → migrated composer |
+| OS | Windows 11 (Google Chrome installed) |
+| Veo credits spent | 0 |
+
+## Summary
+
+| Change | Surface | Verified live? | Cost |
+|---|---|---|---|
+| Duration radio matched on its number, not the English unit (#963, PR #964) | `apply_video_settings` in a Vietnamese settings pane | ✅ e2e `test_e2e_duration_binds_in_a_vietnamese_pane`: **failed** with `develop`'s composer (exit 11, the reporter's error), **passed** on the branch and again on the release tree; `4 giây` and `8 giây` read back checked | $0 (no submit) |
+| Notice-only cookie bar acknowledged when it has no reject (PR #964) | `_dismiss_cookie_bar` under `hl=vi` | ✅ the spike first stopped on this bar (exit 23); the same e2e now passes through it | $0 |
+| Image tile and download button clicked through locators (#957, PR #965) | `gflow image upscale` (2K), CLI door | ✅ e2e `test_migrated_image_upscale_2k_e2e` passed on the branch and the release tree | quota only |
+| Same, MCP door | `gflow_upscale_image` | ✅ e2e `test_mcp_upscale_image_2k_e2e` passed on the branch and the release tree | quota only |
+| `auth status` migrated-host probe opens the profile with its own channel (#962) | `gflow auth status` | ⚠️ no regression only: on the release tree, `gflow auth status --profile denon82` exited 0, *Flow session verified*. That output does not prove the migrated fallback ran, and this host has Chrome, so the fixed branch (no Chrome) was not reached | $0 |
+
+## 5-layer ledger (release tree, 2026-10-11)
+
+| Layer | Locale e2e | Image upscale e2e (CLI + MCP) |
+|---|---|---|
+| File count | n/a (settings only, no submit) | 1 upscaled image per door, asserted by the tests |
+| Magic bytes | n/a | CLI: asserted PNG or JPEG header and > 100 kB; MCP: not asserted (file exists and opens as an image) |
+| Dimensions | n/a | long side ≥ the 2K floor, asserted on both doors; CLI also asserts larger than the source |
+| structlog | no `UiSelectorDriftError`, no exit 11 | no `Element is not attached to the DOM` |
+| User-confirmable artifact | the pane's `N giây` radio read back checked for N = 4 and 8 | the upscaled file in the project's newest catalogued image |
+
+`pytest -m e2e tests/e2e/test_migrated_locale_e2e.py` + the two image-upscale tests on the
+release tree: **3 passed in 101.93 s**.
+
+## Not verified
+
+- **#962 on a host without Google Chrome.** Blocker: every host we drive has Chrome
+  installed, so `channel_for_profile` returns `chrome` either way. Covered offline by
+  `9ea59653` (a chrome-marked profile on a host without Chrome); the contributor reported
+  the original failure on such a host.
+- **Video upscale 1080p.** It raised `UpscaleUnavailableError` on `develop` as well,
+  because the newest clip's 1080p option is disabled on this account. Filed as #967; the
+  shared download-menu helper is covered by the image runs above.
+- **Accounts served labs.** Blocker: every profile we hold is redirected to
+  flow.google.com.
+
+## Pre-tag gates
+
+| Gate | Result |
+|---|---|
+| `/gflow:changelog` | `[Unreleased]` → `[0.83.2] — 2026-10-11`: Fixed (#963, notice-only cookie bar, #957, #962) |
+| `/gflow:check` | ruff, format, pyright 0, hygiene, doc links, PII, mirror (regenerated after the KNOWN_ISSUES fix), council memory, release artifacts green; pytest 4923 passed, 24 skipped, coverage 93% |
+| SonarCloud | PR #964 and PR #965 gates passed; #962 was a fork PR (skipped, maintainer-checked) |
+| `/gflow:doc-review` | council: Auditor 1 YELLOW (KNOWN_ISSUES sent a non-English `--duration` exit-11 user to the cohort workaround; PROJECT_STATUS omitted video upscale from *Not verified*) → KNOWN_ISSUES now names #963 and says upgrade first, PROJECT_STATUS lists #967. Auditor 2 YELLOW (CHANGELOG `auth status` entry had no PR number) → now cites PR #962; 7 version sites, footer, `<details>` balance, mirror in sync. Auditor 3 GREEN (every claim matched to code, `_duration` regex run against decoys). Deferred: "a miss raises exit 11" holds only when the pane renders option groups (exit 23 otherwise, unchanged). Reports local at `tmp/council/` |
+
+## Post-tag evidence
+
+| Evidence | Result |
+|---|---|
+| Signed tag | `v0.83.2` (SSH signature) on `a486f831` |
+| Release workflow | [run 38109515205](https://github.com/ffroliva/gflow-cli/actions/runs/38109515205): `build-and-publish` success, `mcp-registry / publish` success |
+| GitHub Release | https://github.com/ffroliva/gflow-cli/releases/tag/v0.83.2 (not a prerelease) |
+| PyPI | `uvx --refresh --from gflow-cli==0.83.2 gflow --version` → `gflow, version 0.83.2` |
+| Release PR | #968 merged into `main` (`b12a1730`, merge commit; all checks incl. SonarCloud green); back-merged into `develop` (`98ea3232`) |

gflow_cli-0.84.0/docs/LIVE_VERIFICATION_v0.84.0.md

@@ -0,0 +1,61 @@
+# Live verification — v0.84.0
+
+> Evidence for this release, gathered on 2026-10-12 (PRs #970, #971). Each row is a run
+> someone watched, not an inference. Where a check could not be run, the blocker is named.
+
+## Environment
+
+| | |
+|---|---|
+| Profile | `denon82` (real-browser Chrome strategy) |
+| Host Flow served | `flow.google.com` |
+| Transport | `ui_automation` → migrated composer |
+| OS | Windows 11 (Google Chrome installed) |
+| Veo credits spent | 0 (images only, daily image quota) |
+
+## Summary
+
+| Change | Surface | Verified live? | Cost |
+|---|---|---|---|
+| `gflow run --project ID` generates every row into an existing project (#970) | `gflow run --config … --project` | ✅ e2e `test_a_run_given_an_existing_project_generates_every_row_into_it_and_creates_none` passed on `develop` after the merge (63.6 s). The contributor also ran it, with the two existing `batch:N` / local-file scenarios, on their own account served flow.google.com | quota only |
+| Multi-prompt `gflow image t2i --project ID` runs every prompt in that project (#971) | `gflow image t2i "a" "b" --project` | ✅ new e2e `test_multi_prompt_t2i_runs_every_prompt_in_the_given_project` passed on the branch (60.8 s), on a tree identical to the release tree. A first run failed on the test's own `*.png` glob (this host serves JPEG); the CLI had exited 0 with both images saved | quota only |
+
+## 5-layer ledger
+
+| Layer | `gflow run --project` e2e | `t2i --project` e2e |
+|---|---|---|
+| File count | 2 rows, a saved image each, asserted | 2 prompts, ≥ 2 files in `--out`, asserted |
+| Magic bytes | not asserted; each file opens with Pillow (a real image) | not asserted; size > 10 kB asserted (files are `.jpg`) |
+| Dimensions | short side ≥ 512 px, asserted | not asserted |
+| structlog | run summary prints `(existing)` for the project, asserted | CLI exit 0, asserted |
+| User-confirmable artifact | catalog holds exactly the created project, title unchanged; every asset's `flow_project_id` is that project | same two catalog assertions |
+
+## Observed, not changed
+
+- **A project id that does not exist.** Run on the release tree:
+  `gflow image t2i "a paper boat" "a kite" --project 00000000-0000-0000-0000-000000000000
+  --fail-fast`. Flow redirected to `flow.google.com/404?reason=project`; gflow waited 30 s
+  for `.settings-trigger-button` and failed row 0 with **exit 23** (`UiSelectorDriftError`),
+  row 1 skipped, no image, nothing billed. The run stops safely, but exit 23 names the wrong
+  cause (a missing project, not selector drift). The same path serves single-prompt
+  `t2i --project`, so this predates the release.
+- **No MCP door.** `gflow run` is exempt in `tests/mcp/test_cli_parity.py` ("not yet
+  ported") and `gflow_generate_image` takes one prompt, so neither change has an MCP twin to
+  verify.
+
+## Not verified
+
+- **Accounts served labs.** Blocker: every profile we hold is redirected to flow.google.com.
+
+## Pre-tag gates
+
+| Gate | Result |
+|---|---|
+| `/gflow:changelog` | `[Unreleased]` → `[0.84.0] — 2026-10-12`: Added (#970, #971) |
+| `/gflow:check` | on `827a0076` (tree identical to `develop@c7bc2430`, the release cut): hygiene, doc links, PII, mirror, council memory, ruff, format, pyright 0; pytest 4937 passed, 24 skipped, coverage 93% |
+| SonarCloud | #970 was a fork PR (skipped); `develop` gate after its merge passed (new coverage 100%, 0 new issues). PR #971 gate passed |
+| `/gflow:doc-review` | mechanical: links, PII, mirror, footer, 7 version sites green (older ledgers reachable only through INDEX's previous-chain, pre-existing). Council: Auditor 1 YELLOW (ACCOUNT_SAFETY still framed `--project` as single-prompt; `t2i --help` did not say it works with several prompts) → ACCOUNT_SAFETY updated, help now says so. Auditor 2 YELLOW (CHANGELOG cited no PR numbers; ACCOUNT_SAFETY; KNOWN_ISSUES #913 said a re-run always creates a project) → all three fixed. Auditor 3 GREEN (every claim matched to code; both options graded D4). Deferred: a missing project reports exit 23 instead of naming the project (see *Observed*). Reports local at `tmp/council/` |
+
+## Post-tag evidence
+
+_Filled after the signed tag is pushed and the release workflow publishes._

{gflow_cli-0.83.1 → gflow_cli-0.84.0}/docs/PROJECT_STATUS.md

@@ -4,6 +4,46 @@
 
 ## Current release
 
+**v0.84.0 — alpha.** Batch image runs can target an existing Flow project.
+
+**`gflow run --project ID` (#970).** Every run used to create a new project titled
+`gflow-cli run`. `--project` (or a top-level `"project"` key in the config; the CLI wins)
+now runs every row in that existing project and creates none, and the project keeps its
+title in the local catalog. Contributed by @BeckZero.
+
+**`gflow image t2i` takes `--project` with several prompts (#971).** A multi-prompt run
+used to reject `--project` as single-prompt only; it now runs every prompt in that project
+on the same path. `--reference-entity` stays single-prompt only.
+
+Neither command has an MCP twin for this: `gflow run` is not ported yet, and the MCP image
+tool takes one prompt. Full ledger: [LIVE_VERIFICATION_v0.84.0](LIVE_VERIFICATION_v0.84.0.md).
+
+<details><summary>v0.83.2 — non-English UIs, image upscale, and auth status without Chrome</summary>
+
+**v0.83.2 — alpha.** Three fixes on flow.google.com: non-English UIs, image upscale, and
+`auth status` on hosts without Chrome.
+
+**`--duration` works in a non-English Flow UI (#963).** The duration radio was matched on
+its English label (`8s`), so a Vietnamese pane (`8 giây`) stopped every `--duration` run
+at exit 11, before any credit was spent. The radio is now matched on its number, measured
+identical across locales; AGENTS.md records this as the second text-selector exception.
+Live-checking it under a Vietnamese UI also found a **notice-only cookie bar** (no reject
+button) that blocked every run at exit 23; it is now acknowledged when it has no reject.
+
+**`gflow image upscale` no longer fails with *Element is not attached to the DOM* (#957).**
+The tile and download button are Playwright locators, re-resolved on every action.
+
+**`gflow auth status` no longer reports a migrated account as signed out on hosts without
+Google Chrome.** The probe opens the profile with the same channel generation uses.
+
+**Not verified here:** a host without Google Chrome; video upscale, which shares the fixed
+helper but whose live run hit a disabled 1080p option (#967); accounts served labs. Full ledger:
+[LIVE_VERIFICATION_v0.83.2](LIVE_VERIFICATION_v0.83.2.md).
+
+</details>
+
+<details><summary>v0.83.1 — the default image model works on flow.google.com again</summary>
+
 **v0.83.1 — alpha.** The default image model works on flow.google.com again.
 
 **`nano2` runs Nano Banana 2.1 on flow.google.com (#958).** Flow replaced "Nano Banana 2"
@@ -16,6 +56,8 @@ first fixed by @omid-io.
 **Not verified here:** accounts served labs. Full ledger:
 [LIVE_VERIFICATION_v0.83.1](LIVE_VERIFICATION_v0.83.1.md).
 
+</details>
+
 <details><summary>v0.83.0 — video downloads on flow.google.com, upscaling ported</summary>
 
 **v0.83.0 — alpha.** Video runs on flow.google.com download again, and upscaling is
@@ -424,6 +466,8 @@ migrated accounts (#795), and the agent-only composer driver (#799, #824 open).
 
 | Milestone | Status |
 |---|---|
+| `gflow run --project` (#970) and multi-prompt `gflow image t2i --project` (#971) generate into an existing Flow project and create none | ✅ done (v0.84.0) |
+| `--duration` binds in a non-English Flow UI (#963), a notice-only cookie bar is acknowledged, image upscale clicks through locators (#957), and `auth status` probes with the profile's own channel (#962) | ✅ done (v0.83.2) |
 | The default image model (`nano2`) runs Nano Banana 2.1 on flow.google.com — the submit guard accepts its `BELUGA` token (#958) | ✅ done (v0.83.1) |
 | Billed video runs on flow.google.com download again — the generation record is found without its `"CAE"` marker, picked by id from multi-record replies, recovered from `as29s` only (#948); image and video upscale ported to flow.google.com with MCP twins (#922) | ✅ done (v0.83.0) |
 | A reCAPTCHA mint failure, a busy catalog and a missing video workflow id stop misreporting what happened (#915, #900, #898) | ✅ done (v0.82.1) |