gflow-cli 0.89.1__tar.gz → 0.90.0__tar.gz

{gflow_cli-0.89.1 → gflow_cli-0.90.0}/.codex-plugin/plugin.json

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

{gflow_cli-0.89.1 → gflow_cli-0.90.0}/CHANGELOG.md

@@ -7,6 +7,97 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.90.0] — 2026-10-25
+
+### Added
+
+- **`gflow run --resume` picks up where a run stopped**
+  ([#934](https://github.com/ffroliva/gflow-cli/issues/934)). With the same config,
+  project and output folder, a row whose images are already on disk and recorded in the
+  local catalog as that project's is shown as `RESUMED` and not generated again, and a
+  `batch:N` child references it in place. Before, a re-run regenerated every row, parents
+  included, spending image quota twice. `--resume` needs `--project` or a config
+  `"project"` (exit 11 otherwise). CLI only, like `gflow run` itself.
+
+### Fixed
+
+- **`image i2i --ref <file>` no longer uploads the same file again on every run**
+  ([#772](https://github.com/ffroliva/gflow-cli/issues/772)). On flow.google.com, a loop
+  over prompts with one `--ref` file left one copy of that image in the project's library
+  per run. The first upload is now recorded in the local catalog, and a later run in the
+  same project with the same file (same path, same bytes) mentions that image in place.
+  If it was deleted from the project since, the file is uploaded again and the new copy
+  recorded. The MCP image tool does the same. On labs, a file not yet recorded in the
+  project still goes through the editor's own filename dedup (#314).
+
+- **A corrupt cookie store is no longer reported as a network problem**
+  ([#796](https://github.com/ffroliva/gflow-cli/issues/796)). When a profile's Chrome
+  cookie database could not be read as a database, `gflow auth status` said "check
+  network connectivity". It now names the cookie store and says to close any Chrome
+  window using the profile and run `gflow auth login` again. The MCP `gflow_auth_status`
+  tool returns a new `cookie_store_unreadable` outcome (HTTP 409, `retryable: false`)
+  instead of the retryable `verification_error` (#796).
+
+- **The MCP `wait` parameter is described where agents read it**. `gflow_generate_image`
+  and `gflow_generate_video` now carry a `wait` description in `tools/list`: the default
+  `true` runs the generation inside the call, which can outlast a client's tool timeout,
+  and `false` only enqueues it and returns a `task_id` for `tasks/get`. It also says that
+  no gflow command runs the queue worker yet, so a `wait=false` job is never generated
+  (`tasks/get` keeps reporting it as `working`; #1097). The default is unchanged. See
+  [MCP](docs/MCP.md) (#481).
+
+- **`movie run` refuses costume `variants` on an entity character**
+  ([#724](https://github.com/ffroliva/gflow-cli/issues/724)). A variant appends a text
+  delta to the prompt, but an `identity = "entity"` character's body reference already
+  fixes one outfit, so the two contradicted each other inside one generation with no
+  telling which would win. Such a manifest used to run; it is now a configuration error
+  (exit 11) when it is parsed, before any browser starts, and the message says what to do
+  instead: one entity per costume, sharing the same `face_prompt`. Variants on
+  `identity = "text"` characters are unchanged.
+
+- **An output folder gflow cannot write is exit 11, not "Unexpected error"**
+  ([#1091](https://github.com/ffroliva/gflow-cli/issues/1091)). After a successful
+  generation, a failed local write (for example `--out` pointing at a protected folder)
+  kept the media id (#1035) but then ended in the catch-all, with exit 1 and a "file a
+  bug" message. It now ends as a configuration error (exit 11) that says the asset is
+  still in the Flow project. This covers image downloads, upscale and extend exports and
+  scene output, on both the CLI and MCP; a generated video clip keeps its exit 6
+  ([#1003](https://github.com/ffroliva/gflow-cli/issues/1003)).
+
+- **A credit shortfall on flow.google.com is recognised in every UI language, and only
+  when Flow shows it** ([#745](https://github.com/ffroliva/gflow-cli/issues/745)). The
+  warning anchor had an English `aria-label` half, which Flow translates; it is now the
+  warning button's class alone (the measured element carries both). And the check now
+  requires the warning to be visible, so a hidden one Flow keeps mounted cannot turn a
+  real selector drift into "top up your credits" (exit 37).
+
+- **Selector drift is watched again, on flow.google.com**
+  ([#1083](https://github.com/ffroliva/gflow-cli/issues/1083)). The nightly GitHub
+  `selector-probe` workflow loaded the labs.google editor, which redirects to
+  flow.google.com for every account we hold, so it failed as "no recognizable editor" on
+  every run from 2026-08-21 and checked nothing. The selector registry gains a
+  `migrated_editor` surface built from the migrated composer's own constants, graded by a
+  new `$0` `e2e_auth` test that the local canary runs nightly (`run_canary.py --project`);
+  the dead workflow is retired. The canary's labs REST upload test now skips with the
+  measured reason (labs.google serves no session token) instead of reading as RED.
+
+- **The flow.google.com reference-to-video chip-count refusal states the numbers it
+  compared** ([#745](https://github.com/ffroliva/gflow-cli/issues/745)). The guard counts
+  image references and characters together, but the message printed only the image
+  count, so a mismatch caused by a character read as "1 requested but 1 on the prompt".
+  It now reads, for example, "1 image reference(s) + 1 character(s) = 2 chip(s) requested
+  but 1 on the prompt".
+
+### Changed
+
+- **A signed media URL that answers an HTTP error is a failed download, exit 6, not
+  exit 7** ([#941](https://github.com/ffroliva/gflow-cli/issues/941), part 2). After Flow
+  reports a clip done, an error status on its download link (an expired link, for example)
+  used to raise `WireFormatError` (exit 7) and leave the clip `pending` in the catalog. It
+  now raises `MediaDownloadError` (exit 6, `retryable: false`) naming the clip, so the
+  catalog marks it generated and `gflow data download <media_id>` recovers it for free.
+  Scripts that branch on exit 7 for this case should branch on 6.
+
 ## [0.89.1] — 2026-10-24
 
 ### Added
@@ -6576,7 +6667,8 @@ 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.89.1...HEAD
+[Unreleased]: https://github.com/ffroliva/gflow-cli/compare/v0.90.0...HEAD
+[0.90.0]: https://github.com/ffroliva/gflow-cli/compare/v0.89.1...v0.90.0
 [0.89.1]: https://github.com/ffroliva/gflow-cli/compare/v0.89.0...v0.89.1
 [0.89.0]: https://github.com/ffroliva/gflow-cli/compare/v0.88.0...v0.89.0
 [0.88.0]: https://github.com/ffroliva/gflow-cli/compare/v0.87.1...v0.88.0

{gflow_cli-0.89.1 → gflow_cli-0.90.0}/KNOWN_ISSUES.md

@@ -394,7 +394,7 @@ has not landed yet stay nameless until the next sync sweep.
 
 ### `gflow run --config` references cannot resume (#913)
 
-- **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)
+- **Status:** Mitigated ([#934](https://github.com/ffroliva/gflow-cli/issues/934): `gflow run --resume`) · **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 (or, with
@@ -403,6 +403,10 @@ it. The handle that makes in-place referencing work (Flow's reply for the parent
 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.
 
+**Mitigation:** `gflow run --resume` with the same project and output folder skips every
+row whose files are on disk and recorded in the catalog as that project's images, and its
+`batch:N` children reference it in place. A local-file `ref` is still uploaded again.
+
 ### Video duration control is absent on some account cohorts
 
 - **Status:** Mitigated — fail-fast shipped in

{gflow_cli-0.89.1 → gflow_cli-0.90.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: gflow-cli
-Version: 0.89.1
+Version: 0.90.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.89.1 → gflow_cli-0.90.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.89.1
+ARG GFLOW_VERSION=0.90.0
 RUN pip install --no-cache-dir "gflow-cli==${GFLOW_VERSION}"
 
 VOLUME ["/data"]

{gflow_cli-0.89.1 → gflow_cli-0.90.0}/docs/AUTHENTICATION.md

@@ -281,7 +281,7 @@ Probing Flow session (may take up to ~45s on a slow network)...
 Flow session verified as you@example.com.
 ```
 
-> Note: `cookies_present: True` only confirms the file exists. The final verdict line is the live probe result, and it has three failing shapes — all exit 1, each with a different hint. A **dead session** prints a `gflow auth login` remediation hint. A probe that **cannot reach the endpoint** (offline, 5xx) suggests checking connectivity instead of re-logging in. And a profile **missing its `.gflow_browser_strategy` marker** — the state a failed *first* login leaves behind, since that rolls the marker back — says so and points at `gflow auth login --browser chrome --profile <name>`; it is local profile state, not a network fault, and "check connectivity" would send you to the wrong place ([#796](https://github.com/ffroliva/gflow-cli/issues/796), 0.73.2). The MCP twin `gflow_auth_status` reports the same three as HTTP 401, 503 (`retryable: true`) and 409 (`retryable: false`) — see [MCP.md](MCP.md).
+> Note: `cookies_present: True` only confirms the file exists. The final verdict line is the live probe result, and it has four failing shapes — all exit 1, each with a different hint. A **dead session** prints a `gflow auth login` remediation hint. A probe that **cannot reach the endpoint** (offline, 5xx) suggests checking connectivity instead of re-logging in. And a profile **missing its `.gflow_browser_strategy` marker** — the state a failed *first* login leaves behind, since that rolls the marker back — says so and points at `gflow auth login --browser chrome --profile <name>`; it is local profile state, not a network fault, and "check connectivity" would send you to the wrong place ([#796](https://github.com/ffroliva/gflow-cli/issues/796), 0.73.2). A **corrupt or unreadable cookie store** says so and tells you to close any Chrome window using that profile, then run `gflow auth login --profile <name>` again; if that login reports the same, its hint names the last resort: delete the profile's `Default/Network/Cookies` file (this signs the profile out) and log in again ([#796](https://github.com/ffroliva/gflow-cli/issues/796), 0.90.0). The MCP twin `gflow_auth_status` reports the four as HTTP 401, 503 (`retryable: true`), 409 (`retryable: false`) and 409 (`cookie_store_unreadable`, `retryable: false`) — see [MCP.md](MCP.md).
 
 ### `gflow auth renew`
 

{gflow_cli-0.89.1/website → gflow_cli-0.90.0}/docs/CONFIGURATION.md

@@ -407,8 +407,9 @@ unaffected and always opens where you can see it.
 | animation frames / 100 ms timer ticks in 5 s | 300 / 50 | 295 / 50 |
 
 Chrome does not throttle an off-screen window: the page still counts as visible.
-Windows clamps very large offsets, so `-30000,-30000` lands at `-21845,-21845`, still
-past any monitor, on every launch measured. A visible position such as `100,100` opened
+On Windows, `-30000,-30000` landed at `-21845,-21845` (a clamp) on every launch measured
+in September 2026, and at `-30000,-30000` unclamped from 2026-10-25. Either way it is past
+any monitor. A visible position such as `100,100` opened
 exactly there on 8 of 10 launches. In the other two the window was found elsewhere, and
 once it was seen moving mid-run: a visible window can be moved like any other once it
 is open. Not yet measured on macOS or

{gflow_cli-0.89.1 → gflow_cli-0.90.0}/docs/DATA_LAYER.md

@@ -210,7 +210,8 @@ async worker (which mirrors its `generation_queue.error_json` failure into
   (`MediaDownloadError`, exit 6, `error_type=media-download`, #896) also marks that
   clip's asset `MEDIA_GENERATION_STATUS_SUCCESSFUL`: the operation failed, the
   generation did not, and `gflow data download <media_id>` recovers it for free. An
-  HTTP error answer on the signed URL (e.g. an expired link) still leaves it `pending`.
+  HTTP error answer on the signed URL (e.g. an expired link) is the same
+  `MediaDownloadError` and marks it the same way (#941; it was exit 7 and stayed `pending`).
 - A poll that COMPLETES with a Flow-reported failure (`succeeded=false`) is
   recorded as `failed` with `error_type=generation-failed` and the
   `failure_reasons` as detail — not as a success.

{gflow_cli-0.89.1 → gflow_cli-0.90.0}/docs/E2E_TESTING.md

@@ -340,54 +340,36 @@ tokens**. Published content is sanitized for a public repo: SHA, pass/fail
 counts, duration, failure class, and failing test *names* only — never raw logs,
 profile paths, prompts, or signed URLs.
 
-## Selector drift probe (#563)
+## Selector drift check (#563, moved to the canary in #1083)
 
-The canary answers *"does gflow still work on the maintainer's cohort?"*; the
-probe answers *"which Flow DOM selector moved?"* — from hosted CI, with no
-maintainer machine involved. It walks the structured selector inventory in
-`gflow_cli.flow_selectors` (the incident families from #404/#493/#313) against
-a live editor at the pinned 1920×1080 viewport: navigate and read only, **$0**,
-never submits.
+The canary answers *"does gflow still work on the maintainer's cohort?"*; the drift check
+answers *"which Flow DOM selector moved?"*. It grades the structured selector inventory in
+`gflow_cli.flow_selectors` against a live editor: navigate and read only, **$0**, never
+submits.
 
-Runs via `.github/workflows/selector-probe.yml` on `schedule` (05:00 UTC daily)
-plus `workflow_dispatch`. **Never add a `pull_request` trigger**: same-repo
-branch PRs receive repository secrets while running attacker-editable probe
-code (fork PRs are safe — GitHub withholds secrets — but the same-repo case is
-not).
+**Where it runs.** `tests/e2e/test_migrated_selector_drift_e2e.py` (`e2e_auth`) grades the
+registry's `migrated_editor` surface (flow.google.com) with the probe's own `resolve` and
+report, so the nightly canary runs it with every other `$0` tier. Give the canary a project
+the profile owns: `run_canary.py --project <id>` (or `register_task.ps1 -Project <id>`);
+without one the test skips.
 
-### Exit contract
+**Why it moved.** It used to run from `.github/workflows/selector-probe.yml` against the
+labs.google editor with one NextAuth cookie. labs answers 308 to flow.google.com for every
+account we hold, so that workflow exited 2 ("no recognizable editor") on every run from
+2026-08-21 until it was retired, about two months in which nothing watched for drift
+(#1083). Running it in GitHub would now need a full Google session in repository secrets;
+the canary already holds a warm profile on the maintainer's machine.
 
-| Exit | Meaning | Action |
+### Reading the report
+
+| Grade | Meaning | Action |
 |---|---|---|
-| `0` | every registered selector resolved (`ok` / `FALLBACK[n]` / `n/a`) | none |
-| `1` | **drift** — a selector graded MISS or AMBIGUOUS; the report names its key | re-derive that selector, ship a registry edit |
-| `2` | **inconclusive** — expired token, dead project, known alternate UI state, or no recognizable editor arm | fix the credential/project; says nothing about Flow |
-
-Keeping `1` and `2` apart is the whole design: an expired credential must never
-be published as "Google changed the page". The deciding gate is a poll on
-production's own arm indicators (the six `crop_*` variants ⇒ classic, the
-agentic ligatures ⇒ agentic); a page showing neither within 25 s — a sign-in
-wall renders neither — is inconclusive, not drift. Mode-scoped selectors absent
-on the observed arm grade `n/a` (`EXPECTED_ABSENT`), never drift — the probe's
-first two live runs landed on opposite arms (classic locally, agentic on the
-runner) and both graded clean.
-
-### Secrets and token care
-
-Two repository secrets, from a **dedicated throwaway Google account**, never
-the maintainer's: `GFLOW_CI_SESSION_TOKEN` (the
-`__Secure-next-auth.session-token` cookie) and `GFLOW_CI_PROJECT_ID` (any
-project that account owns — a deleted id renders an error shell the probe
-reports as exit 2).
-
-The token **re-issues on every profile open** (observed live 2026-08-21: three
-values in 15 minutes; the first CI dispatch failed exit 2 on a superseded
-snapshot). Harvest accordingly: open the throwaway profile once, read the
-cookie, close the browser, `gh secret set GFLOW_CI_SESSION_TOKEN` from stdin —
-and never reopen that profile without re-syncing the secret afterwards. The
-value also hard-dies at day 30 with no warning. Either way an aged token shows
-as a red exit-2 run, never as drift, and the nightly schedule itself is the
-aging test.
+| `ok` / `FALLBACK[n]` | the selector resolved (a later candidate held for `FALLBACK`) | none; a FALLBACK says how far the page drifted |
+| `n/a` | a mode-scoped entry is absent on the arm Flow served (e.g. the agent-only composer's anchor on a classic account) | none |
+| `DRIFT` / `AMBIGUOUS` | the selector matched nothing, or more than one element where one is expected | the canary turns RED and names the key; re-derive that selector and edit the registry |
+
+`scripts/probe/run_probe.py` still holds `resolve` and `render_report`; its labs `editor`
+surface is kept for an account that is served labs, which none of ours is today.
 
 ---
 
@@ -403,6 +385,7 @@ tests/
     ├── conftest.py                       # e2e_profile_dir, e2e_nosession_profile,
     │                                     #   e2e_env (shared fixtures)
     ├── test_auth_verification_e2e.py     # [e2e, e2e_auth]
+    ├── test_migrated_selector_drift_e2e.py # [e2e, e2e_auth] registry vs flow.google.com — 0 credits
     ├── test_auth_renew_e2e.py            # [e2e, e2e_auth] `gflow auth renew` leaf — 0 credits
     ├── test_credits_refresh_e2e.py       # [e2e, e2e_auth] `--refresh` on CLI + MCP — 0 credits
     ├── test_transports_e2e.py            # [e2e, e2e_{auth,image,batch,video}]

{gflow_cli-0.89.1 → gflow_cli-0.90.0}/docs/INDEX.md

@@ -172,7 +172,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.89.1](LIVE_VERIFICATION_v0.89.1.md) (**2026-10-24, no Veo credits.** Release-tree e2e 9 passed, 1 skipped (credit-spending video case): lost image replies recovered from the grid on t2i and i2i (#1075), upscale straight after generating with no pause (#1067), visible model picker, auth and pre-submit regressions; hidden-picker, `/about` and declined-upload paths offline, blockers named) · previous: [LIVE_VERIFICATION_v0.89.0](LIVE_VERIFICATION_v0.89.0.md) (**2026-10-23, no Veo credits.** Release-tree e2e 20/20 (one re-run after #1010's lost reply body): #1039 default project CLI+MCP; #974/#1053 a missing project is exit 11 on generation, upscale and extend; #1038 nano2.1; #914 warm-client upscale; #892 pre-submit gate; #927 window position; #984/#1059 held profile exit 11 on the PR branches) · previous: [LIVE_VERIFICATION_v0.88.0](LIVE_VERIFICATION_v0.88.0.md) (**2026-10-22, no Veo credits.** #1036 browser proxy through a local proxy; #1037 slow-link create; #992 lost-reply readback; #1035 failed image download keeps the ids; #1041 quiet output; #1026 internal login) · previous: [LIVE_VERIFICATION_v0.87.1](LIVE_VERIFICATION_v0.87.1.md) (**2026-10-22, $0 apart from one Veo lite clip for the #795 spike.** #795: `gflow credits` balance equals Flow's account menu on two accounts, CLI and MCP; #1027: 2K image upscale and both video exports pass with the shared blob capture; project create/rename re-run for the shared `_rpc_reply`) · older: [LIVE_VERIFICATION_v0.87.0](LIVE_VERIFICATION_v0.87.0.md) (**2026-10-22, Veo lite clips under the e2e grant.** #1023: auth status/renew/MCP twin verify again after labs' session URL went 410; #1010: a lost submit reply makes one submit and a non-retryable exit 9, image and video; #1013, #995, #997, #986, #1014 e2e passed on the release tree; image-upscale body loss filed as #1027) · older: [LIVE_VERIFICATION_v0.86.0](LIVE_VERIFICATION_v0.86.0.md) (**2026-10-17/18, 2 Veo extends (owner-approved).** #991: `video extend` on flow.google.com — paid single-segment extend passed on the release tree, plus 3 $0 route-guard e2e; #989: agent-only composer — classic-composer regression 11 passed, agent-only path blocked externally (no account in that cohort; run live by 3 outside users); #982: `auth renew` 4 passed incl. stale→readable and /about) · previous: [LIVE_VERIFICATION_v0.85.0](LIVE_VERIFICATION_v0.85.0.md) (**2026-10-14, 0 credits.** #723/#979: `@Character` on flow.google.com images — 4-scenario e2e (CLI t2i, MCP, i2i + character, id-only refusal) passed on the release tree; #975: multi-prompt `t2i --project-name` — e2e passed) · previous: [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)
+**What was actually live-verified for the latest release?** → latest: [LIVE_VERIFICATION_v0.90.0](LIVE_VERIFICATION_v0.90.0.md) (**2026-10-25, no Veo credits in the release run.** Release-tree e2e 15/15: #772 a local `--ref` uploaded once per project (CLI, MCP, and a recorded image the project no longer holds); #1091 unwritable output exit 11; #934 `run --resume`; #745 credit shortfall; #1083 selector drift; the two re-armed canary tests; #796 and #481 verified at $0 on their PRs; #941 on its PR with one veo-lite clip) · previous: [LIVE_VERIFICATION_v0.89.1](LIVE_VERIFICATION_v0.89.1.md) (**2026-10-24, no Veo credits.** Release-tree e2e 9 passed, 1 skipped (credit-spending video case): lost image replies recovered from the grid on t2i and i2i (#1075), upscale straight after generating with no pause (#1067), visible model picker, auth and pre-submit regressions; hidden-picker, `/about` and declined-upload paths offline, blockers named) · previous: [LIVE_VERIFICATION_v0.89.0](LIVE_VERIFICATION_v0.89.0.md) (**2026-10-23, no Veo credits.** Release-tree e2e 20/20 (one re-run after #1010's lost reply body): #1039 default project CLI+MCP; #974/#1053 a missing project is exit 11 on generation, upscale and extend; #1038 nano2.1; #914 warm-client upscale; #892 pre-submit gate; #927 window position; #984/#1059 held profile exit 11 on the PR branches) · previous: [LIVE_VERIFICATION_v0.88.0](LIVE_VERIFICATION_v0.88.0.md) (**2026-10-22, no Veo credits.** #1036 browser proxy through a local proxy; #1037 slow-link create; #992 lost-reply readback; #1035 failed image download keeps the ids; #1041 quiet output; #1026 internal login) · previous: [LIVE_VERIFICATION_v0.87.1](LIVE_VERIFICATION_v0.87.1.md) (**2026-10-22, $0 apart from one Veo lite clip for the #795 spike.** #795: `gflow credits` balance equals Flow's account menu on two accounts, CLI and MCP; #1027: 2K image upscale and both video exports pass with the shared blob capture; project create/rename re-run for the shared `_rpc_reply`) · older: [LIVE_VERIFICATION_v0.87.0](LIVE_VERIFICATION_v0.87.0.md) (**2026-10-22, Veo lite clips under the e2e grant.** #1023: auth status/renew/MCP twin verify again after labs' session URL went 410; #1010: a lost submit reply makes one submit and a non-retryable exit 9, image and video; #1013, #995, #997, #986, #1014 e2e passed on the release tree; image-upscale body loss filed as #1027) · older: [LIVE_VERIFICATION_v0.86.0](LIVE_VERIFICATION_v0.86.0.md) (**2026-10-17/18, 2 Veo extends (owner-approved).** #991: `video extend` on flow.google.com — paid single-segment extend passed on the release tree, plus 3 $0 route-guard e2e; #989: agent-only composer — classic-composer regression 11 passed, agent-only path blocked externally (no account in that cohort; run live by 3 outside users); #982: `auth renew` 4 passed incl. stale→readable and /about) · previous: [LIVE_VERIFICATION_v0.85.0](LIVE_VERIFICATION_v0.85.0.md) (**2026-10-14, 0 credits.** #723/#979: `@Character` on flow.google.com images — 4-scenario e2e (CLI t2i, MCP, i2i + character, id-only refusal) passed on the release tree; #975: multi-prompt `t2i --project-name` — e2e passed) · previous: [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.89.1 → gflow_cli-0.90.0}/docs/LIVE_VERIFICATION_v0.89.1.md

@@ -79,5 +79,8 @@ release did not change).
 
 ## Post-tag evidence
 
-Filled after publish: the `Release` workflow run, the PyPI version, and `gflow --version` from a
-fresh install.
+- `Release` workflow run `40075047500` on tag `v0.89.1`: **success**.
+- GitHub Release `v0.89.1` published 2026-10-24T07:41:07Z (not a draft, not a prerelease).
+- PyPI: `pip index versions gflow-cli` → `gflow-cli (0.89.1)`.
+- Fresh install: `uvx --refresh --from "gflow-cli==0.89.1" gflow --version` → `gflow, version 0.89.1`.
+- Release PR #1081 merged into `main` with a merge commit; `main` back-merged into `develop`.

gflow_cli-0.90.0/docs/LIVE_VERIFICATION_v0.90.0.md

@@ -0,0 +1,78 @@
+# Live verification — v0.90.0
+
+> Evidence for this release, gathered on 2026-10-24 and 2026-10-25 (PRs #1084–#1098). Every
+> row below was 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, 50 Veo credits) for the release run; `ffroliva` for the 2026-10-24 PR runs |
+| Host Flow served | `flow.google.com`, classic composer |
+| Transport | `ui_automation` → migrated composer |
+| OS | Windows 11 (Google Chrome installed) |
+| Tree | release branch `chore/release-v0.90.0`, cut from `develop@293b4e6c` |
+| Veo credits spent | none in the release run; one `veo-lite` clip on the #941 PR run (2026-10-24). Image daily quota: about 11 images in the release run, about 15 across today's PR runs |
+
+## Release e2e on the release tree
+
+`-m e2e` on `denon82`, project `fd75972d-…`, one pytest process per file:
+**15 passed, 0 skipped, 0 failed.**
+
+| File | Result |
+|---|---|
+| `test_standalone_window_position_e2e.py` | 2 passed (11 s) |
+| `test_incident_quality_e2e.py::test_a_failed_generation_bundle_is_not_hollow` | 1 passed (41 s) |
+| `test_migrated_selector_drift_e2e.py` | 1 passed (9 s) |
+| `test_insufficient_credits_e2e.py` (denon82 at 50 credits, `veo-quality` costs 100) | 1 passed (10 s) |
+| `test_auth_verification_e2e.py` | 4 passed (23 s) |
+| `test_image_download_failure_records_bdd.py` | 2 passed (75 s) |
+| `test_local_ref_uploaded_once_bdd.py` | 3 passed (397 s) |
+| `test_run_resume_e2e.py` | 1 passed (106 s) |
+
+## Summary
+
+| Change | Surface | Verified live? | Cost |
+|---|---|---|---|
+| `gflow run --resume` (#934) | `gflow run` (CLI only, by design) | ✅ `test_run_resume_e2e.py`: only the missing child row is submitted. 1/1 on the PR (#1087) and 1/1 on the release tree | 3 images |
+| A local `--ref` is uploaded into a project once (#772) | `image i2i`, MCP `gflow_generate_image` (worker) | ✅ `test_local_ref_uploaded_once_bdd.py`, three scenarios. CLI: the second run emits `reference_uploads.reused` with the first upload's id, attaches exactly that id in place, and **no** upload event fires. MCP twin: the same. A recorded image the project no longer holds: the in-place search misses, the file is uploaded once more, the new copy is recorded, and the submit guard passes. 3/3 on the PR branch, 3/3 on the release tree | 6 images |
+| An unwritable output folder is exit 11 (#1091) | image downloads (CLI + MCP) | ✅ `test_image_download_failure_records_bdd.py`: exit 11, "Configuration error: Could not write the output file", no "Unexpected error", no path in the message, media id kept. 2/2 on the PR and on the release tree | 2 images |
+| A corrupt cookie store is not a network problem (#796, part) | `auth status`, MCP `gflow_auth_status` | ✅ on the PR (#1096): a copy of denon82's profile with its `Cookies` file overwritten. develop said "Check network connectivity" (MCP 503, retryable); the branch says the cookie store is corrupt and to close Chrome and log in again (MCP 409, not retryable), 2/2. No browser launched. Regression on the release tree: `test_auth_verification_e2e.py` 4/4 | $0 |
+| MCP `wait` described in `tools/list` (#481) | MCP schema | ✅ on the PR (#1095): real `gflow mcp run` over stdio, isolated home. `tools/list` shows the description on both generation tools, and a `wait=false` call stayed pending while `tasks/get` answered `working` (the gap now filed as #1097) | $0 |
+| `movie.toml` entity + `variants` refused (#724) | manifest parsing | ✅ on the PR (#1094): `gflow movie run` on a sample manifest exits 11 with the fix in the message, before any browser starts. No Flow surface | $0 |
+| Credit shortfall recognised in every UI language (#745) | migrated submit, exit 37 | ✅ `test_insufficient_credits_e2e.py` 1/1 on the PR (#1088) and on the release tree (denon82 cannot afford `veo-quality`) | $0 |
+| Selector drift watched on flow.google.com (#1083) | selector registry, canary | ✅ `test_migrated_selector_drift_e2e.py` 1/1 on the PR (#1086) and on the release tree ("0 need attention") | $0 |
+| Chip-count refusal states its numbers (#745 item 9) | refusal message | out of scope: message change at an existing raise site; offline | $0 |
+| A signed URL that answers an HTTP error is exit 6 (#941, part 2) | video download, `data download` | ✅ `test_signed_url_http_error_e2e.py` (a hook forces a 403) 1/1 on the PR (#1084, 2026-10-24). Not re-run on the release tree: it spends Veo credits and no file it covers changed since | 1 `veo-lite` clip |
+| Canary: two stale tests re-armed (#559, PR #1093) | e2e suite | ✅ both files on the PR and on the release tree (rows 1–2 above) | $0 |
+
+## Not verified
+
+- **#796's remaining half** (marker rollback after a `GOOGLE_SESSION_ONLY` login): not in this
+  release; the issue stays open.
+- **That a fresh login repairs a corrupt cookie database** (#796's new advice): not run. The
+  login hint names the fallback (delete `Default/Network/Cookies`) for when it does not.
+- **#1097 (`wait=false` never runs)**: documented, not fixed; filed for the next cycle.
+- **#772 on labs**: blocker, every profile here is served flow.google.com (labs answers 308).
+
+## Observed, not changed
+
+- The #772 e2e first skipped silently: its events are INFO, which the default log level hides
+  since #1041, and the host check read "no migrated events" as labs. The test now raises the
+  child's log level and skips only on positive evidence of labs. The older
+  `test_earlier_run_ref_in_place_bdd.py` reads INFO events the same way and was not re-run
+  here.
+- The canary had gone RED on two `$0` tests that a deliberate fix (#974) and a Windows change
+  (the -30000 window offset is no longer clamped) had made stale; PR #1093 re-armed both.
+
+## Pre-tag gates
+
+- `/gflow:check` on the release tree: the five `scripts/ci` gates, ruff, format and
+  `pyright src` all green; `pytest -n 8 --cov` **5499 passed, 29 skipped**, coverage 93%.
+- `scripts/ci/check_release_artifacts.py`: OK.
+- `/gflow:doc-review`: mechanical pass (sections 1–7) clean, apart from findings that predate this release (old ledgers not listed in INDEX). Council: completeness YELLOW, drift YELLOW, cross-reference RED (the `website/docs/` mirror lagged the release-prep edits; regenerated). 14 findings: the release-blocking ones fixed in the release-prep commit (USAGE still said an OS-refused write is exit 1; the `gflow_auth_status` tool description still named a daemon; the stale mirror), plus the Tier 2 gaps (exit-11 and exit-37 rows, `auth status` cookie-store shape, MCP `reference_images` reuse and #1091, `--resume` in the agent skill, #772 host scope, an MCP.md self-contradiction about `profile_marker_missing`). Reports at `tmp/council/0{1,2,3}-*.md` (local only).
+
+## Post-tag evidence
+
+To be filled after the tag's `Release` workflow publishes to PyPI.