opencode-a2a 0.6.0__tar.gz → 0.6.1__tar.gz

opencode_a2a-0.6.1/.github/workflows/publish.yml

@@ -0,0 +1,160 @@
+name: Publish
+
+on:
+  push:
+    tags:
+      - "v*"
+  workflow_dispatch:
+    inputs:
+      release_tag:
+        description: Existing v* tag to publish or repair
+        required: true
+        type: string
+      publish_to_pypi:
+        description: Publish artifacts to PyPI before syncing the GitHub Release
+        required: true
+        default: false
+        type: boolean
+      sync_github_release:
+        description: Create or repair the GitHub Release and release assets
+        required: true
+        default: true
+        type: boolean
+
+concurrency:
+  group: publish-${{ github.event_name == 'workflow_dispatch' && inputs.release_tag || github.ref_name }}
+  cancel-in-progress: false
+
+permissions:
+  contents: write
+  id-token: write
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0
+          ref: ${{ github.event_name == 'workflow_dispatch' && inputs.release_tag || github.ref }}
+
+      - name: Setup Python
+        uses: actions/setup-python@v6
+        with:
+          python-version: "3.13"
+
+      - name: Setup uv
+        uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: false
+
+      - name: Run regression baseline
+        run: bash ./scripts/doctor.sh
+
+      - name: Export runtime requirements for vulnerability audit
+        run: >
+          uv export --format requirements.txt --no-dev --locked --no-emit-project
+          --output-file /tmp/runtime-requirements.txt >/dev/null
+
+      - name: Run runtime dependency vulnerability audit
+        run: uv run pip-audit --requirement /tmp/runtime-requirements.txt
+
+      - name: Clean previous build artifacts
+        run: rm -rf build dist
+
+      - name: Build package artifacts
+        run: uv build --no-sources
+
+      - name: Verify published version matches tag
+        env:
+          RELEASE_TAG: ${{ github.event_name == 'workflow_dispatch' && inputs.release_tag || github.ref_name }}
+        run: |
+          python - <<'PY'
+          import os
+          import pathlib
+
+          dist_dir = pathlib.Path("dist")
+          wheels = sorted(dist_dir.glob("opencode_a2a-*.whl"))
+          sdists = sorted(dist_dir.glob("opencode_a2a-*.tar.gz"))
+          if len(wheels) != 1:
+              raise SystemExit(f"Expected exactly one wheel in dist/, found {len(wheels)}")
+          if len(sdists) != 1:
+              raise SystemExit(f"Expected exactly one sdist in dist/, found {len(sdists)}")
+          wheel = wheels[0].name
+          sdist = sdists[0].name
+          version = wheel.removeprefix("opencode_a2a-").split("-py3", 1)[0]
+          sdist_version = sdist.removeprefix("opencode_a2a-").removesuffix(".tar.gz")
+          tag = os.environ["RELEASE_TAG"].removeprefix("v")
+          if version != tag:
+              raise SystemExit(f"Wheel version {version!r} does not match tag {tag!r}")
+          if sdist_version != tag:
+              raise SystemExit(f"sdist version {sdist_version!r} does not match tag {tag!r}")
+          print(f"Validated release version: {version}")
+          PY
+
+      - name: Smoke test wheel install
+        run: bash ./scripts/smoke_test_built_cli.sh dist/opencode_a2a-*.whl
+
+      - name: Smoke test sdist install
+        run: bash ./scripts/smoke_test_built_cli.sh dist/opencode_a2a-*.tar.gz
+
+      - name: Publish to PyPI
+        if: ${{ github.event_name != 'workflow_dispatch' || inputs.publish_to_pypi }}
+        uses: pypa/gh-action-pypi-publish@release/v1
+
+      - name: Sync GitHub Release
+        if: ${{ github.event_name != 'workflow_dispatch' || inputs.sync_github_release }}
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          RELEASE_TAG: ${{ github.event_name == 'workflow_dispatch' && inputs.release_tag || github.ref_name }}
+        run: |
+          set -euo pipefail
+
+          retry() {
+            local attempts="$1"
+            local sleep_seconds="$2"
+            shift 2
+
+            local attempt=1
+            while true; do
+              if "$@"; then
+                return 0
+              fi
+
+              if [ "$attempt" -ge "$attempts" ]; then
+                echo "Command failed after ${attempts} attempts: $*" >&2
+                return 1
+              fi
+
+              echo "Retrying (${attempt}/${attempts}) after transient failure: $*" >&2
+              sleep "$sleep_seconds"
+              attempt=$((attempt + 1))
+            done
+          }
+
+          ensure_release() {
+            if retry 3 5 gh release view "$RELEASE_TAG" --json url >/dev/null; then
+              echo "Release ${RELEASE_TAG} already exists."
+              return 0
+            fi
+
+            retry 3 5 gh release create "$RELEASE_TAG" --verify-tag --generate-notes
+          }
+
+          ensure_release
+
+          mapfile -t existing_assets < <(
+            retry 3 5 gh release view "$RELEASE_TAG" --json assets --jq '.assets[].name'
+          )
+
+          for asset in dist/*.tar.gz dist/*.whl; do
+            asset_name="$(basename "$asset")"
+            if printf '%s\n' "${existing_assets[@]}" | grep -Fxq "$asset_name"; then
+              echo "Release asset already present: $asset_name"
+              continue
+            fi
+
+            retry 3 5 gh release upload "$RELEASE_TAG" "$asset"
+          done

{opencode_a2a-0.6.0 → opencode_a2a-0.6.1}/CODE_OF_CONDUCT.md

@@ -18,12 +18,8 @@ This project expects respectful, technically focused collaboration.
 
 ## Reporting
 
-For normal collaboration problems, open an issue or discussion with enough
-context to review the situation. For security-sensitive or private concerns,
-follow the disclosure path in [SECURITY.md](SECURITY.md).
+For normal collaboration problems, open an issue or discussion with enough context to review the situation. For security-sensitive or private concerns, follow the disclosure path in [SECURITY.md](SECURITY.md).
 
 ## Enforcement
 
-Repository maintainers may edit, hide, lock, or remove content that violates
-this policy, and may restrict participation when needed to keep collaboration
-safe and productive.
+Repository maintainers may edit, hide, lock, or remove content that violates this policy, and may restrict participation when needed to keep collaboration safe and productive.

{opencode_a2a-0.6.0 → opencode_a2a-0.6.1}/CONTRIBUTING.md

@@ -2,9 +2,7 @@
 
 Thanks for contributing to `opencode-a2a`.
 
-This repository maintains an OpenCode A2A runtime. Changes
-should keep runtime behavior, Agent Card declarations, OpenAPI examples, and
-machine-readable extension contracts aligned.
+This repository maintains an OpenCode A2A runtime. Changes should keep runtime behavior, Agent Card declarations, OpenAPI examples, and machine-readable extension contracts aligned.
 
 ## Before You Start
 
@@ -50,16 +48,14 @@ uv run pre-commit run --all-files
 uv run pytest
 ```
 
-If you change shell scripts, also run `bash -n` on each modified script, for
-example:
+If you change shell scripts, also run `bash -n` on each modified script, for example:
 
 ```bash
 bash -n scripts/doctor.sh
 bash -n scripts/lint.sh
 ```
 
-If you change extension methods, extension metadata, or Agent Card/OpenAPI
-contract surfaces, also run:
+If you change extension methods, extension metadata, or Agent Card/OpenAPI contract surfaces, also run:
 
 ```bash
 uv run pytest tests/contracts/test_extension_contract_consistency.py
@@ -82,6 +78,18 @@ uv run mypy src/opencode_a2a
 - Link the relevant issue in commits and PR descriptions when applicable.
 - Open PRs as Draft by default when the change still needs review or iteration.
 
+## Release Recovery
+
+`Publish` is the release workflow for tagged versions. It now supports both the normal tag-push path and explicit maintainer recovery runs.
+
+- Tag pushes still perform the full release flow: regression checks, artifact builds, PyPI publish, and GitHub Release sync.
+- Manual `workflow_dispatch` runs require a `release_tag` input so the workflow checks out and rebuilds the exact tagged revision instead of the current branch tip.
+- Manual `workflow_dispatch` runs default `publish_to_pypi=false` so the safest recovery path is to repair the GitHub Release without attempting a duplicate PyPI publish.
+- Set `publish_to_pypi=true` only when a maintainer intentionally needs the manual dispatch to publish artifacts to PyPI before syncing the GitHub Release.
+- GitHub Release sync is idempotent for the tagged release: it creates the release when missing and uploads only missing wheel/sdist assets.
+
+If a release run publishes to PyPI successfully but fails while creating or uploading the GitHub Release, recover with a manual dispatch against the same tag and set `publish_to_pypi=false`.
+
 ## Documentation
 
 Update docs together with code whenever you change:
@@ -91,12 +99,9 @@ Update docs together with code whenever you change:
 - user-facing request or response shapes
 - operational scripts
 
-Keep compatibility guidance centralized in [docs/guide.md](docs/guide.md) unless a
-new standalone document is clearly necessary.
+Keep compatibility guidance centralized in [docs/guide.md](docs/guide.md) unless a new standalone document is clearly necessary.
 
-When changing extension contracts, update
-[`src/opencode_a2a/contracts/extensions.py`](src/opencode_a2a/contracts/extensions.py)
-first and keep these generated/documented surfaces aligned:
+When changing extension contracts, update [`src/opencode_a2a/contracts/extensions.py`](src/opencode_a2a/contracts/extensions.py) first and keep these generated/documented surfaces aligned:
 
 - Agent Card extension params
 - OpenAPI `POST /` extension metadata and examples

{opencode_a2a-0.6.0/src/opencode_a2a.egg-info → opencode_a2a-0.6.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: opencode-a2a
-Version: 0.6.0
+Version: 0.6.1
 Summary: OpenCode A2A runtime
 Author: liujuanjuan1984@Intelligent-Internet
 License-Expression: Apache-2.0
@@ -43,16 +43,12 @@ Dynamic: license-file
 
 > 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.
+`opencode-a2a` adds an A2A runtime layer to `opencode serve`, with auth, streaming, session continuity, interrupt handling, and a clear deployment boundary.
 
 ## What This Is
 
-- An A2A adapter service built on `opencode serve`, with inbound runtime
-  exposure plus outbound peer calling.
-- It supports both roles in one process: serving as an A2A Server and hosting an
-  embedded A2A Client for `a2a_call`.
+- An A2A adapter service built on `opencode serve`, with inbound runtime exposure plus outbound peer calling.
+- It supports both roles in one process: serving as an A2A Server and hosting an embedded A2A Client for `a2a_call`.
 
 ## Architecture
 
@@ -95,8 +91,7 @@ Upgrade later with:
 uv tool upgrade opencode-a2a
 ```
 
-Make sure provider credentials and a default model are configured on the
-OpenCode side, then start OpenCode:
+Make sure provider credentials and a default model are configured on the OpenCode side, then start OpenCode:
 
 ```bash
 opencode auth login
@@ -104,10 +99,7 @@ opencode models
 opencode serve --hostname 127.0.0.1 --port 4096
 ```
 
-Treat the deployed OpenCode user's HOME/XDG config directories as part of the
-runtime state. If a packaged or service-managed deployment appears to ignore
-fresh provider env vars, inspect that user's persisted OpenCode auth/config
-files before assuming the A2A adapter layer is overriding credentials.
+Treat the deployed OpenCode user's HOME/XDG config directories as part of the runtime state. If a packaged or service-managed deployment appears to ignore fresh provider env vars, inspect that user's persisted OpenCode auth/config files before assuming the A2A adapter layer is overriding credentials.
 
 Then start `opencode-a2a` against that upstream:
 
@@ -130,11 +122,9 @@ curl http://127.0.0.1:8000/.well-known/agent-card.json
 
 ## Capabilities
 
-- A2A HTTP+JSON endpoints such as `/v1/message:send` and
-  `/v1/message:stream`
+- 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, and JSON-RPC `agent/getAuthenticatedExtendedCard`
 - 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
@@ -163,21 +153,11 @@ opencode-a2a call http://other-agent:8000 "How are you?"
 ### Outbound Agent Calls (Tools)
 The server can autonomously execute `a2a_call(url, message)` tool calls emitted by the OpenCode runtime. Results are fetched via A2A and returned to the model as tool results, enabling multi-agent orchestration.
 
-When the target peer agent requires bearer auth, configure
-`A2A_CLIENT_BEARER_TOKEN` for server-side outbound calls. When the target peer
-agent requires Basic auth, use `A2A_CLIENT_BASIC_AUTH`.
-These outbound credentials apply to the peer specified by `opencode-a2a call`
-or `a2a_call(url, message)`, not to this service's inbound `A2A_BEARER_TOKEN`.
-The CLI intentionally reads outbound credentials from environment variables only,
-so secrets do not appear in shell history or process arguments.
+When the target peer agent requires bearer auth, configure `A2A_CLIENT_BEARER_TOKEN` for server-side outbound calls. When the target peer agent requires Basic auth, use `A2A_CLIENT_BASIC_AUTH`. These outbound credentials apply to the peer specified by `opencode-a2a call` or `a2a_call(url, message)`, not to this service's inbound `A2A_BEARER_TOKEN`. The CLI intentionally reads outbound credentials from environment variables only, so secrets do not appear in shell history or process arguments.
 
-Server-side outbound client settings are fully wired through runtime config:
-`A2A_CLIENT_TIMEOUT_SECONDS`, `A2A_CLIENT_CARD_FETCH_TIMEOUT_SECONDS`,
-`A2A_CLIENT_USE_CLIENT_PREFERENCE`, `A2A_CLIENT_BEARER_TOKEN`, `A2A_CLIENT_BASIC_AUTH`, and
-`A2A_CLIENT_SUPPORTED_TRANSPORTS`.
+Server-side outbound client settings are fully wired through runtime config: `A2A_CLIENT_TIMEOUT_SECONDS`, `A2A_CLIENT_CARD_FETCH_TIMEOUT_SECONDS`, `A2A_CLIENT_USE_CLIENT_PREFERENCE`, `A2A_CLIENT_BEARER_TOKEN`, `A2A_CLIENT_BASIC_AUTH`, and `A2A_CLIENT_SUPPORTED_TRANSPORTS`.
 
-Detailed protocol contracts, examples, and extension docs live in
-[`docs/guide.md`](docs/guide.md).
+Detailed protocol contracts, examples, and extension docs live in [`docs/guide.md`](docs/guide.md).
 
 ## When To Use It
 
@@ -193,24 +173,17 @@ Look elsewhere if:
 - you want this project to manage your process supervisor or host bootstrap
 - you want a general client integration layer rather than a server wrapper
 
-For client-side integration, prefer
-[a2a-client-hub](https://github.com/liujuanjuan1984/a2a-client-hub).
+For client-side integration, prefer [a2a-client-hub](https://github.com/liujuanjuan1984/a2a-client-hub).
 
 ## Deployment Boundary
 
-This repository improves the service boundary around OpenCode, but it does not
-turn OpenCode into a hardened multi-tenant platform.
+This repository improves the service boundary around OpenCode, but it does not turn OpenCode into a hardened multi-tenant platform.
 
 - `A2A_BEARER_TOKEN` protects the A2A surface.
-- Provider auth and default model configuration remain on the OpenCode side; deployment-time
-  precedence details and HOME/XDG state impact are documented in
-  [docs/guide.md](docs/guide.md#troubleshooting-provider-auth-state).
-- Use `A2A_CLIENT_BEARER_TOKEN` for server-side outbound peer calls initiated by
-  `a2a_call`.
-- Deployment supervision is intentionally BYO. Use `systemd`, Docker,
-  Kubernetes, or another supervisor if you need long-running operation.
-- For mutually untrusted tenants, run separate instance pairs with isolated
-  users, containers, workspaces, credentials, and ports.
+- Provider auth and default model configuration remain on the OpenCode side; deployment-time precedence details and HOME/XDG state impact are documented in [docs/guide.md](docs/guide.md#troubleshooting-provider-auth-state).
+- Use `A2A_CLIENT_BEARER_TOKEN` for server-side outbound peer calls initiated by `a2a_call`.
+- Deployment supervision is intentionally BYO. Use `systemd`, Docker, Kubernetes, or another supervisor if you need long-running operation.
+- For mutually untrusted tenants, run separate instance pairs with isolated users, containers, workspaces, credentials, and ports.
 
 Read before deployment:
 
@@ -221,15 +194,12 @@ Read before deployment:
 
 ## Further Reading
 
-- [docs/guide.md](docs/guide.md)
-  Usage guide, transport details, streaming behavior, extensions, and examples.
-- [SECURITY.md](SECURITY.md)
-  Threat model, deployment caveats, and vulnerability disclosure guidance.
+- [docs/guide.md](docs/guide.md) Usage guide, transport details, streaming behavior, extensions, and examples.
+- [SECURITY.md](SECURITY.md) Threat model, deployment caveats, and vulnerability disclosure guidance.
 
 ## Development
 
-For contributor workflow, local validation, and helper scripts, see
-[CONTRIBUTING.md](CONTRIBUTING.md) and [scripts/README.md](scripts/README.md).
+For contributor workflow, local validation, and helper scripts, see [CONTRIBUTING.md](CONTRIBUTING.md) and [scripts/README.md](scripts/README.md).
 
 ## License
 

{opencode_a2a-0.6.0 → opencode_a2a-0.6.1}/README.md

@@ -2,16 +2,12 @@
 
 > 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.
+`opencode-a2a` adds an A2A runtime layer to `opencode serve`, with auth, streaming, session continuity, interrupt handling, and a clear deployment boundary.
 
 ## What This Is
 
-- An A2A adapter service built on `opencode serve`, with inbound runtime
-  exposure plus outbound peer calling.
-- It supports both roles in one process: serving as an A2A Server and hosting an
-  embedded A2A Client for `a2a_call`.
+- An A2A adapter service built on `opencode serve`, with inbound runtime exposure plus outbound peer calling.
+- It supports both roles in one process: serving as an A2A Server and hosting an embedded A2A Client for `a2a_call`.
 
 ## Architecture
 
@@ -54,8 +50,7 @@ Upgrade later with:
 uv tool upgrade opencode-a2a
 ```
 
-Make sure provider credentials and a default model are configured on the
-OpenCode side, then start OpenCode:
+Make sure provider credentials and a default model are configured on the OpenCode side, then start OpenCode:
 
 ```bash
 opencode auth login
@@ -63,10 +58,7 @@ opencode models
 opencode serve --hostname 127.0.0.1 --port 4096
 ```
 
-Treat the deployed OpenCode user's HOME/XDG config directories as part of the
-runtime state. If a packaged or service-managed deployment appears to ignore
-fresh provider env vars, inspect that user's persisted OpenCode auth/config
-files before assuming the A2A adapter layer is overriding credentials.
+Treat the deployed OpenCode user's HOME/XDG config directories as part of the runtime state. If a packaged or service-managed deployment appears to ignore fresh provider env vars, inspect that user's persisted OpenCode auth/config files before assuming the A2A adapter layer is overriding credentials.
 
 Then start `opencode-a2a` against that upstream:
 
@@ -89,11 +81,9 @@ curl http://127.0.0.1:8000/.well-known/agent-card.json
 
 ## Capabilities
 
-- A2A HTTP+JSON endpoints such as `/v1/message:send` and
-  `/v1/message:stream`
+- 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, and JSON-RPC `agent/getAuthenticatedExtendedCard`
 - 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
@@ -122,21 +112,11 @@ opencode-a2a call http://other-agent:8000 "How are you?"
 ### Outbound Agent Calls (Tools)
 The server can autonomously execute `a2a_call(url, message)` tool calls emitted by the OpenCode runtime. Results are fetched via A2A and returned to the model as tool results, enabling multi-agent orchestration.
 
-When the target peer agent requires bearer auth, configure
-`A2A_CLIENT_BEARER_TOKEN` for server-side outbound calls. When the target peer
-agent requires Basic auth, use `A2A_CLIENT_BASIC_AUTH`.
-These outbound credentials apply to the peer specified by `opencode-a2a call`
-or `a2a_call(url, message)`, not to this service's inbound `A2A_BEARER_TOKEN`.
-The CLI intentionally reads outbound credentials from environment variables only,
-so secrets do not appear in shell history or process arguments.
+When the target peer agent requires bearer auth, configure `A2A_CLIENT_BEARER_TOKEN` for server-side outbound calls. When the target peer agent requires Basic auth, use `A2A_CLIENT_BASIC_AUTH`. These outbound credentials apply to the peer specified by `opencode-a2a call` or `a2a_call(url, message)`, not to this service's inbound `A2A_BEARER_TOKEN`. The CLI intentionally reads outbound credentials from environment variables only, so secrets do not appear in shell history or process arguments.
 
-Server-side outbound client settings are fully wired through runtime config:
-`A2A_CLIENT_TIMEOUT_SECONDS`, `A2A_CLIENT_CARD_FETCH_TIMEOUT_SECONDS`,
-`A2A_CLIENT_USE_CLIENT_PREFERENCE`, `A2A_CLIENT_BEARER_TOKEN`, `A2A_CLIENT_BASIC_AUTH`, and
-`A2A_CLIENT_SUPPORTED_TRANSPORTS`.
+Server-side outbound client settings are fully wired through runtime config: `A2A_CLIENT_TIMEOUT_SECONDS`, `A2A_CLIENT_CARD_FETCH_TIMEOUT_SECONDS`, `A2A_CLIENT_USE_CLIENT_PREFERENCE`, `A2A_CLIENT_BEARER_TOKEN`, `A2A_CLIENT_BASIC_AUTH`, and `A2A_CLIENT_SUPPORTED_TRANSPORTS`.
 
-Detailed protocol contracts, examples, and extension docs live in
-[`docs/guide.md`](docs/guide.md).
+Detailed protocol contracts, examples, and extension docs live in [`docs/guide.md`](docs/guide.md).
 
 ## When To Use It
 
@@ -152,24 +132,17 @@ Look elsewhere if:
 - you want this project to manage your process supervisor or host bootstrap
 - you want a general client integration layer rather than a server wrapper
 
-For client-side integration, prefer
-[a2a-client-hub](https://github.com/liujuanjuan1984/a2a-client-hub).
+For client-side integration, prefer [a2a-client-hub](https://github.com/liujuanjuan1984/a2a-client-hub).
 
 ## Deployment Boundary
 
-This repository improves the service boundary around OpenCode, but it does not
-turn OpenCode into a hardened multi-tenant platform.
+This repository improves the service boundary around OpenCode, but it does not turn OpenCode into a hardened multi-tenant platform.
 
 - `A2A_BEARER_TOKEN` protects the A2A surface.
-- Provider auth and default model configuration remain on the OpenCode side; deployment-time
-  precedence details and HOME/XDG state impact are documented in
-  [docs/guide.md](docs/guide.md#troubleshooting-provider-auth-state).
-- Use `A2A_CLIENT_BEARER_TOKEN` for server-side outbound peer calls initiated by
-  `a2a_call`.
-- Deployment supervision is intentionally BYO. Use `systemd`, Docker,
-  Kubernetes, or another supervisor if you need long-running operation.
-- For mutually untrusted tenants, run separate instance pairs with isolated
-  users, containers, workspaces, credentials, and ports.
+- Provider auth and default model configuration remain on the OpenCode side; deployment-time precedence details and HOME/XDG state impact are documented in [docs/guide.md](docs/guide.md#troubleshooting-provider-auth-state).
+- Use `A2A_CLIENT_BEARER_TOKEN` for server-side outbound peer calls initiated by `a2a_call`.
+- Deployment supervision is intentionally BYO. Use `systemd`, Docker, Kubernetes, or another supervisor if you need long-running operation.
+- For mutually untrusted tenants, run separate instance pairs with isolated users, containers, workspaces, credentials, and ports.
 
 Read before deployment:
 
@@ -180,15 +153,12 @@ Read before deployment:
 
 ## Further Reading
 
-- [docs/guide.md](docs/guide.md)
-  Usage guide, transport details, streaming behavior, extensions, and examples.
-- [SECURITY.md](SECURITY.md)
-  Threat model, deployment caveats, and vulnerability disclosure guidance.
+- [docs/guide.md](docs/guide.md) Usage guide, transport details, streaming behavior, extensions, and examples.
+- [SECURITY.md](SECURITY.md) Threat model, deployment caveats, and vulnerability disclosure guidance.
 
 ## Development
 
-For contributor workflow, local validation, and helper scripts, see
-[CONTRIBUTING.md](CONTRIBUTING.md) and [scripts/README.md](scripts/README.md).
+For contributor workflow, local validation, and helper scripts, see [CONTRIBUTING.md](CONTRIBUTING.md) and [scripts/README.md](scripts/README.md).
 
 ## License
 

{opencode_a2a-0.6.0 → opencode_a2a-0.6.1}/SECURITY.md

@@ -2,56 +2,37 @@
 
 ## Scope
 
-This repository wraps OpenCode as an A2A runtime. It exposes A2A
-HTTP+JSON and JSON-RPC interfaces, and adds authentication, task/session
-contracts, streaming, interrupt handling, and runtime guidance. It does not
-fully isolate upstream model credentials from OpenCode runtime behavior.
+This repository wraps OpenCode as an A2A runtime. It exposes A2A HTTP+JSON and JSON-RPC interfaces, and adds authentication, task/session contracts, streaming, interrupt handling, and runtime guidance. It does not fully isolate upstream model credentials from OpenCode runtime behavior.
 
 ## Security Boundary
 
-- `A2A_BEARER_TOKEN` protects access to the A2A surface, but it is not a
-  tenant-isolation boundary inside one deployed instance.
-- One `OpenCode + opencode-a2a` instance pair is treated as a
-  single-tenant trust boundary by design.
-- Tenant isolation across consumers is expected to come from parameterized
-  self-deployment.
-- For mutually untrusted tenants, use separate instance pairs with distinct
-  Linux users, workspace roots, credentials, and runtime ports.
-- Within one instance, consumers share the same underlying OpenCode
-  workspace/environment by default.
-- LLM provider keys are consumed by the `opencode` process. Prompt injection or
-  indirect exfiltration attempts may still expose sensitive values.
-- Payload logging is opt-in. When `A2A_LOG_PAYLOADS=true`, operators should
-  treat logs as potentially sensitive operational data.
-- This project does not ship host bootstrap or process-manager wrappers as an
-  official product capability. Operators remain responsible for file
-  permissions, secret storage, service users, and supervisor-specific hardening.
+- `A2A_BEARER_TOKEN` protects access to the A2A surface, but it is not a tenant-isolation boundary inside one deployed instance.
+- One `OpenCode + opencode-a2a` instance pair is treated as a single-tenant trust boundary by design.
+- Tenant isolation across consumers is expected to come from parameterized self-deployment.
+- For mutually untrusted tenants, use separate instance pairs with distinct Linux users, workspace roots, credentials, and runtime ports.
+- Within one instance, consumers share the same underlying OpenCode workspace/environment by default.
+- LLM provider keys are consumed by the `opencode` process. Prompt injection or indirect exfiltration attempts may still expose sensitive values.
+- Payload logging is opt-in. When `A2A_LOG_PAYLOADS=true`, operators should treat logs as potentially sensitive operational data.
+- This project does not ship host bootstrap or process-manager wrappers as an official product capability. Operators remain responsible for file permissions, secret storage, service users, and supervisor-specific hardening.
 
 ## Threat Model
 
-This project is currently best suited for trusted or internal environments.
-Important limits:
+This project is currently best suited for trusted or internal environments. Important limits:
 
 - no per-tenant workspace isolation inside one instance
 - no hard guarantee that upstream provider keys are inaccessible to agent logic
-- bearer-token auth only by default; stronger identity propagation is still a
-  follow-up hardening area
-- operators remain responsible for host hardening, secret rotation, process
-  access controls, and reverse-proxy exposure strategy
+- bearer-token auth only by default; stronger identity propagation is still a follow-up hardening area
+- operators remain responsible for host hardening, secret rotation, process access controls, and reverse-proxy exposure strategy
 
 ## Reporting a Vulnerability
 
-Please avoid posting active secrets, bearer tokens, or reproduction payloads
-that contain private data in public issues.
+Please avoid posting active secrets, bearer tokens, or reproduction payloads that contain private data in public issues.
 
 Preferred disclosure order:
 
-1. Use GitHub private vulnerability reporting if it is available for this
-   repository.
-2. If private reporting is unavailable, contact the repository maintainer
-   directly through GitHub before opening a public issue.
-3. For low-risk hardening ideas that do not expose private data, a normal
-   GitHub issue is acceptable.
+1. Use GitHub private vulnerability reporting if it is available for this repository.
+2. If private reporting is unavailable, contact the repository maintainer directly through GitHub before opening a public issue.
+3. For low-risk hardening ideas that do not expose private data, a normal GitHub issue is acceptable.
 
 ## Supported Branches
 

{opencode_a2a-0.6.0 → opencode_a2a-0.6.1}/SUPPORT.md

@@ -17,10 +17,8 @@ Open a GitHub issue when you can provide:
 
 ## Security Concerns
 
-Do not post active secrets, bearer tokens, or sensitive workspace data in a
-public issue. Use the disclosure guidance in [SECURITY.md](SECURITY.md).
+Do not post active secrets, bearer tokens, or sensitive workspace data in a public issue. Use the disclosure guidance in [SECURITY.md](SECURITY.md).
 
 ## Commercial Or SLA Support
 
-This repository does not currently advertise a separate SLA or managed support
-channel. GitHub issues are the default public support path.
+This repository does not currently advertise a separate SLA or managed support channel. GitHub issues are the default public support path.