feat(antigravity): update placemat for Antigravity CLI v1.2.14

[dommango]

What this changes

Daily sync run: the placemat was at v1.2.12, the vendor CLI panel now lists v1.2.14, so this syncs the two intervening releases (v1.2.13, v1.2.14) into antigravity/index.html and antigravity/changelog.html.

• queuedMessages (new card-settings row, class="unverified") — 1.2.14's new follow-up-message setting, absent from the cli/reference settings table
• --json-schema <schema> (card-cli) — noted 1.2.14's startup validation hardening (rejects plain text, bare type names, missing files; exit code 1)
• agy remote-control (card-cli) — noted 1.2.14's systemd-free remote-control start support on Linux
• /resume (card-slash-core) — noted 1.2.14's faster long-conversation loading and its missing-history-step resume fix
• /artifact (card-slash-tools) — noted 1.2.13's clarified viewer m hint labeling

Release-tag, print-head and footer sync date bumped to v1.2.14 / 2026-09-30. sources.json's inventory.fetched bumped to today; no new verified inventory entries (queuedMessages stays outside the inventory list since it isn't yet in cli/reference, same treatment as the existing /effort and --remote-control unverified rows).

Internal-only items from these two releases (rate-limit retry delay tuning, redraw rendering efficiency, narrow-terminal text wrapping, conversation-title attachment handling, sign-in ToS appeal link, cursor-drift/hang fixes) aren't tied to any placemat row, so per AGENTS.md ("the eight cards are a fixed set of headings, not eight quotas to fill") they're omitted from both the cards and the changelog, consistent with how prior syncs (e.g. v1.2.12) handled similarly out-of-scope release-note items.

Type

• Content correction (wrong/outdated/missing entry)

Checklist

• I read AGENTS.md's Style Guide and Content Rules
• node tests/placemat.test.js antigravity passes locally (54 passed, 0 failed)
• node scripts/build-changes.js --all --check passes locally (generated files are fresh)
• No versions/*.html files were edited
• No hand-edited changes.json or feed.xml — regenerated via node scripts/build-changes.js antigravity
• Every new/changed row is sourced from antigravity.google/docs/changelog's hidden CLI panel and antigravity.google/docs/cli/reference — no sibling placemat consulted
• queuedMessages carries class="unverified" (not yet in cli/reference's settings table); everything else is changelog/cli/reference-confirmed
• New row (i-cfg-queued-messages) has a matching id/.row-link permalink
• Only antigravity/ is touched

Source

• https://antigravity.google/docs/changelog (id="panel-cli", id="rel-cli-1.2.13" / id="rel-cli-1.2.14")
• https://antigravity.google/docs/cli/reference (settings table — confirms queuedMessages is absent)

🤖 Generated with Claude Code

https://claude.ai/code/session_011eR9RzdJorRAZ92r8Ckygw

---

Generated by Claude Code

[dommango]

Merge-gate review (code-review skill, medium effort)

Scope: antigravity/{changelog.html,changes.json,feed.xml,index.html,sources.json} — content/data only, no JS/logic changes. node tests/placemat.test.js antigravity (54/54) and node scripts/build-changes.js --all --check both pass.

Two findings came back from the review pass:

1. --json-schema note (index.html:295) — flagged as an unsourced claim that the flag now also requires the schema's root to be "type": "object". Verified against the primary vendor source (antigravity.google/docs/changelog, id="rel-cli-1.2.14" CLI panel article, Improvements list): the release note text reads "...these inputs, and any schema whose root is not "type": "object", now fail at startup with an error and exit code 1." The note is accurate; changelog.html's own entry for this item is just a shorter condensation (house style) and doesn't restate every clause, which is what the reviewer (without a fetch of the live vendor page) read as unsourced. Not actioned — false positive.
2. queuedMessages settings-card grouping (index.html:334) — placed in "Appearance & editing", which otherwise holds only theme/editor-mode rows. Fair point, but card-settings only has 3 groups (Appearance & editing / Safety & permissions / Notifications & account) and none of them are a clean fit for a turn-interruption setting; "Notifications & account" (notifications, showTips, useG1Credits, enableTelemetry) fits worse. Kept it in Appearance & editing alongside the other turn/output-behavior settings (verbosity, runningLightSpeed) rather than invent a fourth group for one unverified row. Minor organizational nit, not a correctness defect — does not rise to CRITICAL/HIGH.

No CRITICAL/HIGH findings stand. Both CI checks (html5validator, placemat tests (zero deps)) are green on the head commit. Proceeding to merge per PIPELINE.md Step 10.

---

Generated by Claude Code