chore(cli-version): verify agy against 1.2.2

[kaizhou-lab]

Moves VERIFIED_AGY_VERSION from 1.2.0 to 1.2.2. The updater went straight from 1.2.0 to 1.2.2, so the triage covers both 1.2.1 and 1.2.2.

Gate	Result
A — contract	DEGRADED — agy publishes no protocol schema; gate B carries the weight
B — live e2e	PASS 7/7, 150.92s
C — release notes	CLEAR

Gate B ran against a manifest download whose sha512 was checked before it executed; the log reports only version=1.2.2, and the binary was byte-identical before and after (mtime=11:02:31 size=180089984). The machine's own agy stayed on 1.1.18.

Gate C was read from the candidate binary — the web changelog has neither 1.2.1 nor 1.2.2 (exact match, 0 hits each).

Flag surface: unchanged

--help and models --help are byte-identical 1.2.0 → 1.2.2, diffed against the captures stored with the previous record. All nine flags build_argv emits are present.

Everything on our surface is a fix

• Transient 502/503/504/per-minute 429 and mid-stream interruptions now retry in-process with backoff while preserving completed tool call outputs, with clear user-facing messages when unrecovered (1.2.1). Directly our path — and the preserved outputs matter, because a retry that discarded them would replay tool cards.
• MCP schema validation relaxes back to honouring open object schemas ({"type":"object"}, additionalProperties: true) instead of rejecting undeclared arguments (1.2.1). This undoes the over-strictness 1.1.27 introduced. Gate B drives an MCP tool call and it passed.
• view_file now rejects non-UTF-8 binary files and files over 100 MB with a clear error instead of overflowing the context window (1.2.2). That surfaces as a tool ERROR step, which our card already renders.
• Gemini-API-key sessions no longer drop prior-turn thinking blocks; conversations without a workspace no longer inherit another session's paths (we always pass --new-project + --add-dir, so that one cannot reach us).

One item renames tools — plugin-bundled MCP servers are now namespaced <plugin>_<server> — but only for plugin-bundled servers, which we do not use. Ours are provisioned through our own path, and the MCP test is unchanged.

Not our surface

excludeDefaultComponents in Markdown agent frontmatter (we never pass --agent), the --continue fallback (we resume by explicit --conversation <id>), deprecated unsandboxed permission-rule warnings (we pass --dangerously-skip-permissions, not rules), inline-mode flashes, Remote Control companion UI, --sandbox status line, image zoom keys, /resume cache speed, a step-cache goroutine leak, deleted-conversation SQLite recreation, artifact-review path matching.

A correction to the previous record

View release anchors on the web page are not CLI-only — the Hub uses them too, and Hub versions such as 1.21.9 / 1.22.2 match a View release 1\.[0-9]+\.[0-9]+ pattern. The only reliable web check is an exact match on the candidate, closing quote included:

grep -c 'View release 1.2.2"' <page>

Tests

Pinned assertions moved with the constant, including the literal verified-release case and the 1.1.29 older-than-1.2.x boundary that guards component-wise comparison. cargo test -p aionui-session --lib cli_version: 14/14. Clippy clean, fmt clean.

Record: ~/aion/protocols/samples/antigravity-cli/1.2.2/

Constants and record only — no source change.