[1/5] Plan SDK evolution demo reliability repairs - #51
Merged
Conversation
ebarti
marked this pull request as ready for review
July 28, 2026 16:48
ebarti
added a commit
that referenced
this pull request
Jul 28, 2026
## Summary - treat `uv.lock` as the authoritative SDK baseline during explicit candidate inspection - isolate locked baselines when the matching SDK is absent or the ambient environment has drifted - keep non-opt-in runs honest by recording the actual ambient version instead of stamping it as locked - convert isolated API snapshot setup, install, execution, timeout, and malformed-output failures into bounded evidence ## Stack - Depends on #51 - This is layer 2 of 5 in the SDK evolution demo reliability stack ## Review boundary This layer repairs baseline provenance and snapshot collection only. Behavior-probe subprocess failures and the final `fail > incomplete > changed > pass` assessment are intentionally implemented together in the next layer so incomplete evidence cannot temporarily appear green. ## Validation - `PYTHONPATH=. .venv/bin/python -m pytest -q` — 421 passed, 12 skipped - `.venv/bin/ruff check .` - `.venv/bin/mypy` - `uv lock --check` - `git diff --check`
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.
Summary
mainWhy
The Agent SDK stages execute successfully, but the documented evolution workflow can label ambient import failures as locked SDK evidence, collapse incomplete probes into a passing headline, and permanently fail CLI-binary snapshots through the wrong module name. The repair needs to preserve the explicit candidate-inspection and credential-scrubbing boundary while making the supported command actionable.
Stack
This is PR 1 of 5 and contains planning documentation only. The implementation branches will be based in order on this branch:
Validation
git diff --cached --checkorigin/mainat2e7e4c3