Repository navigation
Expose the SDK session engine and release adapter 0.5.7 - #107
Merged
Merged
Conversation
…tion # Conflicts: # src/session.ts
…-forwarding # Conflicts: # src/session.ts
This was referenced Sep 14, 2026
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.
Adapter sessions now expose their existing SDK engine for controls and canonical measurements, preserve legacy measurement aliases, and forward snapshotted analysis preparation options. Session prefill uses the published SDK runway helper while preserving transport and cleanup behavior.
Pins adapter 0.5.7 to registry SDK 0.2.5 and includes current main, selected-store capability checks, and BLAKE3 work.
Independent Astra attempt-1 PASS for #95 and #101: full check (380 tests), real packed Chromium meters/response/spectrum with atomic target switching and refusal continuity, publish dry-run, and a normal fresh install with strict public types/imports and one SDK resolution. Publication and attestation follow the exact merged main commit before issue closure.
Refs #95, #101.