Run SDK evolution across all vendor packages#9
Closed
ebarti wants to merge 8 commits into
Closed
Conversation
Owner
Author
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
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.
Summary
Runs the local SDK evolution workflow across the full default vendor package set instead of only
google-antigravity.This PR supersedes the narrower Antigravity-only proof by carrying forward the candidate API diff hardening and adding an all-package report/lock update.
Documentation Added
Adds
docs/sdk-evolution-agent-design.mdbefore implementing changelog and behavior-probe changes. The design document defines:docs/sdk-evolution-agent.mdnow links to this design doc from the user-facing run guide.Agent-Generated Evidence
The committed report was generated through
agent-runtime-kitusing the realantigravity-agent-sdkruntime from a temporary pre-update checkout, with no--packagefilter:Committed report:
The resolver found two update candidates:
claude-agent-sdk:0.2.96 -> 0.2.106google-antigravity:0.1.2 -> 0.1.4Codex package status:
openai-codex: already current at0.1.0b3openai-codex-cli-bin: no resolver update; the lock remains on0.137.0a4, which is newer than PyPI's stablelatestmetadata fieldImplementation
uv.lockforclaude-agent-sdkto0.2.106.google-antigravity 0.1.4.uv lock --dry-run -P ...for candidate API snapshots, avoiding false downgrade diffs when PyPI stablelatestis lower than a locked prerelease.Verification
env -u UV_EXCLUDE_NEWER uv run ruff check .env -u UV_EXCLUDE_NEWER uv run mypyenv -u UV_EXCLUDE_NEWER uv run pytest(99 passed, 3 skipped)env -u UV_EXCLUDE_NEWER uv lock --checkenv -u UV_EXCLUDE_NEWER uv lock --dry-run -P claude-agent-sdk -P openai-codex -P openai-codex-cli-bin -P google-antigravity(No lockfile changes detected)env -u UV_EXCLUDE_NEWER AGENT_RUNTIME_KIT_LIVE=1 AGENT_RUNTIME_KIT_LIVE_PROVIDER=all uv run pytest tests/test_live_smoke.py -q -s(3 passed)Antigravity Comparison With PR #8
Compared with PR #8 (
sdk-evolution-proof-20260622):src/agent_runtime_kit/adapters/antigravity.py: no diff.tests/test_antigravity_adapter.py: no diff.google-antigravitylock state: unchanged at0.1.4.google-antigravityAPI diff artifact: identical to PR Update google-antigravity from SDK evolution report #8.Safety
Codex Model Policy
Codex-backed SDK evolution stages now explicitly run with
model=gpt-5.5andreasoning_effort=xhigh. The override is scoped tocodex-agent-sdkonly; Claude and Antigravity keep provider-native model selection becausegpt-5.5is not a portable model id across adapters.