docs(runtime): state the exact interaction-response gate at the pinned toolchain - #30
Conversation
…d toolchain The gate prose and provider sections still described the 0.132-era and 0.6.x-era toolchain. Pin them to the versions commit 3d7b79f installs: - agent-interface 0.52.0 and agent-runtime 0.134.5 carry the full typed response contract, and the retained-run handle fails closed unless the provider advertises interactions.responseIdempotency and implements the environment or session operation. - agent-provider-cli-bridge 0.7.1 (verified unchanged through the newest published 0.7.7) has no interaction-response wire operation and no interactions capability key, so the local response path stays disabled by the provider package even though the Local CLI Bridge server already implements and advertises the durable respond endpoint. - agent-provider-tangle 0.10.0 statically declares the interaction kinds, replay, and response idempotency and narrows the claim per deployment; LIVE-08 remains the required proof. Add the owning upstream issues (agent-sdk#204 filed for the provider consumption gap; agent-runtime#735 for the release-level dispatch contract test) and a dated probe record in the verification observations.
|
Closing as superseded. The gate statement here is pinned to agent-provider-cli-bridge 0.7.1 ("interactions ABSENT, unchanged through 0.7.7"). That is no longer true: 0.9.x ships |
1 participant
Why
docs/04-runtime-contracts.mdanddocs/08-verification.mdstill described the interaction-response gate with 0.132-era runtime and 0.6.x-era provider facts. This PR pins the gate statement to the exact toolchain3d7b79finstalls and names the owning upstream issues.Probe evidence (static + local-bridge; no live Tangle, per scope fence)
agent-interface 0.52.0operationId+ 7-field binding +commandDigest; acknowledgement with 10 status variants covering all eight documented distinctions;InteractionCapabilities)dist/environment-runtime.d.ts:608,653,dist/provider-adapter.d.ts:41-44,dist/interaction-envelope.d.ts:198-267,dist/interaction-fields.d.ts:118-137agent-runtime 0.134.5dist/index-DHA5Oq5I.d.ts:470-472(requiredRetainedRunHandle.respondToInteraction);dist/runtime-DZql0Fnh.js:3784-3792throws unlesscapabilities.interactions?.responseIdempotency === trueAND the env/session implements the opagent-provider-cli-bridge 0.7.1interactionscapability key; unchanged through newest published0.7.7)interactionmatches in dist; wire ops only/v1/chat/completions,/v1/runs/:id/events,/v1/runs/:id/cancel;dist/index.js:64-122default capabilities omitinteractionsagent-provider-tangle 0.10.0dist/tangle-capabilities.js:58-66declares kindsquestion/permission/plan,replay:true,responseIdempotency:true; narrowed per deployment (responseDedupe+ SDK session op), claim deleted when unprovendrewstone/cli-bridge@d21273e)POST /v1/runs/:runId/interactions/:interactionId/respond(src/sessions/retained/http.ts:194-207), advertised in the live root endpoint JSON;GET /v1/capabilitiesrequiresinteractions.replay+interactions.responseIdempotency; pi backend advertises interactions (src/backends/pi-native-start.ts:293-302); a live probe of the respond route returned the route's own structured acknowledgement (status:"invalid_response", HTTP 400) vs plain 404 on an unknown sibling routeVerdict
The run-bound durable interaction-response operation is not exposed end-to-end by the pinned stack: the runtime gate always throws for the CLI Bridge provider because the provider package neither consumes the server's respond endpoint nor declares the capability. A Braid-side enablement would have to bypass
agent-runtimeownership or dress a type-only surface as a provider advertisement, so the publishable change is this truth update plus the upstream owners:Changes
docs/04-runtime-contracts.md: CLI Bridge provider section restated for0.7.1(wire surface, absent capability key, server-side existence, owner); Tangle provider section restated for0.10.0(declared interactions, per-deployment narrowing,LIVE-08still required); the resumable-interaction gate paragraph now names the pinned versions and the fail-closed runtime behavior; upstream issue list gains agent-sdk#204 and agent-runtime#735.docs/08-verification.md: dated observation recording the probe, whyLIVE-03/LIVE-08remain unattempted, and the owning issues.Verification
Docs-only change;
docs/*.mdis outside the formatter's include set and the verification-command catalog table is untouched, sotest/scripts.test.ts's docs/08 catalog assertion is unaffected. Evidence quotes were re-verified against the installed packages and the live server behavior listed above.