chore(vcr-mem): re-validate scry consumed surface against scry-sai-core 2.3.0 (#383, #242)#523
Merged
Merged
Conversation
…re 2.3.0 (#383, #242) scry released v2.3.0; synth's VCR-MEM-001 layer-2 substrate pins the scry-sai-core DEV-dependency at `"2.0"` (caret) with a comment asserting the 2.x bump is "transparent" because the consumed surface is unchanged. That claim was only verified against 2.0.0 (the lockfile pin) — untested for 2.1/2.2/2.3. Bump the lockfile to scry-sai-core 2.3.0 and re-run the in-tree integration test (scry_shadow_stack_budget) that analyzes the real gust-family module: GREEN — the consumed surface (stack_usage.max_stack_bytes=65536, function_summaries[].recursive, reachable_from_exports) is unchanged, so the "transparent" claim is now empirically backed, not just asserted. Doc comments updated to record the 2.3.0 re-verification. Behavior-frozen: scry-sai-core is a DEV-dependency exercised only by this test — the production `synth` binary does not pull scry, so no codegen / `.text` change. Frozen anchors bit-identical (frozen_codegen_bytes 3/3); fmt clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
What
scry released v2.3.0. synth's VCR-MEM-001 (#383) layer-2 substrate pins the
scry-sai-coredev-dependency at"2.0"with a comment asserting the 2.x bump is"transparent" (consumed surface unchanged) — but that was only ever verified against
2.0.0 (the lockfile pin), untested for 2.1/2.2/2.3.
This bumps the lockfile to scry-sai-core 2.3.0 and re-runs the in-tree integration
test (
scry_shadow_stack_budget) that callsscry_analyze_core::analyze()on the realgust-family module. GREEN — the consumed surface is unchanged:
stack_usage.max_stack_bytes= 65536function_summaries[].recursive(honest-fail recursion gate)reachable_from_exports(dead-path pruning superset)So the "transparent bump" claim is now empirically backed, not just asserted. Doc
comments updated to record the 2.3.0 re-verification.
Gate
Behavior-frozen —
scry-sai-coreis a dev-dependency exercised only by this test, sothe production
synthbinary does not pull scry: no codegen /.textchange. Frozenanchors bit-identical (
frozen_codegen_bytes3/3, control_step0x00210A55/ flight_algo0x07FDF307untouched);cargo fmt --checkclean.Responds to the scry v2.3.0 release; the directive's preferred "external-analysis
dev-dependency + test" shape.
🤖 Generated with Claude Code