[2/5] Observe locked SDK baselines accurately - #52
Merged
Conversation
ebarti
marked this pull request as ready for review
July 28, 2026 16:48
Base automatically changed from
agent/sdk-evolution-demo-reliability-plan
to
main
July 28, 2026 17:53
ebarti
added a commit
that referenced
this pull request
Jul 28, 2026
## Summary - parse resolver updates once as exact package/from/to transitions and reuse them across collection and deterministic gates - derive canonical locked-baseline expectations from collected package evidence, including no-update runs - contain isolated behavior setup, install, execution, timeout, and malformed-output failures as bounded structured evidence - compute `fail > incomplete > changed > pass` from raw probes, diffs, full probe pairing, and trusted expectations - recompute the canonical assessment for reports and implementation gates instead of trusting a cached headline - persist `behavior_summary.json`, include it in the current-state manifest, and surface snapshot/behavior errors and reasons in the Markdown report - require exact API-diff transitions and fail closed on missing, malformed, contradictory, incomplete, or breaking behavior evidence ## Stack - Depends on #52 - This is layer 3 of 5 in the SDK evolution demo reliability stack ## Review notes The layer received a two-pass correctness review. Review findings covered drifted no-update baselines, contradictory cached summaries, malformed nested details, failure precedence, partial probe sets, empty self-declared expectation scope, and real breaking-payload coverage; all were repaired and re-reviewed with no remaining actionable findings. ## Validation - `PYTHONPATH=. .venv/bin/python -m pytest -q` — 449 passed, 12 skipped - focused SDK evolution suite — 90 passed - `.venv/bin/ruff check .` - `.venv/bin/mypy` - `uv lock --check` - `git diff --check` Security-diff scans were intentionally not part of this phase review.
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
uv.lockas the authoritative SDK baseline during explicit candidate inspectionStack
Review boundary
This layer repairs baseline provenance and snapshot collection only. Behavior-probe subprocess failures and the final
fail > incomplete > changed > passassessment 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/mypyuv lock --checkgit diff --check