Repository navigation
refactor: consolidate runtime and provider integration contracts - #241
Merged
Merged
Conversation
…ct-cleanup # Conflicts: # apps/docs/content/guide-sources.json
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.
Providers currently depend on Runtime's private credential storage, while node deployment rules and Harness interactions have parallel definitions. This change gives these boundaries one current contract and removes retired project wire paths.
Core and Runtime must be built from this revision together (Runtime wire 0.9.0, node wire 3). This does not add historical upgrades or change the pinned public API.
Validation:
make checkgates, resuming failed setup/build stages after correction. Web browser acceptance used cached Chromium through an external host-only configuration because Chrome is unavailable: 83/86 passed initially and the three failed tests passed on a targeted rerun. Example browser acceptance: 10/10.Live-model limitation: the optional Claude/MiniMax acceptance scenario did not pass exact response-marker assertions in function resume/steering. Recorded function delivery and steering receipts succeeded; this is not a claim of full live acceptance.
Integrated main through #239 and #240 (906bc67), preserving the distinction between confirmed preparation failure and retryable uncertain states.