Implement AP-SPEC-0038 open production runtime - #109
Merged
Conversation
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
Implements all nine AP-SPEC-0038 open-core production epics as an end-to-end, production-shaped Auths surface.
The normal SDK path remains small and type-driven while the operational surface is progressively disclosed. Protocol meaning, retry safety, lifecycle state, effect commitments, and recovery metadata remain Rust-owned.
Product impact
A user can configure a production client, connect durable state and external custody, authorize an exact effect, execute through a closed provider gateway, recover safely after interruption, and diagnose the result without leaking authority or sensitive payloads. TypeScript and Python expose the same bounded product contract.
Validation
CARGO_INCREMENTAL=0 cargo xtask ci