gflow-cli 0.7.0__tar.gz → 0.8.0__tar.gz

gflow_cli-0.8.0/.claude/commands/gflow/doc-review.md

@@ -0,0 +1,137 @@
+---
+description: Use before cutting any gflow-cli release or after a major feature lands — systematic audit of version refs, INDEX completeness, per-release evidence files, CHANGELOG footer, skill files, and memory records for staleness.
+---
+
+# `/gflow:doc-review` — Documentation Review Gate
+
+Run this gate before cutting a release. Every item reports **PASS / UPDATED / WARN / FAIL**. Any **FAIL** blocks the release.
+
+---
+
+## 1. Version references
+
+Check these files for stale version strings (old numbers, outdated status labels):
+
+| File | What to verify |
+|---|---|
+| `README.md` | Status badge, "What's new" section, install example, milestone table |
+| `CLAUDE.md` | `Active phase` — version, PyPI status, active backlog pointer |
+| `PLAN.md` | Phase status (`IN PROGRESS` / `DONE`) and version annotations |
+| `KNOWN_ISSUES.md` | `Open` entries resolved by this release → move to `Resolved` with evidence |
+| `CHANGELOG.md` | `[Unreleased]` empty; link footer matches new version |
+| `pyproject.toml` + `src/gflow_cli/__init__.py` | Both set to the new version |
+
+Quick grep to spot stragglers:
+
+```bash
+grep -rn "v[0-9]\+\.[0-9]" README.md CLAUDE.md PLAN.md KNOWN_ISSUES.md CHANGELOG.md pyproject.toml
+```
+
+---
+
+## 2. `docs/INDEX.md` completeness
+
+Every `.md` in `docs/` needs an entry; every entry must point to a real file.
+
+```bash
+# files in docs/ missing from INDEX.md
+for f in docs/*.md; do
+  grep -q "$(basename "$f")" docs/INDEX.md || echo "MISSING from INDEX: $f"
+done
+
+# entries in INDEX.md pointing to deleted files
+grep -o 'docs/[^)]*\.md' docs/INDEX.md | while read path; do
+  [ -f "$path" ] || echo "DEAD LINK in INDEX: $path"
+done
+```
+
+---
+
+## 3. Per-release evidence file
+
+After each release a `docs/LIVE_VERIFICATION_vX.Y.Z.md` must exist.
+
+- Latest version has one (create stub if live run already documented elsewhere)
+- `docs/INDEX.md` has an entry for it
+- Previous versions' files are preserved (historical record — never delete)
+
+---
+
+## 4. `.claude/commands/gflow/` skill files
+
+Scan all skills for stale phase/version references:
+
+```bash
+grep -rn "v[0-9]\+\.[0-9]\|Phase [A-Z0-9]" .claude/commands/gflow/
+```
+
+Update in the release prep commit if any references are wrong.
+
+---
+
+## 5. CHANGELOG link footer
+
+```bash
+# Verify [Unreleased] compares from the new version, not an older one
+tail -10 CHANGELOG.md
+```
+
+Must read: `[Unreleased]: …compare/vNEW_VERSION…HEAD`
+
+---
+
+## 6. Memory files
+
+Check `C:\Users\ffrol\.claude\projects\C--development-github-gflow-cli\memory\`:
+
+| File | What to verify |
+|---|---|
+| `MEMORY.md` | All listed files exist; no dangling entries |
+| `phase-b-followups.md` | Items shipped in this release marked done |
+| `video-generation-spec.md` | PR/status accurate |
+| `image-generation-401-next.md` | Resolution status and evidence pointer still valid |
+| `release-signing.md` | Procedure section matches what was actually done |
+
+```bash
+# Check MEMORY.md index integrity
+cd "C:\Users\ffrol\.claude\projects\C--development-github-gflow-cli\memory"
+grep -o '\[.*\]([^)]*\.md)' MEMORY.md | grep -o '([^)]*)' | tr -d '()' | while read f; do
+  [ -f "$f" ] || echo "DEAD LINK: $f"
+done
+```
+
+---
+
+## 7. Stale file cleanup (optional)
+
+Flag (do not delete without user confirmation):
+
+- Temporary debugging artifacts in `docs/` or repo root that were never meant to be permanent
+- Draft specs whose work has fully shipped (move to `docs/archive/` or add "SHIPPED" header)
+- `LIVE_VERIFICATION` files older than two releases that could be archived
+
+Always ask the user before removing or archiving.
+
+---
+
+## Output format
+
+After each section write one line:
+
+```
+[1] Version refs      — PASS
+[2] INDEX completeness — UPDATED (added LIVE_VERIFICATION_v0.7.0.md entry)
+[3] Evidence file     — PASS
+[4] Skill files       — UPDATED (removed stale "Phase A in progress" in plan.md)
+[5] CHANGELOG footer  — PASS
+[6] Memory files      — WARN: release-signing.md procedure section may need update — check with user
+[7] Stale files       — PASS
+```
+
+Then list every **UPDATED** change and every **WARN** / **FAIL** finding for the user to review.
+
+---
+
+## Integration with `/gflow:release`
+
+This skill is invoked at **step 9** of `/gflow:release` (between "review commands for staleness" and "commit the release prep"). All discovered fixes are folded into the release prep commit unless genuinely unrelated to the release.

gflow_cli-0.8.0/.claude/commands/gflow/release.md

@@ -0,0 +1,168 @@
+---
+description: Cut a new gflow-cli release — bump version, update CHANGELOG, tag, push, and back-merge.
+---
+
+# `/gflow:release` — Cut a new release
+
+Follow this sequence verbatim. Every step matters.
+
+> **Branch-protection note:** `main` blocks direct pushes. The release commit travels
+> via a `chore/release-vX.Y.Z` branch PR. The signed tag is pushed independently
+> (tag pushes bypass branch protection and trigger the CI release workflow immediately).
+
+## Inputs
+
+Ask the user (if not already provided):
+
+1. **Version** — the new version (e.g. `0.4.0`, `0.4.0a3`, `1.0.0rc1`). Use PEP 440 prerelease suffixes (`aN`, `bN`, `rcN`). If they don't know, run `/gflow:changelog` first and propose the next bump (PATCH for fixes only, MINOR for new features, MAJOR for breaks).
+2. **Pre-release?** — prerelease versions stay marked as GitHub prereleases. Only the user can say when a release line is ready for the stable tag.
+
+---
+
+## Sequence
+
+**1. Review what's queued.**
+
+Run `/gflow:changelog` — confirm the `[Unreleased]` block is non-empty and accurate before proceeding.
+
+**2. Verify clean working tree.**
+
+```bash
+git status --short
+```
+
+Must be empty. If not, abort and tell the user to commit or stash first.
+
+**3. Verify `main` is up-to-date.**
+
+```bash
+git rev-parse --abbrev-ref HEAD     # must be "main"
+git fetch origin
+git rev-list HEAD..origin/main      # must be empty
+```
+
+If not on `main`, switch: `git checkout main && git pull origin main`.
+If `main` is behind, pull first.
+
+**4. Run quality gates.**
+
+Run `/gflow:check` — all gates must pass. Abort if any fail.
+
+**5. Create a release branch.**
+
+```bash
+git checkout -b chore/release-v<NEW_VERSION>
+```
+
+All release prep commits live here; this branch gets PR'd into `main`.
+
+**6. Bump version** in `pyproject.toml`:
+
+```toml
+[project]
+version = "<NEW_VERSION>"
+```
+
+**7. Bump package version** in `src/gflow_cli/__init__.py`:
+
+```python
+__version__ = "<NEW_VERSION>"
+```
+
+**8. Update version assertion tests** if present:
+
+```bash
+rg -n "__version__|<OLD_VERSION>|version assertion" tests src pyproject.toml
+```
+
+**9. Migrate CHANGELOG.**
+
+- Move all entries under `## [Unreleased]` to a new `## [<NEW_VERSION>] — YYYY-MM-DD` section.
+- Leave `## [Unreleased]` empty.
+- Update the link footer:
+  ```
+  [Unreleased]: https://github.com/ffroliva/gflow-cli/compare/v<NEW_VERSION>...HEAD
+  [<NEW_VERSION>]: https://github.com/ffroliva/gflow-cli/releases/tag/v<NEW_VERSION>
+  ```
+
+**10. Run the documentation review gate.**
+
+Run `/gflow:doc-review` — audit all version refs, INDEX completeness, evidence files, skill files, CHANGELOG footer, and memory files. Fix every **FAIL** before continuing. Fold all discovered fixes into the release prep commit.
+
+**11. Commit the release prep.**
+
+```bash
+git add pyproject.toml src/gflow_cli/__init__.py CHANGELOG.md
+git add docs/ .claude/commands/gflow/        # include any doc-review fixes
+git commit -m "chore(release): v<NEW_VERSION>"
+```
+
+**12. Tag the release commit.** Use `-s` for a signed annotated tag so GitHub shows **"Verified"** AND `.github/workflows/release.yml` passes the signed-tag gate (unsigned or lightweight tags are rejected by CI).
+
+```bash
+git tag -s v<NEW_VERSION> -m "v<NEW_VERSION>"
+```
+
+Signing requirements:
+- **SSH signing (preferred):** `git config --global gpg.format ssh` + `user.signingkey` pointing at your public key.
+- **GPG:** any registered GPG key works.
+- Run `git config --global user.signingkey` to confirm a key is configured.
+
+**13. Push the tag first** (bypasses branch protection; triggers the CI release workflow immediately):
+
+```bash
+git push origin v<NEW_VERSION>
+```
+
+CI will start building the release. Watch <https://github.com/ffroliva/gflow-cli/actions>.
+
+**14. Push the release branch and open the PR.**
+
+```bash
+git push origin chore/release-v<NEW_VERSION>
+```
+
+Open PR `chore/release-v<NEW_VERSION> → main` with title `chore(release): v<NEW_VERSION>`. Merge it once CI is green. (The release workflow already ran from the tag push in step 13 — the PR is to keep `main` up-to-date with the bump commit.)
+
+**15. Back-merge `main` into `develop`.**
+
+After the release PR is merged, bring the bump commit back to `develop` so branches stay aligned:
+
+```bash
+git checkout develop
+git pull origin develop
+git fetch origin main
+git merge origin/main --no-ff -m "chore: back-merge main (v<NEW_VERSION>) into develop"
+git push origin develop
+```
+
+If there are conflicts (rare — only if `develop` has commits that touched the same lines as the bump), resolve them, keeping `develop`'s unreleased work and `main`'s version bump.
+
+**16. Report.**
+
+Tell the user:
+- Tag push triggered `.github/workflows/release.yml`.
+- Watch <https://github.com/ffroliva/gflow-cli/actions> for the release workflow.
+- On success: PyPI publish + GitHub Release with auto-generated notes.
+- On failure (most common: PyPI Trusted Publishing not yet configured): point to <https://pypi.org/manage/account/publishing/>.
+- `develop` is now synced with `main` (back-merge done in step 15).
+- Next development cycle starts on `develop` — open `## [Unreleased]` in CHANGELOG is ready.
+
+---
+
+## Critical reminders
+
+- **NEVER** add `Co-Authored-By: Claude` (or any AI co-author) to the release commit.
+- **NEVER** force-push a release tag once it's on GitHub. Ship a PATCH fix instead.
+- **NEVER** `--no-verify` past hooks. Fix the underlying issue.
+- **NEVER** push directly to `main` — branch protection will reject it. Always use a PR.
+- If quality gates fail at step 4, **STOP**. Surface the failures to the user.
+- If doc-review fails at step 10, **STOP**. Fix before committing.
+
+---
+
+## See also
+
+- [RELEASE.md](../../../RELEASE.md) — full release protocol, prerelease policy, and checklist
+- [README § Releases](../../../README.md#releases) — release policy and cadence
+- [PLAN § Phase 5](../../../PLAN.md#phase-5--public-alpha-release-on-pypi) — first-release exit criteria

gflow_cli-0.8.0/.continue-here.md

@@ -0,0 +1,118 @@
+---
+phase: phase-b-video-download
+task: 0
+total_tasks: 6
+status: ready_to_execute
+last_updated: 2026-05-20T16:22:15.971Z
+---
+
+<current_state>
+Plan written and saved. No code written yet. Ready to execute Task 1 of 6.
+
+Branch: develop (clean, up-to-date after back-merge of main v0.7.0)
+Plan file: docs/superpowers/plans/2026-05-20-video-download-t2v-cli.md
+</current_state>
+
+<completed_work>
+
+This session (prior to plan writing):
+- v0.7.0 release protocol fixed: new /gflow:release (16 steps) with branch-protection-aware push, doc-review gate, back-merge step
+- New /gflow:doc-review skill created at .claude/commands/gflow/doc-review.md
+- PR #34 merged to develop; back-merge main (v0.7.0) → develop done (d012bcd)
+- Memory items D and F in phase-b-followups.md marked resolved
+- develop is fully clean and synced with main
+
+Plan tasks (NOT YET STARTED — all 6 remain):
+- Task 1: VideoResult dataclass in api/video.py
+- Task 2: _download_video helper on VideoGenerationMixin
+- Task 3: generate_video returns VideoResult, gains download=True param
+- Task 4: FlowApiClient.download_video wraps self.download()
+- Task 5: gflow video t2v CLI restored (--aspect / --profile / --out-dir)
+- Task 6: CHANGELOG entries
+</completed_work>
+
+<remaining_work>
+
+All 6 plan tasks. Execute in order — each has TDD steps (RED→GREEN→commit).
+
+Task 1: VideoResult dataclass
+  - Add to src/gflow_cli/api/video.py after VideoStatus
+  - Test in tests/api/test_video.py
+
+Task 2: _download_video on VideoGenerationMixin
+  - Add to src/gflow_cli/api/transports/ui_automation_video.py
+  - Uses page.request.get(routes.media_download_url(media_id), max_redirects=5, timeout=180_000)
+  - Test in tests/api/transports/test_ui_automation_video.py
+
+Task 3: Update generate_video signature
+  - Add download: bool = True param
+  - Return type VideoStatus → VideoResult
+  - After _poll_video_status: if download and status.succeeded → _download_video
+  - Both generate_video and _generate_video_locked change signatures
+
+Task 4: FlowApiClient.download_video
+  - 3-line wrapper: return await self.download(media_id, out_path)
+  - Add after download_image in src/gflow_cli/api/client.py
+  - Test in tests/api/test_client.py
+
+Task 5: cli_video.py T2V restoration
+  - Replace entire file content (plan has full replacement)
+  - Uses UiAutomationTransport directly (not FlowApiClient)
+  - prompt becomes required argument (was optional)
+  - New options: --aspect (9:16/16:9), --profile, --out-dir
+  - Test in tests/cli/test_cli_video.py
+
+Task 6: CHANGELOG
+  - Add entries under [Unreleased]
+</remaining_work>
+
+<decisions_made>
+
+- VideoResult(status: VideoStatus, local_path: Path | None) — new frozen dataclass,
+  NOT a tuple, for clean ergonomics (same pattern as GeneratedImage on image side)
+
+- generate_video is a breaking change (VideoStatus → VideoResult return type) —
+  acceptable in Phase B; no external callers known
+
+- _run_t2v uses UiAutomationTransport directly, NOT FlowApiClient —
+  YAGNI: FlowApiClient.generate_video wrapper deferred; transport pattern
+  proven by tmp/fetch_video.py
+
+- Download uses page.request.get (Playwright, follows 302 natively) NOT httpx —
+  httpx _download static method is image-only and doesn't follow redirects;
+  video needs the 302 to GCS followed with auth context
+
+- Aspect.from_cli() used in CLI (not a hand-rolled mapping) — already exists in
+  src/gflow_cli/api/video.py line 37
+
+- Default aspect for t2v CLI: 9:16 (PORTRAIT) — matches GenerateVideoRequest default
+</decisions_made>
+
+<blockers>
+None. Plan is fully self-contained and executable.
+</blockers>
+
+<context>
+Phase B of gflow-cli. Phase A shipped T2V transport (generate_video on
+UiAutomationTransport) in v0.7.0 but generate_video never downloaded the mp4.
+This plan adds the download primitive and wires the CLI.
+
+Key files to understand:
+- src/gflow_cli/api/video.py — VideoStatus, GenerateVideoRequest, Aspect.from_cli()
+- src/gflow_cli/api/transports/ui_automation_video.py — VideoGenerationMixin, generate_video, _poll_video_status
+- src/gflow_cli/api/routes.py — media_download_url(media_id) → getMediaUrlRedirect URL
+- src/gflow_cli/api/client.py — download() at ~line 510 (already handles the redirect)
+- src/gflow_cli/cli_video.py — all stubs, full replacement planned
+- tmp/fetch_video.py — throwaway proof-of-concept for the download approach
+
+After this plan, the remaining Phase B items are:
+- I2V on UiAutomationTransport (Mode.I2V raises NotImplementedError)
+- R2V on UiAutomationTransport (Mode.R2V raises NotImplementedError)
+- T2V portrait live verification (one credit, one run)
+- Listener-miss flake investigation
+</context>
+
+<next_action>
+Read docs/superpowers/plans/2026-05-20-video-download-t2v-cli.md then
+invoke superpowers:subagent-driven-development to execute Task 1.
+</next_action>

{gflow_cli-0.7.0 → gflow_cli-0.8.0}/.gitignore

@@ -75,3 +75,6 @@ samples/captured/flow_outgoing_*.json
 
 # Doc-council scratch dir (bundles + raw reviews + consensus matrix)
 .doc-council/
+
+worktrees/
+

gflow_cli-0.8.0/.planning/todos/pending/pr-38-review.md

@@ -0,0 +1,8 @@
+# PR #38 Review Tasks
+
+- [x] Task 1: Worktree Initialization
+- [x] Task 2: Compliance & Hygiene Check (FAILED DCO, found missing flag in _spawn_chrome)
+- [x] Task 3: Functional Verification (Unit/Integration) (PASSED 680 tests)
+- [x] Task 4: E2E Headless Validation (PASSED on Windows)
+- [x] Task 5: Windows Regression Check (PASSED)
+- [x] Task 6: Review Synthesis

{gflow_cli-0.7.0 → gflow_cli-0.8.0}/CHANGELOG.md

@@ -7,6 +7,130 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.8.0] — 2026-05-23
+
+> **Multi-image-prompt release + transport hardening.** Introduces the
+> `gflow image batch` subcommand backed by a stay-mounted editor session,
+> restores `gflow video t2v` with first-class auto-download, and ships the
+> image/video mode-switch symmetry invariant that closes the historical
+> "first-attempt listener-miss flake." Also clears all SonarCloud findings
+> on the multi-image-prompt PR (cognitive-complexity refactors of
+> `_set_count`, `parse_tsv_manifest`, and `_generate_images_batch_locked`).
+
+### Added
+
+- `gflow image batch <manifest>` subcommand for batch image generation from
+  JSON or TSV manifests, with `--continue-on-error`. `MAX_BATCH_PROMPTS = 5`.
+  All prompts share one Flow project; jitter (3–7 s default) spaces the
+  submission clicks for anti-bot cadence, not completion wait. Closes
+  [#14](https://github.com/ffroliva/gflow-cli/issues/14) part 2.
+- Application-layer structlog events for image-batch submission:
+  `image_batch.submission_attempt`, `image_batch.submission_result`,
+  `image_batch.row_completed`, `image_batch.inter_submission_latency_ms`.
+  Use these to debug Flow throttling regressions without re-instrumenting.
+- `BatchPartialError` (in `errors`) — raised by fail-fast batch when
+  earlier prompts produced downloadable images before the failing one;
+  carries `partial_results` so the orchestrator can salvage them.
+- `BatchIntegrityError` (in `errors`) — raised by the orchestrator when
+  post-download file count does not match the expected count.
+- `BatchSubmissionResult` (in `api.dto`) — new transport-layer per-prompt
+  outcome with `project_id`, `prompt_idx`, `prompt_hash` fields. Public
+  `list[BatchOutcome]` orchestrator return is unchanged.
+- `ui_automation.image_mode_entered` structlog event — emitted when the
+  editor is switched into Image mode. Companion to the existing
+  `ui_automation_video.video_mode_entered`.
+- `ui_automation.orphaned_project_warning` structlog event — emitted when
+  `_enter_editor` succeeded but a later setup step
+  (`_dismiss_blocking_overlays` / `_switch_to_image_mode`) raises, so the
+  user can find their server-side project record.
+- `ui_automation.batch_403_body` structlog event — emitted (warning level)
+  with a 200-char body prefix when a `batchGenerateImages` response is HTTP
+  403 (WAF / reCAPTCHA), immediately before the `WafRejectionError` raise.
+- `VideoResult` dataclass — return type of `generate_video`, carries
+  `status` and `local_path` ([#29](https://github.com/ffroliva/gflow-cli/issues/29)).
+- `UiAutomationTransport._download_video` — downloads a generated mp4 via
+  `media.getMediaUrlRedirect` using the authenticated page; falls back to
+  `self._out_dir` then `tmp/` when no `out_dir` is supplied
+  ([#29](https://github.com/ffroliva/gflow-cli/issues/29)).
+- `FlowApiClient.download_video(media_id, out_path)` — public API, mirrors
+  `download_image` ([#29](https://github.com/ffroliva/gflow-cli/issues/29)).
+- `gflow video t2v PROMPT` restored — generates and downloads a video
+  end-to-end on `UiAutomationTransport`; supports `--aspect`
+  (`9:16` / `16:9`), `--profile`, and `--out-dir`
+  ([#29](https://github.com/ffroliva/gflow-cli/issues/29)).
+- `UiAutomationTransport._switch_to_image_mode` static method + module-level
+  `IMAGE_TAB_IN_MENU_SELECTORS` cascade — mirror of the video side's
+  `_switch_to_video_mode`. Called from both `generate_images` and
+  `_generate_images_batch_locked` after `_dismiss_blocking_overlays`,
+  before `_configure_generation_settings`.
+
+### Changed
+
+- `gflow image batch` editor session is now persistent across all prompts
+  in a batch. The transport's stay-mounted-session pattern is the
+  canonical shape; same-project semantics are the only supported mode.
+- `_attach_batch_response_listener` now returns `(captured, detach_fn)`;
+  callers that used the single-list return need to unpack accordingly.
+- `UiAutomationTransport.generate_video` now accepts `download: bool = True`
+  and returns `VideoResult` instead of `VideoStatus` — **breaking change
+  for direct transport callers** (the `FlowApiClient` boundary is
+  unaffected). Pass `download=False` to skip the auto-download step.
+- `_set_count` (count-tab selector) is locale-invariant: regex
+  `^(1x|x[2-4])$` (Flow renders digit+x identically in every locale) +
+  positional `.nth(count - 1)` fallback when read-back text is
+  unrecognised. Partial fix for
+  [#24](https://github.com/ffroliva/gflow-cli/issues/24); `ONBOARDING_SELECTORS`
+  still localized text — see KNOWN_ISSUES.
+
+### Fixed
+
+- `gflow image t2i` and `gflow image batch` now explicitly select Image
+  mode in the Flow editor before submitting. Previously, if the account
+  was last in Video mode, prompts were silently routed to the video
+  endpoint — no `batchGenerateImages` response was observed and the
+  listener timed out after 3 minutes. Also resolves the historical
+  "first-attempt listener-miss flake" recorded in `phase-b-followups`
+  memory item #1. Live-verified on profile `ffroliva` (1 t2i shot + full
+  batch e2e); evidence in
+  [`docs/LIVE_VERIFICATION_image_batch.md`](docs/LIVE_VERIFICATION_image_batch.md)
+  § Post-mode-switch-fix verification.
+- `gflow image batch` now actually shares one Flow project across all
+  prompts in a batch. Previously the `--same-project=1` flag was a no-op
+  at the `ui_automation` transport layer; each prompt landed in its own
+  Flow project. ([spec](docs/superpowers/specs/2026-05-22-stay-mounted-batch-session-design.md))
+- `gflow image t2i -n N` now makes one transport call using Flow's native
+  xN count selector instead of fanning out N parallel single-image
+  submissions. Closes [#14](https://github.com/ffroliva/gflow-cli/issues/14) part 1.
+- Structlog now uses `cache_logger_on_first_use=False` so per-test
+  `LogCapture` fixtures see events fired from production modules
+  (previously the cached logger froze the processor chain at import).
+- All SonarCloud findings on the multi-image-prompt PR (S5655 / S5890 /
+  S1192 / S1172 / S3776 ×3) — see PR #40 commit `a0cb010` for the
+  cognitive-complexity refactors and the cast+pragma pattern for
+  `dataclasses.replace`.
+
+### Removed
+
+- **BREAKING:** `--same-project` flag on `gflow image batch`. The flag
+  collapsed to a single behaviour (always-same-project) — no toggle
+  remains. For different-project results, loop `gflow image t2i`
+  externally.
+- **BREAKING:** `--seed` flag from `gflow image t2i` and `gflow image i2i`.
+  The flag was a no-op under the active UI transport since v0.7.0
+  (silently discarded inside the client before reaching the transport).
+  If reproducibility via user-controlled seed becomes possible again —
+  either through Flow UI exposing a seed control or via HTTP transport
+  revival — the surface will be re-introduced at that layer. The
+  wire-format body builder retains its `seed` / `batch_id` parameters for
+  the experimental HTTP transports' internal use.
+- **BREAKING (library):** `FlowApiClient.generate_image` no longer accepts
+  `seed=` or `batch_id=` kwargs. `FlowApiClient.generate_images_batch` no
+  longer accepts `seeds=`. Callers passing these will get a `TypeError`.
+  Same justification as the CLI removal.
+- **BREAKING (library):** `project_title` parameter removed from
+  `run_manifest_image_batch` — the transport now owns project creation
+  via `_enter_editor`, making this orchestrator-side knob dead weight.
+
 ## [0.7.0] — 2026-05-20
 
 > **Downstream-worker ergonomics release.** Hardens `FlowApiClient` for
@@ -685,7 +809,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.7.0...HEAD
+[Unreleased]: https://github.com/ffroliva/gflow-cli/compare/v0.8.0...HEAD
+[0.8.0]: https://github.com/ffroliva/gflow-cli/compare/v0.7.0...v0.8.0
 [0.7.0]: https://github.com/ffroliva/gflow-cli/compare/v0.6.0a6...v0.7.0
 [0.6.0a6]: https://github.com/ffroliva/gflow-cli/compare/v0.6.0a5...v0.6.0a6
 [0.6.0a5]: https://github.com/ffroliva/gflow-cli/compare/v0.6.0a4...v0.6.0a5

{gflow_cli-0.7.0 → gflow_cli-0.8.0}/CLAUDE.md

@@ -19,13 +19,13 @@
 
 ## Active phase
 
-**Phase A — Video T2V DONE (PR #23, merged 2026-05-20 to `develop`).** `UiAutomationTransport.generate_video(T2V)` orchestrates the Flow video editor end-to-end via Playwright UI mimicry — the underlying HTTP video path returns 401 from `aisandbox-pa` and was retired. I2V and R2V raise `NotImplementedError` (deferred to Phase B). Companion PRs landed the onboarding-bypass (#27), changelog-overlay dismiss (#28), and signed-tag release verification (#30).
+**v0.7.0 SHIPPED on PyPI (2026-05-20).** First stable (non-`aN`) release. Downstream-worker ergonomics release: `out_dir` plumbing, `health_check()`, optional `project_id`, `BrowserSessionClosedError` (#16 + #18); auth hardening (#15 + #17); overlay-dismiss (#26); 1:1 aspect-ratio cascade; signed-tag CI gate (#30); listener instrumentation. Image generation end-to-end live-verified on `ui_automation` across four aspect ratios (`9:16`, `16:9`, `1:1`, `4:3`) — see [`docs/LIVE_VERIFICATION_v0.7.0.md`](docs/LIVE_VERIFICATION_v0.7.0.md). The historical `aisandbox-pa` 401 is RESOLVED in v0.7.0 (KNOWN_ISSUES `## Resolved`).
 
-**Active backlog → Phase B.** See the Phase B follow-ups (project memory, run `/gflow:plan` for current detail) and these GitHub issues:
-- [#29](https://github.com/ffroliva/gflow-cli/issues/29) first-class video download (mirror the image-side `download_image` pattern)
-- Image-gen 401 live validation (was the bypass branch's whole reason — never confirmed e2e)
-- CLI restoration: `gflow video t2v/i2v/batch` are currently stubbed
-- I2V then R2V on `UiAutomationTransport`
+**Active backlog → Phase B (video CLI).** Phase A (T2V transport, PR #23) shipped with v0.7.0. PR #36 (merged 2026-05-21) restored `gflow video t2v` with first-class video download ([#29](https://github.com/ffroliva/gflow-cli/issues/29) — CLOSED), `VideoResult`, and `FlowApiClient.download_video`; both `9:16` and `16:9` live-verified on profile `ffroliva` (see [`docs/LIVE_VERIFICATION_video_download.md`](docs/LIVE_VERIFICATION_video_download.md)). Remaining Phase B work:
+- I2V (image-to-video) on `UiAutomationTransport` (`Mode.I2V` still raises `NotImplementedError`); then R2V
+- Restore `gflow video i2v` and `gflow video batch` (currently stubbed with "not yet available")
+- Parameterized live e2e under `tests/e2e/test_video_t2v_e2e.py` mirroring the image-side e2e
+- v0.7.0 follow-ups still open: first-attempt listener-miss flake, signed-tag CI auto-signing (sigstore `gitsign`), and the `/gflow:release` doc bridge for the develop→main flow
 
 Run `/gflow:plan` for the current detailed plan if a superpowers plan is active.