Repository navigation
feat(registry): typed exact-one ApplicationStateInvoke union for host connectors (#650) - #652
Merged
Merged
Conversation
… connectors (#650) Adds the Traverse spec 1773 host-connector invoke variant alongside the capability variant; invalid combinations fail closed with redacted AppStateMachineInvalid diagnostics. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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
ApplicationStateInvokestruct with a public, serializable exact-one union (Traverse spec1773-host-connector-invoke-unionv1.0.0, approved 2026-11-03):Capability { capability_id, input_from: Option<String> }orHostConnector { host_connector }.{"host_connector": "audio.permission.request"}now load through typed manifest parsing instead of failing on a missingcapability_id. Capability-only manifests parse and serialize with the same field names as before (input_fromis now optional per the spec).input_from-with-connector invokes fail closed withAppStateMachineInvalidand fixed messages that never echo manifest-supplied names or values (tested with a sentinel secret).traverse-registryto 0.31.0 (breaking public type, on top of the 0.30.0 contracts-range widening from release(traverse-registry): support traverse-contracts 0.17 (#649) #651, which already resolves withtraverse-contracts0.16). CHANGELOG documents the new host-connector manifest support.Out of scope (per the spec, enforced elsewhere): resolving a connector command against app-declared connectors / Specs 104 and 137 dispatch, which live in Traverse runtime/CLI. Spec 1773's amendments to 044/046/139 are Traverse-repo approvals; this PR does not touch
approved-specs.json.Governing Spec
Project Item
Definition of Done
traverse-contracts0.16 (range>=0.8.1, <0.18.0)Validation
cargo test -p traverse-registry --locked— all pass (97 application_manifest tests incl. 2 new)cargo clippy -p traverse-registry --all-targets --locked -- -D warnings— clean🤖 Generated with Claude Code