gflow-cli 0.41.0__tar.gz → 0.43.0__tar.gz

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/.claude/commands/gflow/llm-council.md

@@ -1,10 +1,10 @@
 ---
-description: Run pr-council-review (PR or branch mode) plus an external-tools corroboration layer (codex, gemini, opt-in agy) for high-stakes reviews where a same-model-family blind spot is a real risk. Tiers: small (internal only, default) / medium (+codex) / high (+codex+gemini). Wrapper around skills/llm-council/SKILL.md.
+description: Run pr-council-review (PR or branch mode) plus an external-tools corroboration layer (codex, plus Antigravity via the agy harness) for high-stakes reviews where a same-model-family blind spot is a real risk. Tiers: small (internal only, default) / medium (+codex) / high (+codex+antigravity). Wrapper around skills/llm-council/SKILL.md.
 ---
 
-# `/gflow:llm-council [PR# | --base <ref>] [--tier small|medium|high] [--include-agy]`
+# `/gflow:llm-council [PR# | --base <ref>] [--tier small|medium|high]`
 
-**Read `skills/llm-council/SKILL.md` and follow its protocol now**, treating `$ARGUMENTS` as: the PR number or `--base <ref>` (branch mode, same as `/gflow:pr-council-review` / `/gflow:branch-review`), plus `--tier <small|medium|high>` (default `small`) and the optional `--include-agy` flag.
+**Read `skills/llm-council/SKILL.md` and follow its protocol now**, treating `$ARGUMENTS` as: the PR number or `--base <ref>` (branch mode, same as `/gflow:pr-council-review` / `/gflow:branch-review`), plus `--tier <small|medium|high>` (default `small`). The `high` tier adds Antigravity (`agy`) alongside `codex`.
 
 > Do **not** call `Skill(skill="llm-council")` or `Skill(skill="pr-council-review")` — the repo's `skills/*/SKILL.md` files are plain Markdown, not registered as Skill-tool-invocable (only `.claude/commands/gflow/*` are). Invoking either errors with `Unknown skill: ...`. Read the files directly instead.
 

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/.env.template

@@ -160,9 +160,18 @@
 # GFLOW_CLI_PROJECT_NAME=
 
 # -----------------------------------------------------------------------------
-# Debugging (opt-in only — both can expose secrets, see docs/CONFIGURATION.md)
+# Debugging (see docs/CONFIGURATION.md; HAR/traceback are opt-in and can
+# expose secrets)
 # -----------------------------------------------------------------------------
 
+# Automatic private incident bundles (DEFAULT: true). On relevant operational
+# failures (Flow app crash, UI drift, transport timeout, WAF/network errors,
+# profile-lock contention) gflow writes a bounded diagnostic bundle under
+# <GFLOW_CLI_HOME>/incidents/. Automatic JSON is allowlisted structural
+# metadata only; screenshots live under sensitive/ and must be reviewed
+# before sharing. Nothing is ever uploaded. Set false to disable.
+# GFLOW_CLI_INCIDENT_CAPTURE=true
+
 # Captures full Playwright network traffic (requests, responses, headers,
 # cookies) to this HAR file for the session. SECURITY: a HAR file contains
 # live auth cookies and bearer tokens -- never share one publicly.

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/.github/workflows/ci.yml

@@ -63,6 +63,12 @@ jobs:
       - name: Documentation links
         run: uv run python scripts/ci/check_doc_links.py
 
+      - name: Website docs PII guard (no private identifiers in the published mirror)
+        run: uv run python scripts/ci/check_website_docs_pii.py
+
+      - name: Website docs mirror in sync (regenerate-and-diff)
+        run: uv run python scripts/ci/generate_website_docs.py --check
+
       - name: Lint
         run: uv run ruff check src tests
 

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/AGENTS.md

@@ -2,7 +2,7 @@
 
 > Universal entry point for AI coding agents. Read this first; everything else routes from here.
 
-Supported tools that auto-discover this file: Cursor, Codex, Aider, Jules, Devin, Windsurf, Zed, Warp, opencode, RooCode, Amp, Junie, Phoenix, GitHub Copilot, VS Code, Factory, Augment, Semgrep, Kilo Code, UiPath. Gemini CLI reads [GEMINI.md](GEMINI.md) and Claude Code reads [CLAUDE.md](CLAUDE.md), both of which cross-reference this file.
+Supported tools that auto-discover this file: Cursor, Codex, Aider, Antigravity (`agy`), Jules, Devin, Windsurf, Zed, Warp, opencode, RooCode, Amp, Junie, Phoenix, GitHub Copilot, VS Code, Factory, Augment, Semgrep, Kilo Code, UiPath. Claude Code reads [CLAUDE.md](CLAUDE.md), which cross-references this file.
 
 ## Project at a glance
 
@@ -39,6 +39,7 @@ Run these gates in order before every commit:
 $env:PYTHONUTF8=1
 uv run python scripts/ci/check_repo_hygiene.py
 uv run python scripts/ci/check_doc_links.py
+uv run python scripts/ci/check_website_docs_pii.py
 uv run ruff check src tests
 uv run ruff format --check src tests
 uv run pyright src
@@ -92,7 +93,7 @@ The `skills/` directory ships installable agent skill docs in plain Markdown wit
 | `plan` | [`skills/plan/SKILL.md`](skills/plan/SKILL.md) | Create a structured task-by-task implementation plan for a feature |
 | `status` | [`skills/status/SKILL.md`](skills/status/SKILL.md) | Show current plan state, progress, and next unchecked task |
 | `pr-council-review` | [`skills/pr-council-review/SKILL.md`](skills/pr-council-review/SKILL.md) | Multi-dimensional PR council review |
-| `llm-council` | [`skills/llm-council/SKILL.md`](skills/llm-council/SKILL.md) | Wraps `pr-council-review` with external CLI reviewers (`codex`/`gemini`, opt-in `agy`) for high-stakes reviews |
+| `llm-council` | [`skills/llm-council/SKILL.md`](skills/llm-council/SKILL.md) | Wraps `pr-council-review` with external CLI reviewers (`codex` + Antigravity `agy`) for high-stakes reviews |
 | `issue-assessment` | [`skills/issue-assessment/SKILL.md`](skills/issue-assessment/SKILL.md) | Triage a GitHub issue (read-only) before any fix work |
 | `issue-resolve` | [`skills/issue-resolve/SKILL.md`](skills/issue-resolve/SKILL.md) | Drive an assessed issue to a test-first fix + draft PR |
 | `check` | [`skills/check/SKILL.md`](skills/check/SKILL.md) | Quality gates (lint/format/types/tests) before every commit |
@@ -108,7 +109,7 @@ and must be resolvable by ANY agent via this file. Vendor directories hold thin
 only (`.claude/commands/gflow/*.md` are pointers into `skills/`); never put protocol
 content in a vendor directory.
 
-**Cursor / Aider / Codex / Gemini CLI (`agy`):** paste or include the relevant `SKILL.md` in your system context. Note: in the `agy` TUI prompt, custom slash commands (e.g. `/gflow:pr-council-review`) are blocked by the TUI's command parser. Type them as plain text without the leading slash (e.g. `gflow:pr-council-review`, `gflow:branch-review`, or `gflow:check`) to trigger the corresponding agent skill workflow.
+**Cursor / Aider / Codex / Antigravity (`agy`):** paste or include the relevant `SKILL.md` in your system context. Note: in the `agy` TUI prompt, custom slash commands (e.g. `/gflow:pr-council-review`) are blocked by the TUI's command parser. Type them as plain text without the leading slash (e.g. `gflow:pr-council-review`, `gflow:branch-review`, or `gflow:check`) to trigger the corresponding agent skill workflow.
 **Claude Code:** the `/gflow:` slash commands in `.claude/commands/gflow/` are auto-discovered when the project is open — no extra setup needed. To register a skill globally, copy the command file to `~/.claude/commands/`.
 **Custom agents:** fetch `skills/gflow-cli/SKILL.md` into your knowledge base before answering gflow questions.
 

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/CHANGELOG.md

@@ -7,6 +7,169 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.43.0] — 2026-07-23
+
+### Added
+
+- **Private incident diagnostics** (`GFLOW_CLI_INCIDENT_CAPTURE`, default
+  **on**). Relevant operational failures — Flow app crashes, agentic-cohort /
+  UI-mode errors, selector drift, transport timeouts, WAF/network/wire-format
+  errors, profile-lock contention, unexpected exceptions — now automatically
+  write a bounded, **private** incident bundle under
+  `<GFLOW_CLI_HOME>/incidents/`: an allowlisted `manifest.json`, structural
+  `ui.json` (ligatures/signals/overlay geometry — never raw text),
+  `network.json` + `browser.json` ring journals (host categories, canonical
+  routes, status codes, text lengths — never prompts/tokens/cookies/bodies/
+  signed URLs), and a `sensitive/screenshot.png` for UI-state failures that
+  every surface marks review-before-sharing. Nothing is ever uploaded; remote
+  MCP/HTTP/worker error envelopes carry only an opaque `{id, capture_status}`
+  while the local CLI prints the bundle path. Retention is bounded
+  (50 bundles / 250 MiB) and validates ownership before pruning. Raw HAR
+  stays separate and opt-in; the manifest's `har_state` now reports honestly
+  whether the session's HAR demonstrably finalized. See
+  [DEBUGGING § Automatic incident bundles](docs/DEBUGGING.md#automatic-incident-bundles).
+  Refs #369, #370, #174, #183.
+- **Profile-lock owner evidence.** `ProfileLockedError` contention now
+  surfaces the recorded lease owner's PID and observed start time locally
+  (never in remote envelopes or logs; identities are per-command HMACs, never
+  the raw owner token). The lock-file layout is v1-versioned: byte 0 is the
+  kernel-locked sentinel and metadata starts at offset 1, so Windows
+  contenders can read it while the lock is held (legacy byte-0 files degrade
+  to "evidence unavailable"). The kernel lock remains authoritative — no
+  reclaim, unlink, or PID kill is ever performed from metadata. Refs #370.
+- **UI-drift debug engine** (`capture_ui_diagnostics`). On a `mode_switch_trigger`
+  failure, gflow dumps the composer's **structural** DOM signature — the
+  Material-Symbols ligature inventory, `crop_*` presence, textbox count, and
+  bounded overlay geometry — to a JSON alongside a **full-page** screenshot,
+  so a Flow frontend change is diagnosable from one artifact instead of a
+  bare (often black) viewport shot. Consolidated onto the incident-bundle
+  engine: the earlier in-development raw URL/title/body-text fields were
+  removed before release. (#183)
+- **`website/docs/` PII-leak CI guard** (`scripts/ci/check_website_docs_pii.py`).
+  The published mkdocs mirror under `website/docs/` is an anonymized copy of
+  canonical `docs/`; this new gate fails CI (and runs in `/gflow:check`) if a
+  known private identifier — `denon82`, the OS username `ffrol`, a real
+  name/email — appears in a published file, catching an anonymization miss
+  before it ships (the failure mode of #362). Public references such as
+  `github.com/ffroliva/gflow-cli` and the APP_AUTHOR path are trap-free by
+  construction, so the guard needs no allow-list.
+
+### Fixed
+
+- **Incident-capture hardening from the max-effort review** (14 confirmed
+  findings fixed pre-release): journals now stage first and page artifacts
+  share the 8s budget via a deadline, so a fully wedged renderer can no longer
+  cost the whole bundle or bypass suppression; the legacy mode-switch debug
+  dump writes structural JSON only (the unmarked full-page screenshot that
+  previously landed in the plain output dir on every ordinary run is gone —
+  the bundle's `sensitive/` screenshot is the one imagery artifact); capture
+  now also covers `generate_character_image` (which additionally gains the
+  exit-15 closed-browser mapping) and `upsample_image`, plus the common
+  stale-Chrome launch-crash contention path (#293); manifests report
+  `har_state: complete` only when the context demonstrably closed gracefully;
+  bundles staged for unexpected non-typed exceptions are now surfaced (path in
+  human output and `--json`); retention runs even when capture is disabled
+  (an opt-out no longer freezes previously captured bundles on disk), runs off
+  the event loop, and an undeletable pending bundle can no longer condemn
+  healthy ones; a Windows sharing violation during manifest finalization gets
+  a bounded retry; `browser.json` records the real JS error class
+  (`TypeError`/`ReferenceError`) instead of the constant `Error`; worker
+  daemon tasks rebind a per-task correlation id so incident ids are unique
+  and joinable to queue rows.
+- **`FlowAppError` and `FlowAgentUiError` now report `retryable: true` on
+  every machine-readable surface.** Both are documented (and presented to
+  humans) as transient/retryable, but the CLI `--json` payload said
+  `retryable: false` and the MCP / worker-queue error envelopes carried no
+  retry signal at all. The classification now lives in one shared
+  `errors.is_retryable()` consumed by CLI JSON, MCP tool envelopes, and
+  persisted worker-queue error payloads — the three surfaces can no longer
+  drift.
+- **Documentation drift corrected against the code:** `gflow image batch` docs
+  claimed generations run in parallel inside Flow (the transport is strictly
+  serial — each prompt's generation is awaited before the next submission)
+  and listed `--fail-fast` as the default (the CLI default is
+  `--continue-on-error`); the root plan still labeled the MCP server as
+  unshipped (shipped v0.21.0/v0.23.0).
+- **Flow's new media-library / agentic A/B cohort now fails cleanly.** When a
+  project opens into Flow's full-page media-library (or agentic chat) composer —
+  which has no classic `crop_*` aspect/mode control — `gflow image` and
+  `gflow video` now raise a clear, retryable `FlowAgentUiError` ("this cohort
+  flaps; retry shortly") instead of the misleading `UiSelectorDriftError`
+  "file a bug". Detection is a runtime DOM scan at a new shared
+  `_mode_switch_error` raise site covering **both** the image and video paths.
+  Refs #174, #183.
+- **Flow web-app crashes now fail cleanly instead of "file a bug".** When Flow's
+  web app renders its client-side-exception error boundary (a transient Flow
+  crash) instead of the editor, the mode-switch raise site now raises a retryable
+  `FlowAppError` (exit code 31) — "transient Flow error, retry shortly" — rather
+  than the misleading `UiSelectorDriftError`. Detected via the Flow error-page
+  title; surfaced by the #183 UI-drift debug engine.
+- **Experimental transport self-lockout.** The `bearer` and `sapisidhash`
+  transports discard a caller-supplied Playwright page and re-acquire the profile
+  `ProfileLease` in their own `setup()`. Driving one via `GFLOW_CLI_TRANSPORT`
+  inside a `FlowApiClient` (which already holds the lease) self-locked with an
+  opaque `ProfileLockedError`. `FlowApiClient` now refuses these standalone-only
+  transports up front with a clear `ConfigurationError` naming the transport and
+  pointing to `ui_automation`/`evaluate_fetch` or standalone use. `evaluate_fetch`
+  is unaffected (it shares the client's page). New `STANDALONE_ONLY_TRANSPORTS`
+  set + `resolve_transport_name()` helper in `api/transports`.
+
+## [0.42.0] — 2026-07-21
+
+### Fixed
+
+- Content-safety `400` responses from Flow are now classified as
+  `ContentPolicyError` (exit code 5) instead of the misleading `WireFormatError`,
+  so callers can branch on a policy rejection deterministically. (#359)
+- Corrected a false `flow_operation_id` invariant. Live verification found
+  `veo-lite` can produce a `remote_started` checkpoint with `operation_id` unset,
+  contradicting the prior claim that only `omni-flash` omits the operation name.
+  `flow_operation_id` is best-effort/optional; `media_id` is the canonical handle
+  used by polling, download, and every CLI lookup. No behaviour change; a
+  regression test now locks the operation-name parser against the real veo
+  capture fixture. (#361)
+
+### Changed
+
+- **Replaced Gemini CLI with Antigravity (`agy`) as the supported Google coding
+  agent** across skills and docs (Google retired Gemini CLI in favor of the
+  Antigravity harness). Antigravity auto-discovers `AGENTS.md` natively, so the
+  dedicated `GEMINI.md` hub is **removed** and Antigravity is listed among the
+  auto-discovering tools in `AGENTS.md`. (#360)
+- **`llm-council` skill:** the `high` tier's second external reviewer is now
+  Antigravity (`agy`) instead of Gemini CLI; `agy` is promoted from an opt-in
+  tool to the pinned `high`-tier slot and the `--include-agy` flag is dropped.
+  When `agy` is unavailable or fails non-interactively, the skill suggests
+  installing Antigravity or substituting another external CLI coding agent rather
+  than failing. (#360)
+- Forward-looking agent references updated for consistency across `AGENTS.md`,
+  `CLAUDE.md`, `README.md`, `llms.txt`, `docs/INDEX.md`, `docs/AGENT_GUIDE.md`,
+  `skills/*`, and CI helper strings. Historical release notes and past
+  verification records are left unchanged. (#360)
+
+### Removed
+
+- Removed the dead `fail_processing_tasks` daemon-recovery method, superseded by
+  the checkpoint-classifying `recover_processing` (internal cleanup; no
+  user-facing behaviour change). (#361)
+
+### Documentation
+
+- Added an onboarding page and quickstart flow to the published docs site, and
+  anonymized personal account data across it. Security vulnerabilities now report
+  through GitHub's private vulnerability reporting rather than a personal email. (#362)
+- Corrected the same-profile concurrency framing (MCP page and docs) to the
+  cross-process `ProfileLease` fail-fast contract (`ProfileLockedError`, exit 11),
+  and recorded that the POSIX `fcntl.flock` lease was verified green on the
+  Windows/macOS/Linux CI matrix. (#361)
+
+### Tests
+
+- Added live-gated end-to-end tests for crash-recovery (a crashed post-submit task
+  recovers as `indeterminate` and is never resubmitted) and cancellation-safe
+  teardown (the profile lease releases on mid-launch cancel). Both were confirmed
+  against real Flow on 2026-07-21. (#361)
+
 ## [0.41.0] — 2026-07-20
 
 ### Added
@@ -2169,7 +2332,9 @@ shell-script template that branches on these codes.
 
 First skeleton. Not functional end-to-end yet.
 
-[Unreleased]: https://github.com/ffroliva/gflow-cli/compare/v0.41.0...HEAD
+[Unreleased]: https://github.com/ffroliva/gflow-cli/compare/v0.43.0...HEAD
+[0.43.0]: https://github.com/ffroliva/gflow-cli/compare/v0.42.0...v0.43.0
+[0.42.0]: https://github.com/ffroliva/gflow-cli/compare/v0.41.0...v0.42.0
 [0.41.0]: https://github.com/ffroliva/gflow-cli/compare/v0.40.0...v0.41.0
 [0.40.0]: https://github.com/ffroliva/gflow-cli/compare/v0.39.0...v0.40.0
 [0.39.0]: https://github.com/ffroliva/gflow-cli/compare/v0.38.1...v0.39.0

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/CLAUDE.md

@@ -1,6 +1,6 @@
 # CLAUDE.md
 
-> Project memory hub for **Claude Code**. The universal coding-agent rules for any tool (Cursor, Codex, Aider, Gemini CLI, etc.) live in [AGENTS.md](AGENTS.md) — this file carries Claude-Code-specific session protocol only.
+> Project memory hub for **Claude Code**. The universal coding-agent rules for any tool (Cursor, Codex, Aider, Antigravity, etc.) live in [AGENTS.md](AGENTS.md) — this file carries Claude-Code-specific session protocol only.
 
 ## What this project is
 

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/KNOWN_ISSUES.md

@@ -14,6 +14,56 @@ Living list of behaviour that's broken, surprising, or limited by design — alo
 
 ## Open
 
+### One-time Flow banner/modal can cover the composer on first load
+
+- **Status:** Open ([#369](https://github.com/ffroliva/gflow-cli/issues/369))
+- **Severity:** Low (transient) · **Affected:** any UI-automation command on a profile that hasn't seen the banner yet
+
+A Flow-side one-time announcement banner/modal can overlay the composer and
+make the mode-switch / settings probes miss. It shows once per
+profile+cookie state, so it is gone on re-run and cannot be reproduced on
+demand. gflow does **not** guess a dismiss selector for unknown overlays
+(clicking unknown UI is riskier than failing). Since v0.43.0 the automatic
+incident bundle records the overlay's bounded geometry, `role`,
+`aria-modal`, `z-index`, `pointer-events`, and inner Material-Symbol
+ligatures (no raw text) plus a `sensitive/` screenshot — enough to write a
+targeted dismissal once the next occurrence is captured. **Workaround:**
+re-run the command; open the project once manually in Chrome to consume the
+banner.
+
+### Reported stale profile lock blocks acquisition (unreproduced)
+
+- **Status:** Open ([#370](https://github.com/ffroliva/gflow-cli/issues/370))
+- **Severity:** Medium (blocks the profile until resolved) · **Affected:** `ProfileLease` acquisition (exit 11)
+
+A user report of `ProfileLockedError` with no apparently-live owner. Not
+reproduced: in every observed case the kernel advisory lock was held by a
+real process (e.g. a pytest child that outlived its parent shell). The
+kernel lock is authoritative — a merely *stale metadata file* cannot block
+acquisition, and gflow will never auto-delete a lock file or kill a
+recorded PID based on metadata. Since v0.43.0, contention reports the
+recorded owner's PID and observed start time locally (lock-file metadata
+now starts at offset 1 so Windows contenders can read it while byte 0 is
+kernel-locked), and a metadata-only incident bundle is written before any
+Chrome launch. **Workaround:** find and close the owning process (the
+error's local output names its PID), or use a different `--profile`.
+
+### Unexplained image-generation HTTP 400 (observed live 2026-07-22)
+
+- **Status:** Open (no issue yet — evidence-gathering)
+- **Severity:** Low (single occurrence) · **Affected:** `image t2i` wire path
+
+One live `batchGenerateImages` call returned an HTTP 400 that was neither a
+content-safety rejection nor a known wire shape; the retry succeeded. Root
+cause unidentified and **not** claimed fixed by v0.43.0. A 400 that resolves
+on retry writes **no** incident bundle (successful commands capture nothing).
+The diagnostics help only when such a 400 *terminates* the command as a
+captured failure (e.g. a `WireFormatError`): its incident bundle's
+`network.json` then carries allowlisted discovery evidence for the failed
+request (numeric error code, status enum, known-key booleans, unknown-key
+count, message length — never the raw body), which is the evidence this entry
+is waiting on. **Workaround:** retry; the failure has not recurred.
+
 ### Flow's `uploadImage` endpoint rejects some JPEGs with HTTP 400 (metadata-sensitive)
 
 - **Status:** Open ([#287](https://github.com/ffroliva/gflow-cli/issues/287))
@@ -109,6 +159,17 @@ reaches the submit** — the request carries no `referenceEntities`, so the
 submit backstops raise `WireFormatError` (**exit 7**) instead of silently
 returning a text-only generation as success.
 
+**Plain generation on this cohort now fails cleanly (#183).** When a project
+opens into this full-page library (or the agentic chat composer) there is no
+classic `crop_*` aspect/mode control, so `gflow image`/`gflow video` can't drive
+generation. Rather than the old opaque `UiSelectorDriftError` "file a bug", the
+mode-switch raise site now runs a runtime DOM scan and raises a clear, **retryable**
+`FlowAgentUiError` (**exit 25**, "this cohort flaps; retry shortly"), and dumps a
+DOM-signature diagnostics artifact (`diag_mode_switch_miss.json` + a full-page
+screenshot) for reporting. The cohort is server-assigned per page load and flaps
+within ~12h, so a re-run often lands the classic UI. Driving the new UI directly
+is still out of scope.
+
 **How to tell which UI your account has:** in the Flow web editor, click
 **Add Media** — a small dialog means the old (working) UI; a navigation to a
 full-page library means the affected new UI.
@@ -352,6 +413,8 @@ The worker queue (`generation_queue`, used by the `gflow serve` daemon and MCP t
 
 **Why this can't be resolved automatically today:** Flow's generation-status REST endpoint rejects a bare, cookie-only `page.request` re-check with HTTP 401 — only a live, authenticated Playwright SPA re-poll (opening the project page and reading the DOM) can turn a preserved handle back into a real status, and that live re-poll path is not wired into recovery yet (tracked for a future phase; see the C1 handle-spike notes in `docs/superpowers/specs/2026-07-19-production-readiness-hardening-design.md` Appendix A).
 
+**Decision (2026-07-21):** keep the safe stub — `recover_processing` marks post-submit interruptions `indeterminate` and never auto-resubmits, which is already correct. Building the auto-reconciler is deferred until **F1** (credit-free project-page re-entry) is confirmed against live Flow; until then a blind reconciler would be speculative code against unverified blackbox behavior. The `client` reconcile-hook seam and the live-gated `tests/e2e/test_crash_recovery_e2e.py` are already in place for when F1 lands.
+
 **Manual reconciliation:** an `indeterminate` row's checkpoint retains whatever handle/project info was captured before interruption. To resolve one by hand: open the relevant Flow project in the browser and check whether the expected asset appears.
 - **Found** — the generation completed; no action needed (the credit was spent as intended, just not auto-recorded locally).
 - **Not found after a few minutes** — it likely never completed; safe to resubmit the same prompt manually.
@@ -585,31 +648,37 @@ one of the 14 supported locales or in English.
 
 ---
 
-### `omni-flash` t2v response omits operation name — `flow_operation_id` persists NULL
+### t2v response can omit operation name — `flow_operation_id` persists NULL
 
 - **Status:** Open · **Severity:** Low · **Affects:** v0.9.0+ (data layer)
 
 The data layer's `on_started` callback captures
 `operations[0].operation.name` from each `batchAsyncGenerateVideoText`
-response and persists it as `operations.flow_operation_id`. The
-`omni-flash` model's response shape does not carry that field, so
-omni-flash rows end up with `flow_operation_id` NULL while `veo-*` rows
-carry the expected `operations/...` identifier. The rest of the row
-(prompt, model, aspect, started/completed timestamps, batch ID, output
-paths) is recorded normally.
-
-**Impact:** cosmetic for now — `gflow data media <id>` and provenance
-lookup by Flow media ID still work. Any future feature that joins on
-`flow_operation_id` (none in the current CLI) would miss omni-flash
-rows.
+response and persists it as `operations.flow_operation_id`. This field
+is **best-effort, not guaranteed for any model**: `omni-flash`'s response
+shape does not carry it, so omni-flash rows end up with
+`flow_operation_id` NULL. **Update 2026-07-21 (live):** the same NULL
+was observed on a live `veo-lite` t2v run (`remote_started` checkpoint
+with `operation_id=None`), on an agentic-UI-cohort account — so `veo-*`
+is not a reliable guarantee either; the original claim that veo-* rows
+always carry the operation name was false. The rest of the row (prompt,
+model, aspect, started/completed timestamps, batch ID, output paths) is
+recorded normally regardless.
+
+**Impact:** cosmetic/provenance-only — `media_id` is the canonical
+handle (poll, download, and every CLI lookup use it, not
+`flow_operation_id`). `gflow data media <id>` and provenance lookup by
+Flow media ID still work. Nothing in the current CLI queries by
+`flow_operation_id`; a future feature that did would miss rows on any
+model whose response omits the operation name.
 
 **Workaround:** none needed if you don't query by `flow_operation_id`.
 
-**Roadmap:** capture an `omni-flash` `batchAsyncGenerateVideoText`
-response sample, identify the equivalent provenance handle (if any), and
-either map it into `flow_operation_id` or document that omni-flash
-legitimately has no such identifier. Track via a follow-up issue once a
-sample is captured.
+**Roadmap:** capture response samples across models (including veo-lite)
+where the operation name is absent, identify the equivalent provenance
+handle (if any), and either map it into `flow_operation_id` or document
+that these cases legitimately have no such identifier. Track via a
+follow-up issue once samples are captured.
 
 ---
 

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: gflow-cli
-Version: 0.41.0
+Version: 0.43.0
 Summary: Unofficial CLI for Google Flow — drive Veo image-to-video generations from the terminal.
 Project-URL: Homepage, https://github.com/ffroliva/gflow-cli
 Project-URL: Issues, https://github.com/ffroliva/gflow-cli/issues
@@ -161,7 +161,7 @@ gflow-cli ships four agent entry points. Pick the one your tool reads first.
 
 | File | Audience | Tools |
 |---|---|---|
-| [**AGENTS.md**](AGENTS.md) | Universal coding-agent spec | Cursor · Codex · Aider · Gemini CLI · Jules · Devin · Windsurf · Zed · Warp · opencode · Copilot |
+| [**AGENTS.md**](AGENTS.md) | Universal coding-agent spec | Cursor · Codex · Aider · Antigravity · Jules · Devin · Windsurf · Zed · Warp · opencode · Copilot |
 | [**CLAUDE.md**](CLAUDE.md) | Claude Code's auto-loaded memory | Claude Code |
 | [**llms.txt**](llms.txt) | LLM-readable summary (llmstxt.org format) | Paste into ChatGPT, Claude, or Gemini to onboard the model |
 | [`skills/gflow-cli/SKILL.md`](skills/gflow-cli/SKILL.md) | Claude Code Skill | Symlink into `~/.claude/skills/` |

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/PLAN.md

@@ -358,7 +358,7 @@ The video-generation feature has its own sub-phase plan (spike → Phase A → P
   - **Phase 3 (PR #90 / [#63](https://github.com/ffroliva/gflow-cli/issues/63), 2026-05-26, develop `9a0896a8`):** replaced `FRAME_SLOTS_STRUCT` with the locale-free pattern `div[type='button'][aria-haspopup='dialog']` (verified via DOM probe — matches exactly 2). Also fixed the End-frame OOB index after Start is attached. **I2V live-proof on de-DE: 124 s, mp4 with `ftyp` magic bytes, both `frame_attached` events fired (Start + End).**
   - **Phase 4 (Task #6, 2026-05-26, branch `claude/next-quick-win-gBPqS`, PR #93):** `NEW_PROJECT_SELECTORS` expanded to all 14 locales (icon-first tier + 14-locale text tier); English-only ARIA fallbacks (`[aria-label*='New project']`, `[aria-label*='Project']`) removed. `SUBMIT_BUTTON_SELECTORS` drops its English-only `button[aria-label*="Create"]` entry — `arrow_forward` icon selectors cover it in all locales. Both tuples are now fully locale-invariant. Note: issue #24 was closed 2026-05-24 after Phases 1–3; Phase 4 is cosmetic tail work. `--lang=en-US` retained only to stabilise `IMAGE_MODEL_OPTION_SELECTORS` (product names like "Nano Banana 2" may be localised). Removing it requires converting the image model picker to a structural anchor — tracked as issue #94 (Phase 5 below). **R2V live e2e on non-EN not yet exercised** — still open.
   - **Phase 5 (2026-05-30, branch `claude/issue-94-staleness-check-MnsEY`, PR #127):** `IMAGE_MODEL_OPTION_SELECTORS` and `VIDEO_MODEL_OPTION_SELECTORS` converted from `dict[Model, str]` to `dict[Model, tuple[str, ...]]` (cascade discipline; Tier 1 structural slots reserved for future DOM-probe-confirmed anchors). `--lang=en-US` removed from Chromium launch args — locale controlled by `locale=locale_env` Playwright kwarg (persists across all navigations including `/project/<uuid>` deep-links) + `FLOW_URL`'s `?hl=en` on initial load. Branded model names confirmed locale-stable. Four new `TestSelectorLocaleInvariance` tests + four `TestSelectImageModel` runtime tests. **R2V live e2e on non-EN still pending (owner gate — requires authenticated non-EN Chrome profile).**
-- [ ] **Model Context Protocol (MCP) Server.** (Backlog) Expose core gflow-cli tools via MCP for language-agnostic agentic access. Planned in [PREDICT.md](file:///C:/development/github/gflow-cli/docs/superpowers/plans/2026-06-22-mcp-server/PREDICT.md) / [SCENARIO.md](file:///C:/development/github/gflow-cli/docs/superpowers/plans/2026-06-22-mcp-server/SCENARIO.md) / [PLAN.md](file:///C:/development/github/gflow-cli/docs/superpowers/plans/2026-06-22-mcp-server/PLAN.md).
+- [x] **Model Context Protocol (MCP) Server — SHIPPED** (stdio + HTTP/SSE server in v0.21.0, MCP→FlowWorker generation wiring in v0.23.0/PR #228; `gflow mcp run/setup` + `gflow serve`). Planned in [PREDICT.md](file:///C:/development/github/gflow-cli/docs/superpowers/plans/2026-06-22-mcp-server/PREDICT.md) / [SCENARIO.md](file:///C:/development/github/gflow-cli/docs/superpowers/plans/2026-06-22-mcp-server/SCENARIO.md) / [PLAN.md](file:///C:/development/github/gflow-cli/docs/superpowers/plans/2026-06-22-mcp-server/PLAN.md).
 - [x] **Tools framework + Prompt Expansion ("Creative Director") — shipped → develop (PRs #210 + #211, 2026-06-28).** Prompt expansion evolved from the never-released `-e`/`--expand` flag into a TOML-defined **Tools framework**: `creative-director` is the first built-in tool, invoked uniformly via `--tool/-t <name>[:k=v]` on every generation command (`image t2i`/`i2i`/`batch`, `video t2v`/`i2v`/`r2v`/`chain`) or standalone via `gflow tools list/show/run`. The tool rewrites a terse prompt via Gemini's 5-component formula (`src/gflow_cli/tools/`, stdlib-urllib expander, never-fatal: missing key / 429-backoff / network / empty-clean all fall back to the original), with 15 domain styles and deterministic banned-keyword stripping. `operations.expanded_prompt` records original + submitted expansion (withheld under `history_prompts=redacted`); `metadata_json.tool` records `{name, version, model, params, config_hash}` provenance (minimized in redacted mode). Reuses `GFLOW_CLI_GEMINI_API_KEY`; `GFLOW_CLI_GEMINI_MODEL` overrides. MCP parity: `gflow_list_tools` + a `tools` array param per AGENTS.md §61. Docs: [TOOLS.md](file:///C:/development/github/gflow-cli/docs/TOOLS.md) + [PROMPT_EXPANSION.md](file:///C:/development/github/gflow-cli/docs/PROMPT_EXPANSION.md). Memory `[[prompt-expansion-feature]]`.
   - **PR #210 (framework):** `tools/` package (spec/loader/registry/runtime/expander/banned/invocation), `creative-director.toml`, `gflow tools list/show/run`, `--tool` on t2i/t2v (single-prompt guard kept), MCP `gflow_list_tools` + `tools` param.
   - **PR #211 (broaden surface):** `original_prompt`/`tool` carried on the request DTOs (`GenerateImageRequest`/`GenerateVideoRequest`/`BatchPromptItem`/`ChainLinkSpec`); recorder reads `request.original_prompt` (kwarg retired); `metadata_json.tool` recording; `--tool` wired into i2i/batch/i2v/r2v/chain; single-prompt guard removed. Silent-misrecord hazard resolved by carrying `original_prompt` on the DTO rather than re-threading a kwarg through each recorder method.
@@ -369,7 +369,7 @@ The video-generation feature has its own sub-phase plan (spike → Phase A → P
 - [ ] **Integrated Filmmaking Studio, Flow Worker & MCP SSE Service.** (Backlog) The MCP→FlowWorker wiring shipped in v0.23.0 (PR #228). Remaining: a local FastAPI/React filmmaking studio dashboard + HTTP/SSE MCP. Planned in [gflow-studio-scaffold/PLAN.md](file:///C:/development/github/gflow-cli/docs/superpowers/plans/2026-06-24-gflow-studio-scaffold/PLAN.md) and [rest-api-layer/PLAN.md](file:///C:/development/github/gflow-cli/docs/superpowers/plans/2026-06-24-rest-api-layer/PLAN.md).
 - [x] **Issue #92: Google account identity persistence shipped 2026-05-28 (PR #110).** After every `gflow auth login`, both auth strategies write the verified email to `$GFLOW_CLI_HOME/profile_<name>/.gflow_account`. `ProfileMeta.google_account` surfaces it; `gflow auth list` and `gflow auth list --json` display it. First-login auto-rename: when no `--profile` flag was given and the only profile is named `default`, it is renamed to the email local-part. `profile_store.rename_profile()` primitive added. Zero-credit smoke test (`tests/smoke/test_profile_account_smoke.py`) ships with backfill path for pre-existing profiles. LLM council (9-dim) run; all must-fix items applied before merge. See `KNOWN_ISSUES.md` § Resolved for full detail.
 - [x] **`/gflow:pr-council-review` slash command shipped 2026-05-26 (PR #97).** Multi-dimensional LLM council for open PRs (4 baseline + 8 adaptive dimensions, mandatory memory-slug binding, draft-PR guard, YELLOW escape valve, live-verify gate). Validated on PR #93; self-audited by 3-agent meta-council surfacing 13 must-fix items applied before merge. See memory `[[llm-council-code-review-pr93]]`.
-  - **Phase A (Backlog — Portability):** extract command body into `skills/pr-council-review/SKILL.md` so Gemini CLI / Codex / Cursor / Aider can consume it. Keep `.claude/commands/gflow/pr-council-review.md` as a thin wrapper. Memory: `[[pr-council-review-portability-backlog]]`.
+  - **Phase A (Backlog — Portability):** extract command body into `skills/pr-council-review/SKILL.md` so Antigravity / Codex / Cursor / Aider can consume it. Keep `.claude/commands/gflow/pr-council-review.md` as a thin wrapper. Memory: `[[pr-council-review-portability-backlog]]`.
   - **Phase B (Backlog — Token optimization):** add `scripts/dev/pr_council_prefetch.py` (single gh-call producing structured JSON for agents) and `scripts/dev/memory_filter.py` (relevant slug bodies only). Targets ~30-50% per-agent context cost reduction.
   - **Phase C (Backlog — Reusable meta-council):** codify the 3-dim audit (completeness / robustness / prompt-clarity) we used on this command as `/gflow:meta-council-audit <path>` for re-use on future skills/commands.
   - Sequencing: **A → C → B**.

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/README.md

@@ -90,7 +90,7 @@ gflow-cli ships four agent entry points. Pick the one your tool reads first.
 
 | File | Audience | Tools |
 |---|---|---|
-| [**AGENTS.md**](AGENTS.md) | Universal coding-agent spec | Cursor · Codex · Aider · Gemini CLI · Jules · Devin · Windsurf · Zed · Warp · opencode · Copilot |
+| [**AGENTS.md**](AGENTS.md) | Universal coding-agent spec | Cursor · Codex · Aider · Antigravity · Jules · Devin · Windsurf · Zed · Warp · opencode · Copilot |
 | [**CLAUDE.md**](CLAUDE.md) | Claude Code's auto-loaded memory | Claude Code |
 | [**llms.txt**](llms.txt) | LLM-readable summary (llmstxt.org format) | Paste into ChatGPT, Claude, or Gemini to onboard the model |
 | [`skills/gflow-cli/SKILL.md`](skills/gflow-cli/SKILL.md) | Claude Code Skill | Symlink into `~/.claude/skills/` |

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/docs/AGENT_GUIDE.md

@@ -124,7 +124,7 @@ is reserved in `check_materiality.py` (which already classifies every change).
 ### Satisfying a gate without Claude Code
 
 Every gate enforces a **deliverable**, not a Claude-specific command. Non-Claude agents
-(Cursor / Codex / Gemini CLI / Aider) and humans read the relevant `skills/<name>/SKILL.md`
+(Cursor / Codex / Antigravity / Aider) and humans read the relevant `skills/<name>/SKILL.md`
 directly and produce the same artifact — e.g. read `skills/predict/SKILL.md` and write the
 5-persona verdict into the PR, instead of running `/gflow:predict`.
 

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/docs/ARCHITECTURE.md

@@ -303,6 +303,41 @@ Format defaults to **human-readable on TTY**, **JSON when piped or `GFLOW_CLI_LO
 
 Pipes cleanly into `jq` / Loki / Datadog without configuration. See [`docs/USER_GUIDE.md` § Journey 6](USER_GUIDE.md#journey-6--read-the-structured-logs) for `jq` recipes.
 
+## Incident diagnostics (shipped, v0.43.0)
+
+`FlowApiClient` owns one session-scoped `IncidentRecorder`
+(`gflow_cli.diagnostics`) because it already owns the persistent
+`BrowserContext`, the Page pool, teardown ordering, settings, and the
+profile lease. Lifecycle, in order:
+
+1. **Construct before lease acquisition** (plus best-effort retention
+   pruning), so `ProfileLockedError` contention can produce a metadata-only
+   bundle without ever launching Chrome.
+2. **Attach listeners after context launch, before the bootstrap
+   navigation:** context-level `request`/`response`/`requestfailed` plus a
+   `page` hook, and `console`/`pageerror` on every pooled page. Callbacks do
+   synchronous primitive extraction into bounded ring journals only — they
+   never retain Playwright objects, read bodies, touch the DOM, or perform
+   I/O.
+3. **Capture at the generation boundaries** (`generate_image` /
+   `generate_images_batch` / `generate_video`) while the page is still
+   alive: structural DOM + sensitive screenshot + journal snapshots are
+   *staged*; the manifest is not yet written. Capture is observation-only
+   and serialized by a recorder-local lock; repeats of one failure
+   fingerprint only bump a suppression counter (max 3 bundles/command).
+4. **Teardown order (load-bearing):** detach + freeze journals → bounded
+   context close → resolve HAR state honestly from a pre-launch file
+   snapshot → atomically finalize staged manifests (`manifest.json` last)
+   → driver stop → lease release. Finalization runs through the same
+   bounded/shielded teardown-step helper as everything else and can never
+   mask a close/driver/lease failure or swallow a cancellation.
+
+The legacy `capture_ui_diagnostics` debug dump consumes the same structural
+DOM engine (`STRUCTURAL_DOM_JS` + `validate_structural_dom`) — there is one
+DOM/screenshot engine, not two artifact formats. See
+[DEBUGGING § Automatic incident bundles](DEBUGGING.md#automatic-incident-bundles)
+and [SECURITY § Automatic incident bundles](SECURITY.md#automatic-incident-bundles-gflow_cli_incident_capture-default-on).
+
 ## Testing topology
 
 | Layer | Test type | Where | Network? |
@@ -395,6 +430,8 @@ We attempted three pure-HTTP transport strategies before settling on `ui_automat
 
 All three now live as standalone modules under `src/gflow_cli/api/transports/experimental/` (`evaluate_fetch.py` / `bearer.py` / `sapisidhash.py`), preserved for reference and future iteration. None survives Google's anti-bot stack for mutation/generation endpoints, so the production path is `ui_automation`.
 
+**Standalone-only transports.** `bearer` and `sapisidhash` discard any caller-supplied Playwright page and launch their own browser under a fresh `ProfileLease`, so they are **standalone-only** — they cannot run inside a `FlowApiClient` that already holds the profile lease (the second acquire would self-lock with `ProfileLockedError`). Selecting either via `GFLOW_CLI_TRANSPORT` (or the Python API) while the client owns the profile now fails fast with a clear `ConfigurationError` naming the transport, rather than the opaque lock error. `evaluate_fetch` is exempt: it reuses the client's shared page and takes no second lease. The standalone-only set lives in `STANDALONE_ONLY_TRANSPORTS` (`api/transports/__init__.py`); to drive `bearer`/`sapisidhash`, run them outside an owning client.
+
 ### What this costs users
 
 - A **persistent Chrome profile** on disk (~150 MB after `playwright install chromium`).

{gflow_cli-0.41.0 → gflow_cli-0.43.0}/docs/CONFIGURATION.md

@@ -261,6 +261,15 @@ GFLOW_CLI_HISTORY_PROMPTS=redacted gflow image t2i "confidential brief"
 **When to set it:** capturing locale-invariant DOM via `scripts/dev/capture_locale_invariants.py`, or live-verifying a generation under a non-EN account language.
 **Important:** Chrome's *UI* language is independently forced to `en-US` via the `--lang=en-US` launch arg (so Flow keeps serving `/fx/tools/flow/` and the editor's localized text selectors keep working). This env var only affects request headers — not the editor UI you see. See [KNOWN_ISSUES § issue #24](../KNOWN_ISSUES.md) for the path to dropping `--lang=en-US`.
 
+### `GFLOW_CLI_INCIDENT_CAPTURE`
+
+**What:** Automatically writes a **private incident bundle** on relevant operational failures (Flow app crash, agentic-cohort/UI-mode errors, selector drift, transport timeouts, WAF/network/wire-format errors, profile-lock contention, unexpected exceptions while a page is alive) under `<GFLOW_CLI_HOME>/incidents/<YYYY-MM-DD>/<UTC-stamp>-<incident-id>-<rand>/`. See [DEBUGGING § Automatic incident bundles](DEBUGGING.md#automatic-incident-bundles) for the bundle layout and triggers.
+**Values:** `true` | `false`
+**Default:** `true`
+**When to disable:** shared machines where even structural failure metadata should not persist, or scripted runs that must write nothing outside the output dir.
+
+**Privacy:** the automatic JSON artifacts (`manifest.json`, `ui.json`, `network.json`, `browser.json`) are built from an explicit allowlist — no prompts, tokens, cookies, headers, request/response bodies, signed URLs, raw page titles, raw error/console text, or unknown hosts/routes ever enter them. The screenshot is inherently sensitive (it can show your account identity, prompts, and media) and therefore lives under the bundle's `sensitive/` subdirectory — **review it before sharing**. Nothing is ever uploaded; retention is bounded (at most 50 complete bundles / 250 MiB, pruned oldest-first at startup). Raw HAR capture stays separate and strictly opt-in via `GFLOW_CLI_HAR_PATH`.
+
 ### `GFLOW_CLI_HAR_PATH`
 
 **What:** Captures full Playwright network traffic (requests, responses, headers, cookies) to a HAR file for the session — useful for diagnosing wire-format surprises or WAF rejections.