chore(cli-version): verify agy against 1.2.3 - #992
Merged
Merged
Conversation
Gate B: 7/7, 419.10s, against a manifest download whose sha512 was checked before it ran. The log reports only version=1.2.3, and the binary was byte-identical before and after (mtime 08:48:23, size 181740432). On the runtime: 419s against a normal 140-255s. Per-test against the previous night's 1.2.2 run, team_mcp went 74s -> 213s and tool_card 13s -> 35s -- a ~2.8x slowdown that is UNIFORM across unrelated tests, the shape provider latency has taken before (09-03, 09-04). agy cannot be A/B tested, so whether 1.2.3 is itself slower is not established and is not claimed. All seven passed; not a veto. Recorded in the gate-c-manual so the next run on this version can settle it: back to normal means the provider, still slow means a real data point. Gate C: CLEAR, read from the candidate binary's own `agy changelog`; the web page does not have 1.2.3. Small release. The one item that could shift behaviour -- per-request tool-choice constraints now translated into native backend function-calling -- is internal to agy's model calls; gate B's tool and MCP paths ran and passed. Subagent enable_mcp_tools inheritance, /copy btw, /hooks plugin listing and feedback-prompt timing are not our surface. --help and models --help are byte-identical 1.2.2 -> 1.2.3, diffed against the captures stored with the previous record. Record: ~/aion/protocols/samples/antigravity-cli/1.2.3/
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves
VERIFIED_AGY_VERSIONfrom 1.2.2 to 1.2.3.Gate B ran against a manifest download whose sha512 was checked before it executed; the log reports only
version=1.2.3, and the binary was byte-identical before and after (mtime=08:48:23 size=181740432). The machine's own agy stayed on 1.1.18. Gate C was read from the candidate binary — the web changelog does not carry 1.2.3 (exact match, 0 hits).On the runtime — recorded, not attributed
419s against a normal 140–255s. Per-test against the previous night's 1.2.2 run:
team_mcp_tools_call_and_runtime_envtool_card_is_renderableA ~2.8× slowdown that is uniform across unrelated tests — the shape provider latency has taken before (09-03, 09-04), not a single slow code path. But agy cannot be A/B tested (running an older copy self-updates it), so whether 1.2.3 is itself slower is not established and is not claimed. The only 1.2.3 item that could plausibly alter model-call patterns is the tool-choice translation below; that is a hypothesis with no way to test it here. All seven passed; not a veto. The next run on this same version settles it either way.
Flag surface: unchanged
--helpandmodels --helpbyte-identical 1.2.2 → 1.2.3, diffed against the stored captures.Triage — small release, nothing on a contract we drive
any,required, and named functions) into native backend function-calling configurations." Internal to how agy talks to its model backend. It can change which tools the model reaches for; gate B's tool and MCP paths ran and passed.enable_mcp_tools: truenow inherit the parent's MCP servers — subagent definitions are agy-side config we do not author./copy btw,/hookslisting plugin-bundled hooks, proactive-feedback prompt timing — interactive TUI.Tests
Pinned assertions moved with the constant.
cargo test -p aionui-session --lib cli_version: 14/14. Clippy clean, fmt clean.Record:
~/aion/protocols/samples/antigravity-cli/1.2.3/Constants and record only — no source change.