feat(addie): add private smoke live composition - #7331
Draft
bokelley wants to merge 2 commits into
Draft
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
Replaces the prior pre-live composition wiring with a pure JSON-text declarative contract for the frozen stage-1 authority. This is not a live coordinator.
not_provisioned: ordinal 1 requires the exact reviewed request-tool replay binding and semantic request fingerprint; ordinal 2 additionally requires exact provider continuation binding.Safety and scope
Validation
npm run typecheck, migration validation (3/3), and diff checks passed.pg_trgmcontrib prerequisite. After installing that prerequisite, a recreated fresh database completed the clean migration/integration rerun.HUSKY=0commit only for the unchanged two-file staged correction in commitdce6dce29b4d8933b8cdf908e37d90c121d29038; no other bypass was used.No protocol release surface changed, so no changeset is required.
Related to #6842.
Open workspace in Conductor