* test(agent): cover antigravity in fakeagent and the e2e user journey
* no-mistakes(document): Add antigravity to agent lists, doctor example, and fakeagent doc comment
* no-mistakes(document): Add antigravity to agent Values and auto resolution order in docs
* feat(recordfixture): capture antigravity fixtures via the owned e2e-record workflow
* no-mistakes(review): Assert Antigravity recorder argv forwarding; focused tests pass
* fix(recordfixture): stage agy captures atomically and contain the process tree
* no-mistakes(review): Test plain fixture replay path by splitting TestRunAgyReplaysRecordedFixture into structured/plain subtests
* no-mistakes(review): Validate Antigravity captures and replay configured fixtures reliably
* no-mistakes(document): Document Antigravity capture and replay behavior
* no-mistakes: apply CI fixes
* fix(recordfixture): expect cmd-exe quote escaping in agy argv test; dedupe antigravity docs
The windows-core run at 0ba9bd95 failed TestCaptureAgyPlacesForwardedFlagsBeforePromptAndSchemaLast
because the fake .cmd agent records Go's literal backslash-quote escaping:
cmd.exe %~1 expansion does not undo it, while real agy parses argv with
CommandLineToArgvW and sees the unescaped JSON. Assert the escaped schema
arg on Windows with a comment explaining the harness-only artifact.
After rebasing onto main (#812), agents.md carried two Antigravity adapter
sections and two supported-agents table rows. Keep one of each, reflecting
final capabilities: session resume via --conversation and
terminal-authoritative result precedence (structured_output >
result.response > stream deltas).
* fix(recordfixture): reject any non-SUCCESS agy result during capture validation
validateAgyCapture only inspected the final result status, so a capture
containing an ERROR result followed by SUCCESS validated even though the
production replay parser treats any ERROR result as fatal. Fail fast on
the first non-SUCCESS result and require at least one result event.
Gurkirat Khaira
5dbbb3aaec