opencode-a2a 0.8.2__tar.gz → 1.1.0__tar.gz

opencode_a2a-1.1.0/MANIFEST.in

@@ -0,0 +1 @@
+recursive-include docs *.md

{opencode_a2a-0.8.2/src/opencode_a2a.egg-info → opencode_a2a-1.1.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: opencode-a2a
-Version: 0.8.2
+Version: 1.1.0
 Summary: OpenCode A2A runtime
 Author: liujuanjuan1984@Intelligent-Internet
 License-Expression: Apache-2.0
@@ -19,12 +19,13 @@ Classifier: Topic :: Internet :: WWW/HTTP
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: a2a-sdk==0.3.26
+Requires-Dist: a2a-sdk==1.0.2
 Requires-Dist: aiosqlite<1.0,>=0.20
 Requires-Dist: fastapi<1.0,>=0.110
 Requires-Dist: httpx<1.0,>=0.27
 Requires-Dist: pydantic<3.0,>=2.6
 Requires-Dist: pydantic-settings<3.0,>=2.2
+Requires-Dist: protobuf<7.0,>=6.33.5
 Requires-Dist: sqlalchemy<3.0,>=2.0
 Requires-Dist: sse-starlette<4.0,>=2.1
 Requires-Dist: uvicorn<1.0,>=0.29
@@ -41,6 +42,15 @@ Dynamic: license-file
 
 # opencode-a2a
 
+```text
+  ___                    ____          _              _    ____     _
+ / _ \ _ __   ___ _ __  / ___|___   __| | ___        / \  |___ \   / \
+| | | | '_ \ / _ \ '_ \| |   / _ \ / _` |/ _ \_____ / _ \   __) | / _ \
+| |_| | |_) |  __/ | | | |__| (_) | (_| |  __/_____/ ___ \ / __/ / ___ \
+ \___/| .__/ \___|_| |_|\____\___/ \__,_|\___|    /_/   \_\_____/_/   \_\
+      |_|
+```
+
 > Expose OpenCode through A2A.
 
 `opencode-a2a` adds an A2A runtime layer to `opencode serve`, with auth, streaming, session continuity, interrupt handling, and a clear deployment boundary.
@@ -68,11 +78,11 @@ flowchart TD
         PeerA2A --> PeerRuntime
     end
 
-    External -->|message/send,\nmessage:stream| Ingress
+    External -->|SendMessage,\nSendStreamingMessage| Ingress
     Ingress -->|tool call| OpenCode
     OpenCode -->|model/tool result events| Ingress
     Ingress -->|a2a_call| Outbound
-    Outbound -->|message/send,\nmessage:stream| PeerA2A
+    Outbound -->|SendMessage,\nSendStreamingMessage| PeerA2A
     PeerA2A -->|tool result| Outbound
     PeerRuntime -->|task session\nexecution| PeerA2A
 ```
@@ -112,7 +122,7 @@ A2A_HOST=127.0.0.1 \
 A2A_PORT=8000 \
 A2A_PUBLIC_URL=http://127.0.0.1:8000 \
 OPENCODE_WORKSPACE_ROOT=/abs/path/to/workspace \
-opencode-a2a
+opencode-a2a serve
 ```
 
 Verify that the service is up:
@@ -125,7 +135,7 @@ curl http://127.0.0.1:8000/.well-known/agent-card.json
 
 - A2A HTTP+JSON endpoints such as `/v1/message:send` and `/v1/message:stream`
 - A2A JSON-RPC support on `POST /`
-- SDK-owned A2A task surfaces such as `GET /v1/tasks`, task push notification config routes, and JSON-RPC `agent/getAuthenticatedExtendedCard`
+- SDK-owned A2A task surfaces such as `GET /v1/tasks`, task push notification config routes, JSON-RPC `GetExtendedAgentCard`, and HTTP `GET /extendedAgentCard`
 - Peering capabilities: can act as a client via `opencode-a2a call`
 - Autonomous tool execution: supports `a2a_call` tool for outbound agent-to-agent communication
 - SSE streaming with normalized `text`, `reasoning`, and `tool_call` blocks
@@ -135,11 +145,10 @@ curl http://127.0.0.1:8000/.well-known/agent-card.json
 
 ## A2A Protocol Support
 
-- Default protocol line: `0.3`
-- Declared supported protocol lines: `0.3`, `1.0`
-- `0.3` is the stable interoperability baseline for the current runtime surface.
-- `1.0` currently covers version negotiation plus protocol-aware JSON-RPC and REST error shaping, while transport payloads, enums, pagination, signatures, and interface-level protocol declarations still follow the shipped SDK baseline.
-- The detailed compatibility matrix and machine-readable support boundary are documented in [`docs/guide.md`](docs/guide.md) and [`docs/compatibility.md`](docs/compatibility.md).
+- Supported A2A protocol line: `1.0`
+- The runtime is now v1-only across HTTP+JSON, JSON-RPC, Agent Card discovery, and protocol-aware error contracts.
+- Legacy `0.3` method aliases and payload shapes are rejected instead of being normalized at runtime.
+- The detailed runtime contract and machine-readable support boundary are documented in [`docs/guide.md`](docs/guide.md) and [`docs/compatibility.md`](docs/compatibility.md).
 
 ## Peering Node / Outbound Access
 
@@ -151,12 +160,12 @@ Interact with other A2A agents directly from the command line:
 ```bash
 # Using the target peer agent's Bearer token via environment injection
 A2A_CLIENT_BEARER_TOKEN=your-outbound-token \
-opencode-a2a call http://other-agent:8000 "How are you?"
+opencode-a2a call http://other-agent:8000/.well-known/agent-card.json "How are you?"
 
 # Using the target peer agent's Basic auth via environment injection
 # Accepts raw user:pass or its base64-encoded value
 A2A_CLIENT_BASIC_AUTH="user:pass" \
-opencode-a2a call http://other-agent:8000 "How are you?"
+opencode-a2a call http://other-agent:8000/.well-known/agent-card.json "How are you?"
 ```
 
 ### Outbound Agent Calls (Tools)

{opencode_a2a-0.8.2 → opencode_a2a-1.1.0}/README.md

@@ -1,5 +1,14 @@
 # opencode-a2a
 
+```text
+  ___                    ____          _              _    ____     _
+ / _ \ _ __   ___ _ __  / ___|___   __| | ___        / \  |___ \   / \
+| | | | '_ \ / _ \ '_ \| |   / _ \ / _` |/ _ \_____ / _ \   __) | / _ \
+| |_| | |_) |  __/ | | | |__| (_) | (_| |  __/_____/ ___ \ / __/ / ___ \
+ \___/| .__/ \___|_| |_|\____\___/ \__,_|\___|    /_/   \_\_____/_/   \_\
+      |_|
+```
+
 > Expose OpenCode through A2A.
 
 `opencode-a2a` adds an A2A runtime layer to `opencode serve`, with auth, streaming, session continuity, interrupt handling, and a clear deployment boundary.
@@ -27,11 +36,11 @@ flowchart TD
         PeerA2A --> PeerRuntime
     end
 
-    External -->|message/send,\nmessage:stream| Ingress
+    External -->|SendMessage,\nSendStreamingMessage| Ingress
     Ingress -->|tool call| OpenCode
     OpenCode -->|model/tool result events| Ingress
     Ingress -->|a2a_call| Outbound
-    Outbound -->|message/send,\nmessage:stream| PeerA2A
+    Outbound -->|SendMessage,\nSendStreamingMessage| PeerA2A
     PeerA2A -->|tool result| Outbound
     PeerRuntime -->|task session\nexecution| PeerA2A
 ```
@@ -71,7 +80,7 @@ A2A_HOST=127.0.0.1 \
 A2A_PORT=8000 \
 A2A_PUBLIC_URL=http://127.0.0.1:8000 \
 OPENCODE_WORKSPACE_ROOT=/abs/path/to/workspace \
-opencode-a2a
+opencode-a2a serve
 ```
 
 Verify that the service is up:
@@ -84,7 +93,7 @@ curl http://127.0.0.1:8000/.well-known/agent-card.json
 
 - A2A HTTP+JSON endpoints such as `/v1/message:send` and `/v1/message:stream`
 - A2A JSON-RPC support on `POST /`
-- SDK-owned A2A task surfaces such as `GET /v1/tasks`, task push notification config routes, and JSON-RPC `agent/getAuthenticatedExtendedCard`
+- SDK-owned A2A task surfaces such as `GET /v1/tasks`, task push notification config routes, JSON-RPC `GetExtendedAgentCard`, and HTTP `GET /extendedAgentCard`
 - Peering capabilities: can act as a client via `opencode-a2a call`
 - Autonomous tool execution: supports `a2a_call` tool for outbound agent-to-agent communication
 - SSE streaming with normalized `text`, `reasoning`, and `tool_call` blocks
@@ -94,11 +103,10 @@ curl http://127.0.0.1:8000/.well-known/agent-card.json
 
 ## A2A Protocol Support
 
-- Default protocol line: `0.3`
-- Declared supported protocol lines: `0.3`, `1.0`
-- `0.3` is the stable interoperability baseline for the current runtime surface.
-- `1.0` currently covers version negotiation plus protocol-aware JSON-RPC and REST error shaping, while transport payloads, enums, pagination, signatures, and interface-level protocol declarations still follow the shipped SDK baseline.
-- The detailed compatibility matrix and machine-readable support boundary are documented in [`docs/guide.md`](docs/guide.md) and [`docs/compatibility.md`](docs/compatibility.md).
+- Supported A2A protocol line: `1.0`
+- The runtime is now v1-only across HTTP+JSON, JSON-RPC, Agent Card discovery, and protocol-aware error contracts.
+- Legacy `0.3` method aliases and payload shapes are rejected instead of being normalized at runtime.
+- The detailed runtime contract and machine-readable support boundary are documented in [`docs/guide.md`](docs/guide.md) and [`docs/compatibility.md`](docs/compatibility.md).
 
 ## Peering Node / Outbound Access
 
@@ -110,12 +118,12 @@ Interact with other A2A agents directly from the command line:
 ```bash
 # Using the target peer agent's Bearer token via environment injection
 A2A_CLIENT_BEARER_TOKEN=your-outbound-token \
-opencode-a2a call http://other-agent:8000 "How are you?"
+opencode-a2a call http://other-agent:8000/.well-known/agent-card.json "How are you?"
 
 # Using the target peer agent's Basic auth via environment injection
 # Accepts raw user:pass or its base64-encoded value
 A2A_CLIENT_BASIC_AUTH="user:pass" \
-opencode-a2a call http://other-agent:8000 "How are you?"
+opencode-a2a call http://other-agent:8000/.well-known/agent-card.json "How are you?"
 ```
 
 ### Outbound Agent Calls (Tools)

{opencode_a2a-0.8.2 → opencode_a2a-1.1.0}/docs/compatibility.md

@@ -1,15 +1,14 @@
 # Compatibility Guide
 
-This document explains the compatibility promises `opencode-a2a` currently tries to uphold for A2A consumers, operators, and maintainers.
+This document defines the compatibility promises `opencode-a2a` currently upholds for A2A consumers, operators, and maintainers.
 
 ## Runtime Support
 
 - Python versions: 3.11, 3.12, 3.13
-- A2A SDK line: `0.3.x`
-- Default advertised protocol line: `0.3`
-- Declared supported protocol lines: `0.3`, `1.0`
+- A2A SDK line: `1.x.y`
+- Supported A2A protocol line: `1.0`
 
-The repository pins the SDK version in `pyproject.toml`. Upgrade the SDK deliberately rather than relying on floating dependency resolution.
+The repository currently pins one concrete SDK release in `pyproject.toml` within that v1 line. Upgrade the SDK deliberately rather than relying on floating dependency resolution. The SDK-owned core JSON-RPC method set follows that pinned release and is locked by repository tests so SDK upgrades trigger an explicit compatibility review.
 
 ## Contract Honesty
 
@@ -21,12 +20,12 @@ Machine-readable discovery surfaces must reflect actual runtime behavior:
 - JSON-RPC wire contract
 - compatibility profile
 
-If runtime support is not actually implemented, do not publish it as a supported machine-readable capability.
+If runtime support is not implemented, do not publish it as a supported machine-readable capability.
 
 Consumer guidance:
 
-- Treat the core A2A send / stream / task methods as the portable baseline.
-- Treat `urn:a2a:*` entries in this repository as shared repo-family conventions, not as a claim that they are part of the A2A core baseline.
+- Treat the v1 core A2A methods (`SendMessage`, `SendStreamingMessage`, `GetTask`, `CancelTask`, `SubscribeToTask`) as the portable baseline.
+- Treat `urn:opencode-a2a:extension:...` entries in this repository as repository-governed extension identifiers, not as a claim that they are part of the A2A core baseline.
 - Treat `opencode.*` methods and `metadata.opencode.*` fields as provider-private OpenCode control and discovery surfaces layered on top of the portable A2A baseline.
 - Treat [extension-specifications.md](./extension-specifications.md) as the stable URI/spec index, not as the main usage guide.
 
@@ -45,7 +44,8 @@ External TCK runs and local conformance experiments are investigation inputs. Th
 This repository still ships as an alpha project. Within that alpha line, these declared surfaces should not drift silently:
 
 - core A2A send / stream / task methods
-- version negotiation and protocol-aware error shaping
+- v1-only request/response payloads and enum values
+- v1 protocol-aware JSON-RPC and REST error shaping
 - shared session-binding metadata
 - shared model-selection metadata
 - shared streaming metadata
@@ -53,12 +53,13 @@ This repository still ships as an alpha project. Within that alpha line, these d
 - authenticated extended card and OpenAPI wire-contract metadata
 
 Changes to those surfaces should be treated as compatibility-sensitive and should include corresponding test updates.
+- provider-private session query params use one top-level request shape; the repository does not promise parallel nested `query.*` aliases for the same filters.
 
 Service-level behavior layered on top of those core methods should also be declared explicitly when interoperability depends on it. Current examples:
 
-- `tasks/resubscribe` replay-once behavior for terminal updates
+- `SubscribeToTask` replay-once behavior for terminal updates
 - first-terminal-state-wins task persistence policy
-- task-scoped `acceptedOutputModes` negotiation persistence across send / stream / get / resubscribe
+- task-scoped `acceptedOutputModes` negotiation persistence across send / stream / get / subscribe
 - request-body rejection behavior for oversized transport payloads
 
 ## Deployment Profile
@@ -92,13 +93,13 @@ The default SQLite-first profile is intended for local or controlled single-inst
 ## Extension Stability
 
 - Shared metadata and extension contracts should stay synchronized across Agent Card, OpenAPI, and runtime behavior.
-- Public Agent Card should stay intentionally minimal. Detailed extension params belong in the authenticated extended card and OpenAPI, not back in the anonymous discovery surface.
+- Public Agent Card should stay intentionally minimal. Detailed extension params belong in the authenticated extended card, while anonymous OpenAPI should mirror only the shared public disclosure subset.
 - Deployment-conditional methods must be declared as conditional rather than silently disappearing.
 - `opencode.sessions.prompt_async` input-part passthrough is compatibility-sensitive. Changes to supported part types, passthrough field semantics, or rejection behavior should be treated as wire-level changes.
 - `opencode.sessions.shell` is compatibility-sensitive as a deployment-conditional shell snapshot surface. It should not silently widen into a general interactive shell API.
 - `opencode.workspaces.*` and `opencode.worktrees.*` are boundary-sensitive and should remain explicitly provider-private, operator-scoped, and deployment-conditional where applicable.
 - Interrupt callback and recovery methods are compatibility-sensitive because clients may depend on request ID lifecycle, expiry semantics, and identity scoping.
-- Agent Card media modes and `acceptedOutputModes` handling are compatibility-sensitive. Changes to declared chat modes, to task-scoped negotiation persistence, or to `DataPart` -> `TextPart` downgrade behavior should be treated as wire-level changes.
+- Agent Card media modes and `acceptedOutputModes` handling are compatibility-sensitive. Changes to declared chat modes, to task-scoped negotiation persistence, or to output filtering of structured tool payloads should be treated as wire-level changes.
 - Agent Card and OpenAPI publication of `protocol_compatibility`, `service_behaviors`, and runtime feature toggles is compatibility-sensitive discoverability surface.
 
 ## Extension Boundary Governance
@@ -132,7 +133,7 @@ This repository distinguishes between three layers:
 
 Important note:
 
-- `urn:a2a:*` extension URIs used here should be read as shared conventions in this repository family.
+- `urn:opencode-a2a:extension:...` extension URIs used here are repository-governed, versioned permanent identifiers.
 - They are not a claim that those extensions are part of the A2A core baseline.
 - `opencode.*` methods are intentionally product-specific. They improve OpenCode-aware workflows but should not be assumed to transfer unchanged to unrelated A2A agents.
 
@@ -142,6 +143,6 @@ This repository does not currently promise:
 
 - hard multi-tenant isolation inside one instance
 - generic provider-auth orchestration on behalf of OpenCode
-- a claim that all declared `1.0` protocol surfaces are fully implemented beyond the documented compatibility matrix
+- compatibility with legacy A2A `0.3` method aliases or payload shapes
 
 Those areas may evolve later, but they should not be implied by current machine-readable discovery output.

opencode_a2a-1.1.0/docs/conformance-triage.md

@@ -0,0 +1,32 @@
+# External Conformance Triage
+
+This document summarizes the current interpretation rules for external TCK runs after the repository's A2A v1 migration.
+
+## Current Runtime Baseline
+
+- `opencode-a2a` now targets the `a2a-sdk 1.x.y` line
+- the runtime is v1-only
+- canonical JSON-RPC core methods are `SendMessage`, `SendStreamingMessage`, `GetTask`, `CancelTask`, and `SubscribeToTask`
+- legacy `0.3` aliases and payload shapes are intentionally rejected rather than normalized
+
+## How To Read TCK Failures
+
+When a TCK run fails, classify the result before changing the runtime:
+
+- `Runtime gap`
+  - the failure reproduces against the current v1-only runtime and contradicts the repository's declared machine-readable contract
+- `TCK assumption mismatch`
+  - the failure depends on method names, payload shapes, or schema expectations that do not match the current A2A v1 SDK/runtime contract
+- `Local experiment artifact`
+  - the failure depends on dummy-backed local behavior, environment heuristics, or unrelated tooling/setup issues
+
+## Current Guidance
+
+- Re-run conformance against the current runtime before using any historical triage note.
+- Treat Agent Card, authenticated extended card, OpenAPI, and runtime tests as the repository's declared source of truth.
+- Do not reopen removed `0.3` compatibility behavior just to satisfy an outdated TCK assumption.
+- If a TCK gap is real, document it against the current v1 contract with the exact request/response payloads that failed.
+
+## Historical Note
+
+Earlier repository-local triage notes were written before the v1 migration and described a mixed `0.3` / partial `1.0` state. Those notes are no longer normative and were removed to avoid stale guidance.

{opencode_a2a-0.8.2 → opencode_a2a-1.1.0}/docs/conformance.md

@@ -59,8 +59,8 @@ Each run keeps the following artifacts in the selected output directory:
 When a TCK run fails, inspect the raw report before changing the runtime:
 
 - Some failures may point to real runtime gaps.
-- Some failures may come from TCK assumptions that do not match `a2a-sdk==0.3.25`.
-- Some failures may come from A2A v0.3 versus v1.0 naming or schema drift.
+- Some failures may come from TCK assumptions that do not match the current `a2a-sdk 1.x.y` contract.
+- Some failures may come from local dummy-backed experiment behavior rather than a wire-level runtime defect.
 
 The experiment is useful only if those categories stay separate during triage.
 

opencode_a2a-1.1.0/docs/extension-specifications.md

@@ -0,0 +1,169 @@
+# Extension Specifications
+
+This document is the stable specification index for extension URIs published by `opencode-a2a`. It is intentionally a compact URI/spec map, not the main consumer guide. For runtime behavior, request examples, and operational setup, see [`guide.md`](./guide.md). For compatibility promises and stability expectations, see [`compatibility.md`](./compatibility.md).
+
+## Discovery Surface Note
+
+`opencode-a2a` splits extension discovery into three layers:
+
+- Public Agent Card: minimal anonymous discovery for core interfaces and low-sensitivity shared extensions
+- Authenticated extended Agent Card: the canonical machine-readable source for deployment-specific provider-private contracts
+- OpenAPI metadata: minimal anonymous shared-contract disclosure only; provider-private method matrices are intentionally not expanded there
+
+Provider-private contract note:
+
+- `opencode.*` methods in this repository are deployment-specific provider extensions, not portable A2A baseline capabilities.
+- Shared `metadata.shared.*` contracts are intended to remain low-risk and transportable.
+- Compatibility and wire-contract URIs are descriptive metadata contracts, not activatable runtime capabilities.
+- URI path segments identify the contract, not its auth or disclosure tier; public-vs-extended disclosure is controlled by Agent Card and OpenAPI surfaces.
+
+## SDK and Discovery Compatibility
+
+- A2A v1.0 Agent Cards expose extended-card availability via `AgentCard.capabilities.extendedAgentCard`.
+- `opencode-a2a` emits `capabilities.extendedAgentCard` in both public and authenticated extended cards; it does not emit the removed top-level `supportsAuthenticatedExtendedCard` field.
+- The canonical authenticated extended Agent Card HTTP endpoint is `GET /extendedAgentCard`.
+
+## URI Index
+
+| Extension | Scope | Disclosure | URI | Section |
+| --- | --- | --- | --- | --- |
+| Shared Session Binding v1 | Shared request metadata | Public + extended | `urn:opencode-a2a:extension:session-binding:v1` | [Shared Session Binding v1](#shared-session-binding-v1) |
+| Shared Model Selection v1 | Shared request metadata | Public + extended | `urn:opencode-a2a:extension:model-selection:v1` | [Shared Model Selection v1](#shared-model-selection-v1) |
+| Shared Stream Hints v1 | Shared response/stream metadata | Public + extended | `urn:opencode-a2a:extension:stream-hints:v1` | [Shared Stream Hints v1](#shared-stream-hints-v1) |
+| Shared Interactive Interrupt v1 | Shared JSON-RPC callback methods | Public + extended | `urn:opencode-a2a:extension:interactive-interrupt:v1` | [Shared Interactive Interrupt v1](#shared-interactive-interrupt-v1) |
+| OpenCode Session Management v1 | Provider-private JSON-RPC methods | Extended only | `urn:opencode-a2a:extension:session-management:v1` | [OpenCode Session Management v1](#opencode-session-management-v1) |
+| OpenCode Provider Discovery v1 | Provider-private JSON-RPC methods | Extended only | `urn:opencode-a2a:extension:provider-discovery:v1` | [OpenCode Provider Discovery v1](#opencode-provider-discovery-v1) |
+| OpenCode Workspace Control v1 | Provider-private JSON-RPC methods | Extended only | `urn:opencode-a2a:extension:workspace-control:v1` | [OpenCode Workspace Control v1](#opencode-workspace-control-v1) |
+| OpenCode Interrupt Recovery v1 | Provider-private JSON-RPC methods | Extended only | `urn:opencode-a2a:extension:interrupt-recovery:v1` | [OpenCode Interrupt Recovery v1](#opencode-interrupt-recovery-v1) |
+| A2A Compatibility Profile v1 | Authenticated discovery metadata | Extended only | `urn:opencode-a2a:extension:compatibility-profile:v1` | [A2A Compatibility Profile v1](#a2a-compatibility-profile-v1) |
+| A2A Wire Contract v1 | Authenticated discovery metadata | Extended only | `urn:opencode-a2a:extension:wire-contract:v1` | [A2A Wire Contract v1](#a2a-wire-contract-v1) |
+
+## Shared Session Binding v1
+
+Extension URI: `urn:opencode-a2a:extension:session-binding:v1`
+
+- Scope: shared A2A request metadata for rebinding to an existing upstream OpenCode session, plus negotiated response/task session metadata
+- Disclosure: public Agent Card and authenticated extended Agent Card
+- Activation: client requests the URI via `A2A-Extensions` and sends `metadata.shared.session.id`
+- Runtime fields: `metadata.shared.session.id`, `metadata.shared.session`, optional provider-private companions `metadata.opencode.directory` and `metadata.opencode.workspace.id`
+- Dependencies: none declared by this version
+- Security boundary: shared session identity is portable; provider-private routing metadata remains deployment-scoped
+- Versioning: breaking changes require a new versioned URI
+
+## Shared Model Selection v1
+
+Extension URI: `urn:opencode-a2a:extension:model-selection:v1`
+
+- Scope: shared request-scoped model override for the main chat path
+- Disclosure: public Agent Card and authenticated extended Agent Card
+- Activation: client requests the URI via `A2A-Extensions` and sends `metadata.shared.model`
+- Runtime fields: `metadata.shared.model.providerID`, `metadata.shared.model.modelID`
+- Applies to methods: `SendMessage`, `SendStreamingMessage`
+- Dependencies: none declared by this version
+- Security boundary: request-scoped model preference is shared; provider defaults and auth remain OpenCode deployment concerns
+- Versioning: breaking changes require a new versioned URI
+
+## Shared Stream Hints v1
+
+Extension URI: `urn:opencode-a2a:extension:stream-hints:v1`
+
+- Scope: shared response/task/stream metadata for block identity, progress, and usage hints
+- Disclosure: public Agent Card and authenticated extended Agent Card
+- Activation: client requests the URI via `A2A-Extensions`; runtime emits shared metadata on streamed events and final task payloads
+- Declared field map:
+  - `metadata.shared.stream.block_type`
+  - `metadata.shared.stream.sequence`
+  - `metadata.shared.progress.type`
+  - `metadata.shared.progress.status`
+  - `metadata.shared.usage.input_tokens`
+  - `metadata.shared.usage.output_tokens`
+  - `metadata.shared.usage.total_tokens`
+- Clients must not treat undeclared metadata under this namespace as part of the shared v1 contract
+- Dependencies: none declared by this version
+- Security boundary: this extension is observational metadata only; callback methods are defined by the separate shared interactive interrupt extension
+- Versioning: breaking changes require a new versioned URI
+
+## Shared Interactive Interrupt v1
+
+Extension URI: `urn:opencode-a2a:extension:interactive-interrupt:v1`
+
+- Scope: shared JSON-RPC callback methods used to answer interactive permission and question interrupts
+- Disclosure: public Agent Card and authenticated extended Agent Card
+- Activation: client requests the URI via `A2A-Extensions` before calling `a2a.interrupt.*` methods
+- Methods: `a2a.interrupt.permission.reply`, `a2a.interrupt.question.reply`, `a2a.interrupt.question.reject`
+- Runtime fields: `metadata.shared.interrupt`, including `metadata.shared.interrupt.request_id` as the callback correlation key
+- Dependencies: none declared by this version
+- Security boundary: the methods are shared, but request IDs remain scoped to authenticated caller identity and local interrupt state
+- Versioning: breaking changes require a new versioned URI
+
+## OpenCode Session Management v1
+
+Extension URI: `urn:opencode-a2a:extension:session-management:v1`
+
+- Scope: OpenCode session read, mutation, and control methods exposed as A2A JSON-RPC extension methods
+- Disclosure: authenticated extended Agent Card only
+- Activation: authenticated client requests the URI via `A2A-Extensions` before calling `opencode.sessions.*`
+- Methods: `opencode.sessions.status`, `list`, `get`, `children`, `todo`, `diff`, `messages.get`, `messages.list`, `prompt_async`, `command`, `fork`, `share`, `unshare`, `summarize`, `revert`, `unrevert`, and deployment-conditional `shell`
+- Dependencies: none declared by this version
+- Security boundary: this extension is provider-private and deployment-scoped; consumers must not treat it as portable A2A baseline behavior
+- Versioning: breaking changes require a new versioned URI
+
+## OpenCode Provider Discovery v1
+
+Extension URI: `urn:opencode-a2a:extension:provider-discovery:v1`
+
+- Scope: OpenCode provider and model discovery methods exposed as A2A JSON-RPC extension methods
+- Disclosure: authenticated extended Agent Card only
+- Activation: authenticated client requests the URI via `A2A-Extensions` before calling `opencode.providers.list` or `opencode.models.list`
+- Methods: `opencode.providers.list`, `opencode.models.list`
+- Dependencies: none declared by this version
+- Security boundary: provider/model catalogs remain OpenCode-specific operational surfaces
+- Versioning: breaking changes require a new versioned URI
+
+## OpenCode Workspace Control v1
+
+Extension URI: `urn:opencode-a2a:extension:workspace-control:v1`
+
+- Scope: OpenCode project, workspace, and worktree discovery/control methods exposed as A2A JSON-RPC extension methods
+- Disclosure: authenticated extended Agent Card only
+- Activation: authenticated client requests the URI via `A2A-Extensions` before calling `opencode.projects.*`, `opencode.workspaces.*`, or `opencode.worktrees.*`
+- Methods: stable project discovery plus experimental workspace/worktree discovery and deployment-conditional mutation methods
+- Dependencies: none declared by this version
+- Security boundary: this extension is provider-private, operator-scoped, and partly deployment-conditional
+- Versioning: breaking changes require a new versioned URI
+
+## OpenCode Interrupt Recovery v1
+
+Extension URI: `urn:opencode-a2a:extension:interrupt-recovery:v1`
+
+- Scope: local interrupt recovery methods exposed as A2A JSON-RPC extension methods
+- Disclosure: authenticated extended Agent Card only
+- Activation: authenticated client requests the URI via `A2A-Extensions` before calling `opencode.permissions.list` or `opencode.questions.list`
+- Methods: `opencode.permissions.list`, `opencode.questions.list`
+- Dependencies: none declared by this version
+- Security boundary: recovery state is adapter-local and scoped to the current authenticated caller
+- Versioning: breaking changes require a new versioned URI
+
+## A2A Compatibility Profile v1
+
+Extension URI: `urn:opencode-a2a:extension:compatibility-profile:v1`
+
+- Scope: authenticated discovery metadata describing protocol support, extension retention, and stable service behaviors
+- Disclosure: authenticated extended Agent Card only
+- Activation: authenticated extended Agent Card discovery
+- Data surface: `protocol_compatibility`, method-retention metadata, deployment profile summary, and declared service behaviors
+- Dependencies: none declared by this version
+- Security boundary: this is deployment-specific contract metadata, not a portable core A2A guarantee
+- Versioning: breaking changes require a new versioned URI
+
+## A2A Wire Contract v1
+
+Extension URI: `urn:opencode-a2a:extension:wire-contract:v1`
+
+- Scope: authenticated discovery metadata describing supported methods, HTTP endpoints, extension URIs, and unified error semantics
+- Disclosure: authenticated extended Agent Card only
+- Activation: authenticated extended Agent Card discovery
+- Data surface: core JSON-RPC methods, core HTTP endpoints, extension JSON-RPC methods, conditional availability, and protocol compatibility summary
+- Dependencies: none declared by this version
+- Security boundary: this is deployment-specific discovery metadata, not an invitation to assume portability of `opencode.*` surfaces
+- Versioning: breaking changes require a new versioned URI