@sabaiway/agent-workflow-kit 5.6.0 → 5.8.0

package/CHANGELOG.md

@@ -4,6 +4,98 @@ Semantically versioned ([semver](https://semver.org)), newest first. The `versio
 is the current release. `upgrade` mode reads a project's `docs/ai/.workflow-version` and applies
 every `migrations/<version>-<slug>.md` newer than it, in semver order.
 
+## 5.8.0 — the bundled agy bridge speaks the catalog the installed CLI actually serves, and grounding stops needing a shell (AD-095; antigravity-cli-bridge 5.2.0)
+
+**A model display string is matched exactly, so a stale one is not a documentation bug — it is a
+dispatch that refuses before it spends anything.** The bundled agy bridge had been describing a
+catalog captured from CLI v1.0.13 while the installed binary moved to 1.1.13. The user-facing
+catalog tables and every default pin now carry bytes read off `agy models` on the live binary,
+which also turned up a `Gemini 3.6 Flash` family no announcement mentioned and confirmed 3.5 Flash
+is still served. (The wrapper's own header comment stays a compact family inventory and now says
+so, pointing at `agy models` for the exact strings.)
+
+- **`Gemini 3.7 Flash (High)` is the bridge default for both roles** — `agy-run` and `agy-review` —
+  and joins the review wrapper's frontier set, so a council review on it stays advisory-silent.
+  Asserting frontier grade for the review lane was the maintainer's explicit call, not a default
+  that drifted. Any model remains selectable through `AGY_MODEL`; the sub-frontier advisory is
+  still a silenceable warning, never a gate.
+- **The catalog lists every served row individually.** The 3.6 and 3.5 families are enumerated
+  Low/Medium/High rather than collapsed into `(Low|Medium|High)` — a collapsed row reads as a
+  display string that does not exist, and pasting it fails.
+- **The reference stops overclaiming the wrapper's output.** v1.1.13 adds `--output-format
+  json|stream-json`, `--json-schema`, `--effort` and `--mode`; the wrapper adopts none of them, so
+  the docs now say text-DEFAULT and state plainly that raw passthrough JSON rides without
+  first-class parsing or validation. The old "no JSON output mode" sentence had become false.
+- **`grounding.mjs --extra <text|@file>` merges orchestrator facts inside the tool.** Appending
+  live judgment facts to an emitted facts payload had been a shell append four times running; it is
+  now an input. Extras append byte-verbatim after the mechanical sections. The read surface is
+  deliberately narrow and fail-closed: an `@file` must sit inside a PROVEN work tree (a successful
+  `git rev-parse --show-toplevel` — never a `cwd` fallback) or the system temp surface, never
+  inside the git dir including a linked worktree's `.git` gitfile, and it is read through the kit's
+  no-follow descriptor door so a FIFO cannot block the assembler and a symlink leaf cannot
+  substitute its target. Git location variables (`GIT_DIR`, `GIT_WORK_TREE`, …) are scrubbed before
+  every git query, so an ambient override cannot prove a foreign tree.
+
+## 5.7.0 — what the kit emits is now something a test executed, a claim it proved, or a command you can run (AD-092 + AD-093 + AD-094; memory 4.3.0)
+
+**Three feedback plans, one release.** A live upgrade session on a deployed TypeScript project
+returned seven items of feedback, and every one reduced to the same shape: the kit EMITTED something
+— a shell command, a status line, a prescribed operation, an optimality verdict — and nothing
+downstream ever ran it, proved it, or performed it. This release closes that shape end to end, and
+closes it for future releases too: a kit candidate can no longer be dispatched without proving
+itself against the kit that is ALREADY published.
+
+- **The canonical coverage destination refuses by name instead of writing to the filesystem root.**
+  The emitted cmd becomes `"${AW_GIT_DIR:?exported by run-gates}/agent-workflow-lcov.info"`:
+  byte-identical where the runner injects the variable, a loud named bash refusal where a human
+  pastes it into a bare shell — the old form expanded an unset variable to empty and sent the lcov
+  to `/`. Recognition is APPEND-ONLY (`KNOWN_COVERAGE_FLAG_SETS`): every form the kit ever emitted
+  stays recognized, so a deployed old-form gate is never reclassified as customized. `run-gates` now
+  reads `${VAR:?…}` as a producer reference and refuses before spawning uninjected. And the emitted
+  command is a FIXTURE the tests execute — asserted by running it, unset and injected both, never by
+  admiring the string.
+- **"Flow optimal" became a claim the advisor must be able to SEE.** Binary probes gained NAMED third
+  outcomes: `gates-inert.producer-unrecognized` (a checker no recognized producer feeds, where the
+  tracked-tree census says most of the tree is outside the assessable domain — the remedy is "mark
+  the real producer or drop the checker", never a `node --test` prescription) and
+  `gates-inert.coverage-domain-narrow` (a live producer certifying an assessable minority — converges
+  only on an explicit acknowledgment, fingerprint-bound to the fact, re-firing when the fact
+  changes). The census is the predicate: no census, no optimality claim. A vendored copy of a core
+  check no longer stops the upgrade: the migration preserves it as a zero-diff `keep` row plus
+  separately rendered verify metadata, and only a genuine id collision on the canonical checker id
+  still hard-stops. On the advisor side, the source-size tool copy gets its own named outcomes —
+  `source-size.adopted-elsewhere` (optional) and `source-size.id-squatter` (attention, a
+  hand-apply recovery, never a stop).
+- **The `lcovProducer` marker lets a declaration CLAIM a producer the closed cmd-world cannot name**
+  — vitest, pnpm wrappers, any runner that writes the lcov. Only the literal `true` counts, the
+  marker never widens what a RUN may certify (a marker-claimed producer that writes no lcov still
+  ends `skipped-no-lcov`), and it is FORWARD-ONLY by decision: the published 5.6.0 kit rejects a
+  marker-carrying `gates.json` loudly at validation (exit 5, naming the key) rather than degrading
+  to a false advisory — upgrade the kit before marking (Issue-016 states all three cross-version
+  axes).
+- **Upgrade step 3 is a registry-owned run-list, not prose.** `tools/upgrade-runlist.mjs` owns the
+  seven operation identities (`pointers` · `footprint` · `configs` · `gates-migration` · `bridges` ·
+  `lens` · `bridge-settings`); the checklist in `references/modes/upgrade.md` renders from it, a
+  structure test holds doc ↔ registry in both directions, and the four config "ensures" the doc used
+  to prescribe as prose are ONE runnable command — `ensure-configs.mjs --reconcile [--dry-run]`,
+  fixed order, create-only seeds, a CLOSED outcome vocabulary that throws on any token outside it.
+  A library module invoked as a command now says so and exits 2 instead of silently exiting 0.
+- **A tool-composed line a user reads is user-grade language.** Machine tokens and tool self-labels
+  ride machine lines (`[tool] key=value`); alarm words render only under a DETECTED abnormal
+  condition; the read-only refresh degrade states only what its re-scan PROVED (one scanner, closed
+  `clean-parity`/`drifted`/`unverifiable` vocabulary) instead of an unconditional "may be PARTIALLY
+  updated". The guard test enumerates every composer's outcome variants from its own closed branch
+  set — a new line joins the contract by construction. The hide-footprint report now states its
+  delta against the current managed block: `+N added` / `−N removed`, sets listed, `+0/−0` explicit.
+- **A kit-carrying dispatch needs TWO receipts, dry-run included.** Beside the candidate smoke
+  (packs the candidate, installs it into a foreign fixture, asserts the advisor sees what this
+  repo's own suite cannot show), `scripts/release/cross-version-gate.mjs` installs the PUBLISHED kit
+  `@latest` and asserts the three Issue-016 axes BY NAME — `schema-accept` / `execution` /
+  `producer-recognition` — with the conditional arms decided by comparing the probed published
+  version against `MARKER_AWARE_SINCE` (fixed forever at `5.7.0`, the first marker-aware kit), never
+  inferred from the accept itself. Both receipts are HEAD-bound and field-validated; an unreachable
+  registry refuses loudly with no receipt.
+
 ## 5.6.0 — a source-size practice your project declares, and a record that is debt rather than permission (AD-091; engine 2.1.0)
 
 **A big module is expensive long before anyone calls it a problem, and nothing in the kit ever said

package/README.md

@@ -229,7 +229,7 @@ file), or run the guarded `/agent-workflow-kit uninstall`.
 | `/agent-workflow-kit upgrade` | existing deployment | reads `docs/ai/.workflow-version`, shows the changelog diff, preserves your authored memory, applies migrations, re-stamps — then prints a **read-only** one-line backend-status line (what's set up vs missing); refreshes the already-placed bridges from the kit's bundled copies (never installs a new one — set one up with `/agent-workflow-kit setup`) |
 | `/agent-workflow-kit help` | any time | **read-only command index** — every command, grouped (Inspect / Configure / Orchestrate / Lifecycle) and tagged read-only / writer / guarded. The discoverable entry point, and where any unrecognized invocation lands (always read-only — a garbage invocation never writes). Never writes, never commits, never runs a subscription CLI. |
 | `/agent-workflow-kit backends` | any time | **read-only** check of the optional execution-backends (the `codex` / `agy` bridges): what's set up vs missing and the next step. Never writes, never commits, never runs a subscription CLI (credentials = marker-file presence, not a live login). |
-| `/agent-workflow-kit gates` | any time | **project gate runner** — runs the verification commands **your project itself declares** in `docs/ai/gates.json` (seeded at deploy; hand-editable `{ id, title, cmd }` entries, each `cmd` one bash line) as one batch: a per-gate **PASS/FAIL table** + one machine-readable summary line, exit 0 iff all green; a failing gate's own output is shown verbatim; `--only <id>` re-runs one. Honest distinct outcomes for a missing / empty / malformed declaration — never a silent green. The runner writes nothing **by default** and never commits — opt-in `--final` runs the FULL declared matrix and mints ONE final-run receipt into the git-dir core-evidence store (status green/red, pre/post tree fingerprints, the declaration, the consumed lcov's sha; the receipt the commit-guard binds); it executes only your own declared commands (a batching convenience, not a sandbox). The velocity tier auto-approves only the exact no-`--final` form — the recording run stays explicit. |
+| `/agent-workflow-kit gates` | any time | **project gate runner** — runs the verification commands **your project itself declares** in `docs/ai/gates.json` (seeded at deploy; hand-editable `{ id, title, cmd }` entries plus the optional boolean `lcovProducer`, each `cmd` one bash line) as one batch: a per-gate **PASS/FAIL table** + one machine-readable summary line, exit 0 iff all green; a failing gate's own output is shown verbatim; `--only <id>` re-runs one. Honest distinct outcomes for a missing / empty / malformed declaration — never a silent green. The runner writes nothing **by default** and never commits — opt-in `--final` runs the FULL declared matrix and mints ONE final-run receipt into the git-dir core-evidence store (status green/red, pre/post tree fingerprints, the declaration, the consumed lcov's sha; the receipt the commit-guard binds); it executes only your own declared commands (a batching convenience, not a sandbox). The velocity tier auto-approves only the exact no-`--final` form — the recording run stays explicit. |
 | `/agent-workflow-kit setup [backend]` | opt-in, any time | **link-only** auto-setup of a bridge: places the bundled bridge skill (only into an absent / empty / managed dir — never overwrites an unmanaged one) + links its wrappers onto `PATH` via managed symlinks (idempotent; refuses to clobber a non-symlink; try `--dry-run` to preview). The binary install + the one-time subscription login stay **manual**: it prints the exact **login** command and points the binary install at each bridge's `setup/README.md`. POSIX wrappers — on Windows use WSL. Never commits, never runs a subscription CLI. |
 | `/agent-workflow-kit status` | any time | **read-only** single view of **versions + deployment + settings + bridges**: which members (kit / memory / engine / the two bridges) are installed and at what version (with an honest "installed on this machine" note when one is behind) and — in a project — what's deployed (`docs/ai`, the version stamps, and the **visibility**: visible / hidden / unclear), plus your settings (orchestration recipes, attribution, velocity) and the bridges' readiness. The two version axes (package number vs deployment-structure head) stay decoupled. Never writes, never commits, never runs a subscription CLI. |
 | `/agent-workflow-kit recipes` | any time | **read-only** orchestration advisor: presents four named recipes for composing the bridges into plan → execute → review — **Solo / Reviewed / Council / Delegated** — plans + recommends one for your environment (degrading with a stated reason when a backend isn't ready), and offers the choice. The orchestrator runs it via the bridge skills and **always commits**; the kit never executes a recipe, never runs a subscription CLI, never commits. |
@@ -237,7 +237,7 @@ file), or run the guarded `/agent-workflow-kit uninstall`.
 | `/agent-workflow-kit set-recipe` | any time | **config writer** for `docs/ai/orchestration.json`: tell the agent your preference in plain language and it maps it to explicit `--set <activity>.<slot>=<recipe>` / `--unset` ops; the kit validates, **previews by default**, and writes only on `--write` (deployment-gated, atomic, symlink/TOCTOU-safe), resolving the effective recipe vs live readiness. Writes **only** that file — **never runs a backend, never commits**; hand-editing stays fully supported. |
 | `/agent-workflow-kit review-state` | any time | **read-only review-receipt checker** — makes "reviewed ≠ shipped" detectable: the bridge review wrappers append a receipt per successful review (into a file inside the git dir — never committable); this checks that every backend your configured `plan-execution.review` recipe names holds a **fresh, grounded receipt for the current uncommitted tree** (any later edit moves the fingerprint and stales the receipt; a review continuation never re-attests a folded tree). `--check` gives a gate exit code to declare in `docs/ai/gates.json` **by hand or via the consent-gated seeder** (preview → your explicit yes; never without consent). `--await [--timeout <s>]` (AD-049) BLOCKS until every recipe-named backend has receipted the current tree — the durable completion signal is the receipt, never a process event — so you wait for the bridges instead of hand-polling. Never writes, never commits, never runs a subscription CLI; it spawns read-only `git` queries to fingerprint the tree — and `git commit --no-verify` stays possible (discipline, not a sandbox). |
 | `/agent-workflow-kit sandbox-masks` | any time | **cosmetic exclude lane for sandbox device masks** — an OS sandbox (Claude Code) injects character-device masks into the work tree as untracked `git status` noise; the review domain already ignores them **by construction** (never-committable untracked classes — char/block devices, FIFOs, sockets — are excluded from the fingerprint, the assembled review payload, and the clean checks). This mode hides them from `git status` too: flagless = read-only probe (derives the CURRENT mask set from the unfiltered walk + lstat — never a frozen list — and revalidates fenced entries, loudly flagging one that became a real path); `--apply` = consent-gated FULL-BLOCK replace of its own fenced block in `git rev-parse --git-path info/exclude` (stale masks drop by construction; `--clear` always means REMOVE the block — it takes precedence over the derivation). Writes ONLY its fence — never `.gitignore`, never global config; symlinked/non-regular exclude paths and malformed fences fail closed. Watch note: a real file at an excluded path is silently skipped by bulk staging (`git add -A`/`git add .`) — delete the stale line first; the probe flags exactly this case. |
-| `/agent-workflow-kit grounding` | any time | **grounded-review facts assembler** — mechanizes populating `agy-review --facts @f`: slices your entry-point's **Hard Constraints** section verbatim (exactly one match, else a loud stop) and/or a plan's decision-bearing sections (`## Approach` + `## Verification` required, `## Decisions (locked)` when present; duplicates stop), under the same byte budget the agy wrapper enforces (minus `--reserve-bytes` for the artifact share), with a loud tail-trim on overflow. `--autonomy` (AD-044) appends the COMPUTED effective autonomy policy from the git-top `docs/ai/autonomy.json` (every red-line + per-activity level, stated source line; absent file → the computed defaults ARE the policy, exit 0; a malformed policy fails CLOSED, exit 1). Prints to stdout; `--out` writes **one scratch file only** — system-temp outside the repo ($TMPDIR / /tmp, rewritable) or a **fresh** gitignored in-repo path (create-only, exclusive write; an existing in-repo file, even gitignored, is refused — the `.env` clobber class); tracked, not-ignored-in-repo, other outside-repo, and symlink/non-regular destinations are all refused. Never commits, never runs a subscription CLI. |
+| `/agent-workflow-kit grounding` | any time | **grounded-review facts assembler** — mechanizes populating `agy-review --facts @f`: slices your entry-point's **Hard Constraints** section verbatim (exactly one match, else a loud stop) and/or a plan's decision-bearing sections (`## Approach` + `## Verification` required, `## Decisions (locked)` when present; duplicates stop), under the same byte budget the agy wrapper enforces (minus `--reserve-bytes` for the artifact share), with a loud tail-trim on overflow. `--autonomy` (AD-044) appends the COMPUTED effective autonomy policy from the git-top `docs/ai/autonomy.json` (every red-line + per-activity level, stated source line; absent file → the computed defaults ARE the policy, exit 0; a malformed policy fails CLOSED, exit 1). `--extra <text|@file>` (repeatable) appends your own facts **byte-verbatim** after the mechanical sections, so the merge is a tool input rather than a shell append — an `@file` must sit inside the proven git work tree (never the git dir) or the system temp surface, and is read through a no-follow descriptor (a FIFO cannot block it, a symlink leaf cannot substitute its target). Prints to stdout; `--out` writes **one scratch file only** — system-temp outside the repo ($TMPDIR / /tmp, rewritable) or a **fresh** gitignored in-repo path (create-only, exclusive write; an existing in-repo file, even gitignored, is refused — the `.env` clobber class); tracked, not-ignored-in-repo, other outside-repo, and symlink/non-regular destinations are all refused. Never commits, never runs a subscription CLI. |
 | `/agent-workflow-kit core-evidence` | any time | **the ONE loop-evidence writer** (strip-the-kit) — every core evidence record lands in a single append-only JSONL store inside the git dir (never committable; versioned schema, latest-per-key supersession, byte-identical duplicates refused, malformed lines fail every reader closed). `red-proof "<file>#<pattern>"` declares an observed-red **BEFORE a bugfix** (N/N red runs + content custody + base + the pre-fix fingerprint; green/mixed/timeout are DISTINGUISHED refusals — nothing written); `degrade --backend --reason` is the ONLY escape for an unavailable review backend (per-tree, never all backends); `summary` renders the whole loop state statelessly (gate result · per-backend verdicts · red-proofs · degrades) — no ledger, no rounds, nothing remembered. Honest residual: records are forgeable — self-discipline, not a security boundary. Never commits, never runs a subscription CLI. |
 | `/agent-workflow-kit coverage-check` | any time | **the final-run checker** (D3(c)+(d)) — **certifies coverage ONLY inside the `--final` run that owns the lcov** (ownership is exclusive by CONVENTION over the fixed path, not enforced — a concurrent writer to it is a stated residual, queued as LCOV-EXCLUSIVE-OWNERSHIP): an artifact on disk proves nothing about the tree it came from, so a standalone run prints its findings and states `attested=no` / `NO VERDICT` rather than a PASS (an lcov that predates an edit would otherwise certify a line the suite never executed). `attested=` claims a verdict was ISSUED, pass or fail — a run over uncovered lines still reads `attested=yes` and still exits 1, and a run whose coverage arm never executed (no lcov) reads `attested=no` even inside `--final`, because nothing was read and nothing is certified. The runner passes a nonce whose one-way commitment over `{nonce, fingerprint, base}` is the `final-start.attempt` it recorded; a context describing another tree, or matching no recorded attempt, is a REFUSAL, never a verdict. Findings are unchanged — reads the lcov the declared `unit-tests` gate produced at the FIXED git-dir path and fails on any uncovered CHANGED executable Node line (listed `file:line`; a changed file absent from the map is a file-level red; out-of-domain/unsupported files are LISTED — the claim narrowed honestly); VERIFIES every current-base red-proof declaration (bound test exists · custody hash unchanged · green N/N now · pre-fix fingerprint differs); prints `lcov-sha256=<hex|none>` of the exact bytes it consumed — the sha the `--final` receipt binds and re-hashes. An absent lcov is a LOUD `skipped-no-lcov`; a symlinked path is a refusal. `--check` is the gate exit code — declare it as the LAST gate (`run-gates --final` refuses otherwise). Read-only. |
 | `/agent-workflow-kit commit-guard` | any time | **the read-only pre-commit guard** (D10) — makes the commit capture the whole current working tree, so «verified» and «about to be committed» are the same bytes (the receipt itself has a stated residual — see the mode doc). FIRST it refuses an **INDEX that lags the verified working tree** (the gates and the fingerprint describe the WORKING tree while `git commit` takes the INDEX alone, and the fingerprint cannot tell them apart — so a lagging index used to ship a strict subset of what was verified): unstaged tracked paths or reviewable untracked-not-ignored paths, named up to a bounded cap with the remainder stated, a dirty tracked **submodule** named separately with its own recovery, and fail-closed on an undecidable probe. This deliberately blocks a partial commit. Then it binds the LATEST completed `run-gates --final` receipt to the EXACT current tree: refuses on a missing/red/stale receipt, fingerprint drift under the run, a dangling later attempt, declaration content drift, evidence-hash or lcov drift, or unsatisfied review obligations (the same review-state decision, recomputed over a sanitized env — forged out-of-repo stores never satisfy). Re-runs NO gate or test. Wire it into `.git/hooks/pre-commit` (the installer writes the RESOLVED invocation). `git commit --no-verify` stays the stated residual. |

package/SKILL.md

@@ -3,7 +3,7 @@ name: agent-workflow-kit
 description: Deploy or upgrade a portable AI-agent memory-and-workflow system in any project. Use when the user wants to bootstrap `docs/ai/` + an entry-point `AGENTS.md` (+ `CLAUDE.md` alias) + cap/archive/index enforcement in a new or existing repo, set up the Memory Map and session protocols, install the docs-rotation pre-commit hook, or run `/agent-workflow-kit` / `/agent-workflow-kit upgrade`. Triggers on phrases like "set up the memory system", "deploy the AI workflow here", "bootstrap docs/ai", "upgrade the workflow".
 disable-model-invocation: true
 metadata:
-  version: '5.6.0'
+  version: '5.8.0'
 ---
 
 # agent-workflow-kit

package/bridges/antigravity-cli-bridge/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: antigravity-cli-bridge
-description: Delegate work to Google's Antigravity CLI (`agy`) — the successor to Gemini CLI — to reach Gemini, Claude, and GPT-OSS models under a Google AI Pro/Ultra subscription from the terminal. Use when the user wants to run a headless `agy` prompt, hand a focused task or second-opinion review to `agy`, install or authenticate Antigravity CLI, check or economise its quota/models, bridge project context into `agy`, set up a second delegated-execution backend beside Codex, or troubleshoot `agy` flags, models, auth, conversations, or its no-JSON headless behaviour.
+description: Delegate work to Google's Antigravity CLI (`agy`) — the successor to Gemini CLI — to reach Gemini, Claude, and GPT-OSS models under a Google AI Pro/Ultra subscription from the terminal. Use when the user wants to run a headless `agy` prompt, hand a focused task or second-opinion review to `agy`, install or authenticate Antigravity CLI, check or economise its quota/models, bridge project context into `agy`, set up a second delegated-execution backend beside Codex, or troubleshoot `agy` flags, models, auth, conversations, or its headless behaviour.
 metadata:
-  version: '5.1.1'
+  version: '5.2.0'
 ---
 
 # antigravity-cli-bridge
@@ -53,16 +53,22 @@ keep probes short (see *How the main agent drives agy*).
 ## Models
 
 Pass the **exact display string** to `--model` (or set `AGY_MODEL`). The wrapper defaults to
-`Gemini 3.1 Pro (High)`. Run `agy models` for the live list — if it differs from this table, the live
-list wins.
+`Gemini 3.7 Flash (High)`. Run `agy models` for the live list — if it differs from this table, the
+live list wins.
 
 | Model string | Use it for |
 |---|---|
-| `Gemini 3.5 Flash (Low)` | cheapest; reachability checks, smoke tests, simple transforms |
-| `Gemini 3.5 Flash (Medium)` | cheap probes, context-reachability checks, quick summaries |
-| `Gemini 3.5 Flash (High)` | fast drafting / review when a little more effort helps |
+| `Gemini 3.7 Flash (Low)` | cheapest; reachability checks, smoke tests, simple transforms |
+| `Gemini 3.7 Flash (Medium)` | cheap probes, context-reachability checks, quick summaries |
+| `Gemini 3.7 Flash (High)` | wrapper + review default; asserted frontier-grade (fork (a)) |
+| `Gemini 3.6 Flash (Low)` | previous Flash generation, still served — prefer 3.7 |
+| `Gemini 3.6 Flash (Medium)` | previous Flash generation, still served — prefer 3.7 |
+| `Gemini 3.6 Flash (High)` | previous Flash generation, still served — prefer 3.7 |
+| `Gemini 3.5 Flash (Low)` | older Flash generation, still served — prefer 3.7 |
+| `Gemini 3.5 Flash (Medium)` | older Flash generation, still served — prefer 3.7 |
+| `Gemini 3.5 Flash (High)` | older Flash generation, still served — prefer 3.7 |
 | `Gemini 3.1 Pro (Low)` | cheaper Pro pass for medium reasoning |
-| `Gemini 3.1 Pro (High)` | wrapper default; hard reasoning, plan critique, architecture review |
+| `Gemini 3.1 Pro (High)` | hard reasoning, plan critique, architecture review (slower, deeper) |
 | `Claude Sonnet 4.6 (Thinking)` | a Claude second opinion through the same subscription |
 | `Claude Opus 4.6 (Thinking)` | strongest Claude reasoning available via `agy` |
 | `GPT-OSS 120B (Medium)` | an open-weights cross-check / diversity pass |
@@ -89,10 +95,12 @@ AGY_HARD_TIMEOUT=8m agy-run "..."             # hard wall-clock cap via timeout(
 agy-run "..." -- --add-dir .                  # passthrough agy flags (never a permission widener)
 ```
 
-`agy` is **headless-only** here (`-p`/`--print`) and there is **no JSON output mode** in v1.0.13 — you
-get plain text. If you need structure, ask for Markdown with explicit headings and validate it
+`agy` is **headless-only** here (`-p`/`--print`); v1.1.13 adds `--output-format json|stream-json`,
+and text stays the wrapper default — JSON can ride passthrough (`-- --output-format json`) but with
+no first-class parsing/validation (adoption is a backlog item). If you need structure, ask
+for Markdown with explicit headings and validate it
 yourself. Wrapper inputs: first argument is the prompt (`text`, `-` for stdin, or `@file`);
-`AGY_MODEL` (default `Gemini 3.1 Pro (High)`); `AGY_TIMEOUT` → `--print-timeout` (default `5m`);
+`AGY_MODEL` (default `Gemini 3.7 Flash (High)`); `AGY_TIMEOUT` → `--print-timeout` (default `5m`);
 `AGY_HARD_TIMEOUT` → hard `timeout(1)` wall-clock cap (default = `AGY_TIMEOUT`); extra `agy` flags
 after `--`. Full detail: [`references/models-and-flags.md`](references/models-and-flags.md).
 
@@ -154,7 +162,7 @@ release). `agy-review … --nonce <n>` is the plain-argument equivalent
 (one seam; flag and a non-empty env must agree, a disagreeing pair refuses pre-spend) — the lane
 for hosts whose dispatch policy has no env-prefix form.
 
-Frontier default `Gemini 3.1 Pro (High)`; **any** model is allowed (a sub-frontier one earns a
+Frontier default `Gemini 3.7 Flash (High)`; **any** model is allowed (a sub-frontier one earns a
 silenceable `AGY_PROBE=1` advisory). An oversized `code` review is **DELIVERED, not refused**: the
 change set is cut into under-cap parts, fed over continuation turns and reviewed in a final turn, and
 the answer must reproduce a line the wrapper picked from each part — a missing or wrong echo is a
@@ -190,9 +198,9 @@ without an explicit `--add-dir`, so ground a review **self-contained** via `agy-
 rather than relying on `agy` to read the change set. Re-runnable from a project root (use a cheap model):
 
 ```bash
-AGY_MODEL="Gemini 3.5 Flash (Low)" agy-run \
+AGY_MODEL="Gemini 3.7 Flash (Low)" agy-run \
   "Read the cwd context file and state the dialogue language plus one Hard Constraint, in two lines."
-AGY_MODEL="Gemini 3.5 Flash (Low)" agy-run \
+AGY_MODEL="Gemini 3.7 Flash (Low)" agy-run \
   "Without me pointing you at any file, name a project-specific skill under .agents/skills/ here and cite its path."
 ```
 
@@ -241,15 +249,16 @@ checklist, prompt templates, output handling). Essentials:
 - Subdirectory `CLAUDE.md` files are **not** auto-loaded by `agy` (only the cwd context file +
   `.agents/skills/`). Put cross-cutting rules in the root context file, or include local rules in the
   prompt when they matter.
-- **No JSON output** and **no `agy inspect`** in v1.0.13 — parse text; there is no machine-readable
-  introspection.
+- **Text is the wrapper default** — the CLI's 1.1.x `--output-format json|stream-json` can ride
+  passthrough but with no first-class parsing/validation (adoption is backlog) — and there is
+  **no `agy inspect`**: no machine-readable introspection.
 - Model names must match the `agy models` display strings **exactly**.
 - **Quota is finite.** Heavy use of Pro/Claude models can exhaust the subscription; prefer Flash for
   cheap work.
 - **A run can't hang forever.** The wrapper caps `agy` with `timeout(1)` (`AGY_HARD_TIMEOUT`,
   default = `AGY_TIMEOUT`) because `agy`'s own `--print-timeout` is **not** a reliable wall-clock
   kill (a run was seen surviving 32 min past a 10m `--print-timeout`). A heavy `--add-dir` agentic
-  prompt on the slowest model (`Gemini 3.1 Pro (High)`) can run unbounded — prefer a faster model or
+  prompt on a slow model (e.g. `Gemini 3.1 Pro (High)`) can run unbounded — prefer a faster model or
   a **self-contained prompt** (no `--add-dir`); an "exceeded the hard cap" error is the guard firing.
 - `agy` output is plain text and may be incomplete or out of date — treat it as advisory until the
   main agent verifies it.

package/bridges/antigravity-cli-bridge/bin/agy-review.sh

@@ -35,7 +35,7 @@
 #   agy-review --conversation <id> [--decided @f] [--focus "…"]   # resume a specific conversation
 #
 # Environment (every optional var has an explicit default so a no-env run is safe under set -u):
-#   AGY_MODEL                default "Gemini 3.1 Pro (High)"; ANY model allowed (advisory warn off-frontier).
+#   AGY_MODEL                default "Gemini 3.7 Flash (High)"; ANY model allowed (advisory warn off-frontier).
 #                            Set empty (AGY_MODEL=) to drop --model and use agy's settings.json.
 #   AGY_HARD_TIMEOUT         default 30m  (duration string; the timeout(1) hard cap via agy-run)
 #   AGY_TIMEOUT              default = AGY_HARD_TIMEOUT (agy's soft --print-timeout)
@@ -322,11 +322,11 @@ aw_resolve_timeout_bin() {
   printf '%s' "$bin"
 }
 
-DEFAULT_AGY_REVIEW_MODEL="Gemini 3.1 Pro (High)"
+DEFAULT_AGY_REVIEW_MODEL="Gemini 3.7 Flash (High)"
 # Review-receipt identity (AD-038). AW_BRIDGE_VERSION mirrors this bridge's SKILL.md/capability.json
 # version (drift-guarded by agy-review.test.mjs against capability.json).
 AW_RECEIPT_BACKEND="agy"
-AW_BRIDGE_VERSION="5.1.1"  # aw-version-anchor
+AW_BRIDGE_VERSION="5.2.0"  # aw-version-anchor
 # `-` not `:-` so an EXPLICIT empty AGY_MODEL= survives (drop --model, use settings.json — agy.sh:52).
 AGY_MODEL="${AGY_MODEL-$DEFAULT_AGY_REVIEW_MODEL}"
 # D5 control-byte screen — IMMEDIATELY after resolution, BEFORE the off-frontier advisory (or any
@@ -335,8 +335,9 @@ if [[ "$AGY_MODEL" == *[$'\x01'-$'\x1f'$'\x7f']* ]]; then
   echo "error: AGY_MODEL contains control bytes — fix the setting (env or bridge-settings.conf) and re-run." >&2
   exit 2
 fi
-# Frontier review models. ANY model is allowed; a sub-frontier one only earns a soft, silenceable warning.
-FRONTIER_SET=("Gemini 3.1 Pro (High)" "Claude Opus 4.6 (Thinking)" "Claude Sonnet 4.6 (Thinking)")
+# Frontier review models. ANY model is allowed; a sub-frontier one only earns a soft, silenceable
+# warning. Gemini 3.7 Flash (High) is asserted frontier-grade (fork (a), maintainer 2026-08-14).
+FRONTIER_SET=("Gemini 3.7 Flash (High)" "Gemini 3.1 Pro (High)" "Claude Opus 4.6 (Thinking)" "Claude Sonnet 4.6 (Thinking)")
 
 # Duration-string timeouts (NOT codex's bare seconds): agy-run forwards a duration to --print-timeout,
 # and the timeout(1) hard cap is a duration too — never numerically compared, so 30m vs 2h is fine.

package/bridges/antigravity-cli-bridge/bin/agy-review.test.mjs

@@ -285,7 +285,16 @@ describe('agy-review.sh — model policy advisory (1)', () => {
     rmSync(sb.home, { recursive: true, force: true });
     assert.equal(r.status, 0, r.stderr);
     assert.doesNotMatch(r.stderr, /non-frontier model/);
-    assert.match(r.argv, /Gemini 3\.1 Pro \(High\)/, 'the frontier default reaches agy');
+    assert.match(r.argv, /Gemini 3\.7 Flash \(High\)/, 'the frontier default reaches agy');
+  });
+
+  it('an explicit Gemini 3.7 Flash (High) is FRONTIER — no advisory (fork (a), maintainer 2026-08-14)', () => {
+    const sb = makeSandbox();
+    const r = run(sb, { args: ['code', '--facts', 'a tiny fact'], env: { AGY_MODEL: 'Gemini 3.7 Flash (High)' } });
+    rmSync(sb.home, { recursive: true, force: true });
+    assert.equal(r.status, 0, r.stderr);
+    assert.doesNotMatch(r.stderr, /non-frontier model/, 'a FRONTIER_SET member never warns');
+    assert.match(r.argv, /Gemini 3\.7 Flash \(High\)/);
   });
 });
 
@@ -2444,8 +2453,8 @@ describe('agy-review.sh — dispatch-posture labeling (D5)', () => {
     const receipts = readReceipts(sb.repo);
     rmSync(sb.home, { recursive: true, force: true });
     assert.equal(r.status, 0, r.stderr);
-    assert.match(r.stderr, /review posture: model=Gemini 3\.1 Pro \(High\)/, 'the banner states the actual run posture');
-    assert.deepEqual(receipts[0].posture, { model: 'Gemini 3.1 Pro (High)' }, 'banner ↔ receipt parity');
+    assert.match(r.stderr, /review posture: model=Gemini 3\.7 Flash \(High\)/, 'the banner states the actual run posture');
+    assert.deepEqual(receipts[0].posture, { model: 'Gemini 3.7 Flash (High)' }, 'banner ↔ receipt parity');
     assert.deepEqual(Object.keys(receipts[0]), Object.keys(RECEIPT_FIXTURE), 'fixture key set + order');
   });
 
@@ -2498,7 +2507,7 @@ describe('agy-review.sh — dispatch-posture labeling (D5)', () => {
     const receipts = readReceipts(sb.repo);
     rmSync(sb.home, { recursive: true, force: true });
     assert.equal(r.status, 0, r.stderr);
-    assert.match(r.stderr, /^review posture: model=Gemini 3\.1 Pro \(High\) timeout=30m$/m);
+    assert.match(r.stderr, /^review posture: model=Gemini 3\.7 Flash \(High\) timeout=30m$/m);
     assert.deepEqual(Object.keys(receipts[0].posture), ['model'], 'timeout never enters the receipt posture');
   });
 

package/bridges/antigravity-cli-bridge/bin/agy.sh

@@ -17,7 +17,9 @@
 # policy (no plan contract, no auto-approve, no workspace edits) — that is left
 # to whatever flow we design later, which can opt in via passthrough flags.
 #
-# Models (pass the exact display string from `agy models`, or set AGY_MODEL):
+# Model families (compact inventory only; run `agy models` for exact display strings, then pass
+# one via AGY_MODEL):
+#   Gemini 3.7 Flash (Low|Medium|High), Gemini 3.6 Flash (Low|Medium|High),
 #   Gemini 3.5 Flash (Low|Medium|High), Gemini 3.1 Pro (Low|High),
 #   Claude Sonnet 4.6 (Thinking), Claude Opus 4.6 (Thinking), GPT-OSS 120B (Medium)
 #
@@ -237,8 +239,9 @@ if ! command -v agy >/dev/null 2>&1; then
   exit 127
 fi
 
-# `-` (empty) => skip --model and let agy use settings.json; default to Pro.
-AGY_MODEL="${AGY_MODEL-Gemini 3.1 Pro (High)}"
+# `-` (empty) => skip --model and let agy use settings.json; default to Flash (High) — asserted
+# frontier-grade (fork (a), maintainer 2026-08-14).
+AGY_MODEL="${AGY_MODEL-Gemini 3.7 Flash (High)}"
 AGY_TIMEOUT="${AGY_TIMEOUT:-5m}"
 AGY_TIMEOUT="$(aw_effective_timeout AGY_TIMEOUT 5m)"
 # Hard wall-clock cap (defaults to AGY_TIMEOUT). agy's own --print-timeout is NOT a reliable
@@ -355,7 +358,7 @@ set -e
 if [[ $rc -eq 124 || $rc -eq 137 ]]; then
   echo "error: agy exceeded the hard cap AGY_HARD_TIMEOUT=$AGY_HARD_TIMEOUT and was terminated." >&2
   echo "       This usually means a heavy '--add-dir' agentic run, or the slowest model looping." >&2
-  echo "       Retry with a faster model (e.g. AGY_MODEL='Gemini 3.5 Flash (High)') or a" >&2
+  echo "       Retry with a faster model (e.g. AGY_MODEL='Gemini 3.7 Flash (Low)') or a" >&2
   echo "       self-contained prompt without --add-dir. Raise AGY_HARD_TIMEOUT only if the run is healthy." >&2
 fi
 exit $rc

package/bridges/antigravity-cli-bridge/bin/agy.test.mjs

@@ -447,6 +447,30 @@ describe('agy.sh — bridge settings file (bridges 2.3.0)', { concurrency: true
   });
 });
 
+// ── the wrapper's OWN default model (fork (a), round-1 council F3) ────────────────
+describe('agy.sh — default model pin', () => {
+  it('absent AGY_MODEL → the stub argv carries --model Gemini 3.7 Flash (High)', () => {
+    const home = makeSandbox(ARGV_STUB);
+    const argvFile = join(home, 'argv.txt');
+    const r = runWrapper(home, { AGY_STUB_ARGV: argvFile });
+    const argv = readFileSync(argvFile, 'utf8');
+    rmSync(home, { recursive: true, force: true });
+    assert.equal(r.status, 0, r.stderr);
+    assert.match(argv, /^--model$/m, 'the default run passes --model');
+    assert.match(argv, /^Gemini 3\.7 Flash \(High\)$/m, 'the wrapper default is the probed display string');
+  });
+
+  it("explicit AGY_MODEL='' drops --model entirely (settings.json takes over)", () => {
+    const home = makeSandbox(ARGV_STUB);
+    const argvFile = join(home, 'argv.txt');
+    const r = runWrapper(home, { AGY_MODEL: '', AGY_STUB_ARGV: argvFile });
+    const argv = readFileSync(argvFile, 'utf8');
+    rmSync(home, { recursive: true, force: true });
+    assert.equal(r.status, 0, r.stderr);
+    assert.doesNotMatch(argv, /^--model$/m, 'an explicit empty model never emits --model');
+  });
+});
+
 // ── settings surface ⟷ manifest (drift guard, D6) ────────────────────────────────
 // agy-run's --help stays candidate-C (not contract-pinned), but its SETTINGS surface
 // is manifest-pinned like the other three wrappers: the Settings help section and the

package/bridges/antigravity-cli-bridge/capability.json

@@ -3,9 +3,9 @@
   "schema": 1,
   "name": "antigravity-cli-bridge",
   "kind": "execution-backend",
-  "version": "5.1.1",
+  "version": "5.2.0",
   "provides": ["review", "probe"],
-  "posture": { "model": "Gemini 3.1 Pro (High)" },
+  "posture": { "model": "Gemini 3.7 Flash (High)" },
   "roles": {
     "review": {
       "cmd": "agy-review",
@@ -180,7 +180,7 @@
       ],
       "guardrails": [
         { "value": "subscription-only — every *_API_KEY env var is unset before the run", "enforcement": "enforced", "source": "bin/agy.sh" },
-        { "value": "any model is selectable via AGY_MODEL; the default is Gemini 3.1 Pro (High)", "enforcement": "advisory", "source": "bin/agy.sh" },
+        { "value": "any model is selectable via AGY_MODEL; the default is Gemini 3.7 Flash (High)", "enforcement": "advisory", "source": "bin/agy.sh" },
         { "value": "hard wall-clock cap AGY_HARD_TIMEOUT (built-in default 5m)", "enforcement": "enforced", "condition": "only while timeout(1)/gtimeout is on PATH — otherwise the wrapper warns and runs uncapped", "source": "capability.json settings.AGY_HARD_TIMEOUT" },
         { "value": "the prompt rides a single argv — over AGY_MAX_PROMPT_BYTES (120000) the run refuses", "enforcement": "enforced", "source": "bin/agy.sh" },
         { "value": "no review posture, no grounding, no receipt — the reply is raw model output", "enforcement": "advisory", "source": "bin/agy.sh" }

package/bridges/antigravity-cli-bridge/references/driving-agy.md

@@ -18,13 +18,14 @@ edits, verification, and final judgment.
 
 | Task | Model |
 |---|---|
-| Reachability / smoke / "is it wired?" | `Gemini 3.5 Flash (Low)` |
-| Cheap probes, summaries | `Gemini 3.5 Flash (Medium)` |
-| Quick review with a little more effort | `Gemini 3.5 Flash (High)` |
-| Reasoning, plan critique, careful drafting | `Gemini 3.1 Pro (High)` (wrapper default) |
-| Same reasoning, lower quota cost | `Gemini 3.1 Pro (Low)` |
+| Reachability / smoke / "is it wired?" | `Gemini 3.7 Flash (Low)` |
+| Cheap probes, summaries | `Gemini 3.7 Flash (Medium)` |
+| Review, reasoning, careful drafting | `Gemini 3.7 Flash (High)` (wrapper default; asserted frontier-grade) |
+| Slower, deeper reasoning pass | `Gemini 3.1 Pro (High)` |
+| Same Pro reasoning, lower quota cost | `Gemini 3.1 Pro (Low)` |
 | A different engine's opinion | `Claude Sonnet 4.6 (Thinking)`, `Claude Opus 4.6 (Thinking)`, or `GPT-OSS 120B (Medium)` |
 
+The 3.6 / 3.5 Flash families remain served — prefer 3.7 (newest generation at the same tiers).
 Don't reach for Pro by reflex — Flash answers most reachability/probe questions for a fraction of the
 quota.
 
@@ -94,7 +95,7 @@ What it does for you, and what YOU must supply:
   `AGY_REVIEW_ALLOW_ADDDIR` is **RETIRED** (recognized, arms nothing): headless `agy` auto-denies its
   own `read_file`, so the offload it armed could return a confident fabrication with no way to tell.
   The kit never grants that permission — the feed exists so none is needed.
-- **Model:** frontier default `Gemini 3.1 Pro (High)`; any model is allowed (a sub-frontier one earns a
+- **Model:** frontier default `Gemini 3.7 Flash (High)`; any model is allowed (a sub-frontier one earns a
   silenceable `AGY_PROBE=1` advisory). The service can still **stall on large/substantive prompts**
   (Issue-001) — keep reviews **focused**; the hard timeout is the guard.
 - **Posture banner — quote it verbatim.** Every review states its ACTUAL posture on ONE stderr line
@@ -127,9 +128,9 @@ Probe **reachability** from a project root (cheap model) — this is the one pla
 context file is the point of the prompt:
 
 ```bash
-AGY_MODEL="Gemini 3.5 Flash (Low)" agy-run \
+AGY_MODEL="Gemini 3.7 Flash (Low)" agy-run \
   "Read the cwd context file and report the dialogue language plus one Hard Constraint."
-AGY_MODEL="Gemini 3.5 Flash (Low)" agy-run \
+AGY_MODEL="Gemini 3.7 Flash (Low)" agy-run \
   "Without using a file pointer, is there a project-specific planning skill in this repo? Name it and cite its path."
 ```
 

package/bridges/antigravity-cli-bridge/references/models-and-flags.md

@@ -1,14 +1,18 @@
 # `agy` models & flags (reference)
 
 The source of truth is the live binary: `agy --version`, `agy --help`, `agy models`. The tables below
-were captured from **v1.0.13**; if the binary disagrees, the binary wins. The wrapper command is
+were captured from **v1.1.13**; if the binary disagrees, the binary wins. The wrapper command is
 `agy-run`, backed by `bin/agy.sh`.
 
 ## Headless behaviour
 
 Use `-p`, `--print`, or `--prompt` to run one non-interactive prompt and print the text response. The
-wrapper always uses headless `-p`. **There is no JSON output mode in v1.0.13** — ask for Markdown,
-bullets, tables, or fenced blocks when the caller needs structure, then validate the text yourself.
+wrapper always uses headless `-p`. v1.1.13 adds `--output-format text|json|stream-json` and
+`--json-schema` (structured output); **text stays the wrapper default** — raw passthrough
+(`agy-run "…" -- --output-format json`) is possible but rides with NO first-class parsing or schema
+validation (first-class adoption is a separate backlog item). When the caller needs structure
+through the wrapper, ask for Markdown, bullets, tables, or fenced blocks, then validate the text
+yourself.
 
 ## Wrapper contract
 
@@ -30,7 +34,7 @@ Environment:
 
 | Var | Default | Effect |
 |---|---|---|
-| `AGY_MODEL` | `Gemini 3.1 Pro (High)` | model display string; set empty (`AGY_MODEL=`) to drop `--model` and let `agy` use `settings.json` |
+| `AGY_MODEL` | `Gemini 3.7 Flash (High)` | model display string; set empty (`AGY_MODEL=`) to drop `--model` and let `agy` use `settings.json` |
 | `AGY_TIMEOUT` | `5m` | value passed to `--print-timeout` |
 | `AGY_HARD_TIMEOUT` | `= AGY_TIMEOUT` | hard `timeout(1)` wall-clock cap (a duration string) |
 | `AGY_MAX_PROMPT_BYTES` | `120000` | single-argv byte ceiling. `agy` takes the prompt as ONE `-p` argv; past `MAX_ARG_STRLEN` (~131072) `execve` fails with a cryptic `Argument list too long`. The wrapper measures the resolved `-`/`@file` prompt and fails loud over the ceiling. A huge **literal** `agy-run "<huge>"` fails at the wrapper's own `exec`, so route large prompts via `-`/`@file`. |
@@ -55,7 +59,7 @@ agy-review --continue | --conversation <id>   [--decided @f] [--focus "…"]   #
 
 | Var | Default | Effect |
 |---|---|---|
-| `AGY_MODEL` | `Gemini 3.1 Pro (High)` | frontier default; **any** model is allowed — a sub-frontier one earns a silenceable advisory (quality-first, not a gate) |
+| `AGY_MODEL` | `Gemini 3.7 Flash (High)` | frontier default (fork (a), 2026-08-14); **any** model is allowed — a sub-frontier one earns a silenceable advisory (quality-first, not a gate) |
 | `AGY_PROBE` | `0` | `1` silences the off-frontier model advisory AND lets `code` run without `--facts` (an ungrounded probe never attests — its receipt is probe-marked) |
 | `AGY_REVIEW_MAX_TOTAL_BYTES` | `240000` | the ceiling on the SUM of all outgoing prompt bytes an oversized `code` review's chunked feed may send; checked BEFORE the first turn is spent |
 | `AGY_REVIEW_ALLOW_ADDDIR` | `0` | **RETIRED** — recognized so an existing settings line never warns as unknown, but it arms nothing. An oversized `code` review is a chunked feed with a per-part delivery proof; the `--add-dir` offload it armed could not be verified (headless `agy` auto-denies `read_file`) |
@@ -72,11 +76,17 @@ Pass the **exact display string** from `agy models`, or set `AGY_MODEL`.
 
 | Model string | Practical use |
 |---|---|
-| `Gemini 3.5 Flash (Low)` | lowest-cost smoke tests and simple rewrites |
-| `Gemini 3.5 Flash (Medium)` | cheap probes, fast summaries, context-reachability checks |
-| `Gemini 3.5 Flash (High)` | fast review when a little more reasoning effort is useful |
+| `Gemini 3.7 Flash (Low)` | lowest-cost smoke tests, cheap probes, simple rewrites (newest Flash) |
+| `Gemini 3.7 Flash (Medium)` | fast summaries, context-reachability checks |
+| `Gemini 3.7 Flash (High)` | wrapper + review default — asserted frontier-grade (fork (a)) |
+| `Gemini 3.6 Flash (Low)` | previous Flash generation, still served — prefer 3.7 |
+| `Gemini 3.6 Flash (Medium)` | previous Flash generation, still served — prefer 3.7 |
+| `Gemini 3.6 Flash (High)` | previous Flash generation, still served — prefer 3.7 |
+| `Gemini 3.5 Flash (Low)` | older Flash generation, still served — prefer 3.7 |
+| `Gemini 3.5 Flash (Medium)` | older Flash generation, still served — prefer 3.7 |
+| `Gemini 3.5 Flash (High)` | older Flash generation, still served — prefer 3.7 |
 | `Gemini 3.1 Pro (Low)` | cheaper Pro pass for medium reasoning |
-| `Gemini 3.1 Pro (High)` | wrapper default; hard reasoning, plan critique, architecture review |
+| `Gemini 3.1 Pro (High)` | hard reasoning, plan critique, architecture review (slower, deeper) |
 | `Claude Sonnet 4.6 (Thinking)` | cross-vendor reasoning comparison |
 | `Claude Opus 4.6 (Thinking)` | expensive deep critique when the user wants another high-end pass |
 | `GPT-OSS 120B (Medium)` | open-weights-style comparison / diversity pass |
@@ -84,11 +94,11 @@ Pass the **exact display string** from `agy models`, or set `AGY_MODEL`.
 Examples:
 
 ```bash
-AGY_MODEL="Gemini 3.5 Flash (Medium)" agy-run "Read AGENTS.md and report one Hard Constraint."
+AGY_MODEL="Gemini 3.7 Flash (Low)" agy-run "Read AGENTS.md and report one Hard Constraint."
 AGY_MODEL="Claude Sonnet 4.6 (Thinking)" AGY_TIMEOUT=10m agy-run @review-prompt.md
 ```
 
-## Flags (from `agy --help`, v1.0.13)
+## Flags (from `agy --help`, v1.1.13)
 
 | Flag | Meaning | Notes |
 |---|---|---|
@@ -102,12 +112,19 @@ AGY_MODEL="Claude Sonnet 4.6 (Thinking)" AGY_TIMEOUT=10m agy-run @review-prompt.
 | `--dangerously-skip-permissions` | auto-approve all tool permissions | avoid by default; use only with explicit user approval |
 | `--sandbox` | run with terminal restrictions enabled | prefer when delegating a prompt that might trigger tool/terminal work |
 | `--log-file <path>` | override the CLI log-file path | keep logs secret-free and out of committed artifacts |
+| `--output-format <fmt>` | print-mode output: `text` (default), `json`, `stream-json` | NEW in 1.1.x; not wrapper-adopted (backlog) |
+| `--json-schema <s\|path>` | enforce structured output (stream-json final result) | NEW in 1.1.x; not wrapper-adopted (backlog) |
+| `--effort <low\|medium\|high>` | reasoning effort for the session | NEW in 1.1.x; the display strings already carry an effort tier — the wrapper keeps model selection in ONE place (`AGY_MODEL`) |
+| `--mode <m>` | agent execution mode (`accept-edits`, `plan`) | NEW in 1.1.x; not used by the wrapper |
+| `--agent` / `--project <id>` / `--new-project` | agent + project selection for the session | NEW in 1.1.x; not used by the wrapper |
+| `--disable-slash-commands` | disable slash command/skill expansion in print mode | NEW in 1.1.x; not used by the wrapper |
 
-## Subcommands (v1.0.13)
+## Subcommands (v1.1.13)
 
-`changelog`, `help`, `install`, `models`, `plugin` / `plugins`, `update`.
+`agent` / `agents`, `changelog`, `help`, `install`, `models`, `plugin` / `plugins`, `update`.
 
-**Not available in v1.0.13:** any JSON output mode, and any `agy inspect`. Output is plain text.
+**Still not available in v1.1.13:** any `agy inspect`. Wrapper output stays plain text (the
+`--output-format` lane is not adopted here — see the backlog row).
 
 ## Project-context flags
 

package/bridges/antigravity-cli-bridge/setup/README.md

@@ -9,7 +9,7 @@ works in any project.
 ```bash
 curl -fsSL https://antigravity.google/cli/install.sh | bash
 export PATH="$HOME/.local/bin:$PATH"   # add to ~/.bashrc / ~/.zshrc to persist
-agy --version                          # expect 1.0.13 or newer
+agy --version                          # expect 1.1.13 or newer
 ```
 
 - The binary is **`agy`** (not `antigravity`); it installs to `~/.local/bin/agy`.
@@ -59,12 +59,13 @@ agy --version
 echo "say OK" | agy-run -
 ```
 
-Expected: the version prints (`1.0.13` or newer), then a short reply containing `OK`. If `agy-run`
+Expected: the version prints (`1.1.13` or newer), then a short reply containing `OK`. If `agy-run`
 reports `'agy' not found`, fix your `PATH` (step 1). If it asks you to sign in, complete step 2.
 
 ## Notes
 
-- `agy-run` is headless and plain-text only; there is no JSON output mode.
+- `agy-run` is headless and text by default; the CLI's 1.1.x `--output-format json` can ride
+  passthrough (`-- --output-format json`) but the wrapper adds no parsing/validation.
 - `AGY_MODEL` selects the exact model display string; `AGY_TIMEOUT` controls `--print-timeout`.
 - Extra `agy` flags go after `--`, e.g. `agy-run @prompt.md -- --add-dir .`.
 - Re-run interactive `agy` only when the OAuth token expires or the account changes.

package/capability.json

@@ -3,7 +3,7 @@
   "schema": 1,
   "name": "agent-workflow-kit",
   "kind": "composition-root",
-  "version": "5.6.0",
+  "version": "5.8.0",
   "provides": [],
   "roles": {},
   "detect": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sabaiway/agent-workflow-kit",
-  "version": "5.6.0",
+  "version": "5.8.0",
   "description": "Portable, cross-agent memory & workflow for AI coding agents — Claude Code, Codex, Cursor, Devin Desktop. One command deploys an AGENTS.md entry point + docs/ai context with cap/archive/index enforcement into any repo.",
   "keywords": [
     "ai-agents",