Teach single-call mailbox delivery and durable operations - #4
Merged
Conversation
Device commands now surface a delivery capability (realtime|mailbox|both) and tb call takes a per-call --delivery realtime|mailbox|fallback policy. The skill teaches the unified single-call form: fallback enqueues only on a proven non-dispatch, completed and unknown outcomes never enqueue, and agents never send a second enqueue or fixed-interval polling. Adds the tb device op ls/get/cancel surface, execution-ambiguity safety rules (result_unknown, expired+executionMayHaveOccurred), and store:// result handling with tb store commands.
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.
What
Bring the skill in line with the current tool-bridge implementation, which added durable device Mailbox delivery as part of the unified command invoke.
SKILL.md
deliverycapability metadata (realtime|mailbox|both) from the per-call--delivery realtime|mailbox|fallbackpolicy; offline-tolerant calls are a singletb call --delivery fallback— the gateway owns the enqueue decision (only a proven non-dispatch enqueues; completed results including device business errors, and outcome-unknown sends, never enqueue). Agents never send a second enqueue request of their own.x-tb-delivery: realtimevs 202 +x-tb-delivery: mailboxsemantics; after receiving an operation identity the sync flow ends — no fixed-interval polling, at most onetb device op getwhen the task actually needs current state. claim/renew/complete stay device-side.result_unknownandexpired + executionMayHaveOccurred: trueare execution ambiguity — no auto retry/re-enqueue without independently proven idempotency and user authorization; delivery mode never relaxeseffect/confirmboundaries.store://URIs are object identities (tb store stat/get);tb store shareonly on explicit user request, output handled as a secret, revocable viarevoke-share.references/cli-reference.md
deliveryadded to the help field list.--delivery/--ttl/--idempotency-keysyntax and constraints, fallback semantics, operation states,tb device ls/op ls|get|cancel, cooperative cancel and ambiguity rules.tb storesurface.Validation
npx --yes skills add . --listdiscovers exactly one skill (tool-bridge) with the updated description.All command syntax verified against the CLI source (
packages/cli/src/commands/call.ts,device.ts,store.ts) in the main tool-bridge repo.