docs(release): v0.2.0 pre-publish testing checklist

Ten-step hands-on checklist the maintainer runs locally before
bumping the version and cutting the release. Covers every P10.x
capability end-to-end: backward compat smoke, multi-workspace
attach + conflict reject, --force, ACP --target, A2A
contextRoutes, reply.target, cross-target isolation, docs review.
Also includes the post-checklist bump + publish pointer to the
existing publish.md runbook and a 72h rollback note.

Scope note: codex peer-id (P10.9) is explicitly marked deferred
to v0.3 so testers skip it — codex remains single-instance in
v0.2.0.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: ccd

docs/release/v0.2.0-testing.md

@@ -0,0 +1,242 @@
+# v0.2.0 pre-release testing checklist
+
+Ten hands-on checks covering every Phase 10 capability. Run them
+locally before bumping the version and cutting the release. Each
+step lists the command, the expected observable, and the pass/fail
+line. Stop at the first failure — do not publish.
+
+Scope note: codex peer-id routing (P10.9) is **deferred to v0.3** —
+skip any test involving `a2a-bridge codex --id <id>`. `codex`
+itself still works in single-instance mode (`codex:default`).
+
+## 0. Build and install from source
+
+```bash
+cd /home/ubuntu/robtg/a2a-bridge
+git checkout dev && git pull origin dev
+bun install
+bun run check:ci
+```
+
+Expected: all four check:ci stages green (tsc, depcruise, tests,
+smoke tarball + smoke-e2e). `455 pass 0 fail`.
+
+Then install the freshly-packed tarball into a scratch directory
+so the global npm install of `a2a-bridge@0.1.x` stays untouched
+while you test:
+
+```bash
+npm pack
+mkdir -p /tmp/a2a-v020-test && cd /tmp/a2a-v020-test
+npm init -y >/dev/null
+npm install /home/ubuntu/robtg/a2a-bridge/a2a-bridge-*.tgz
+./node_modules/.bin/a2a-bridge --version
+```
+
+Expected: `a2a-bridge v0.1.1` (the CHANGELOG is drafted as 0.2.0
+but the bump hasn't landed yet — that's step after this checklist).
+
+Keep two terminals open. `TEST_DIR=/tmp/a2a-v020-test` below.
+
+## 1. Backward compat: v0.1 single-CC flow still works
+
+```bash
+# Terminal A — fresh daemon
+A2A_BRIDGE_STATE_DIR=/tmp/a2a-v020-test/state-single \
+  $TEST_DIR/node_modules/.bin/a2a-bridge daemon start
+
+$TEST_DIR/node_modules/.bin/a2a-bridge daemon status
+```
+
+Expected: `daemon status` prints pid, control port 4512, A2A port
+4520. No errors about multi-target. Leave it running.
+
+```bash
+# Terminal B — attach a single CC without any target env vars
+$TEST_DIR/node_modules/.bin/a2a-bridge claude --help | head -5
+```
+
+(You don't need a real Claude Code session for this checklist —
+we're validating the wiring, not human-in-the-loop UX. The stub
+CC pattern via `DaemonClient` already covers the CC side in the
+test suite.)
+
+Pass: daemon is live, no startup errors, `daemon status` shows a
+single pid, `daemon logs` shows no `force` / `target` rejections.
+
+## 2. `daemon targets` subcommand (P10.5)
+
+```bash
+$TEST_DIR/node_modules/.bin/a2a-bridge daemon targets
+```
+
+With no CC attached yet, expected output is
+`no targets registered`.
+
+In a second shell, simulate an attach by running the existing
+conflict-test subprocess (it attaches a stub CC as `claude:ws-a`):
+
+```bash
+cd /home/ubuntu/robtg/a2a-bridge
+bun test src/cli/claude-conflict.test.ts 2>&1 | tail -10
+```
+
+Expected: `2 pass 0 fail`.
+
+## 3. Multi-workspace attach + conflict reject (P10.2, P10.3, P10.6)
+
+```bash
+cd /home/ubuntu/robtg/a2a-bridge
+bun test src/runtime-plugin/daemon-client/daemon-client.test.ts
+bun test src/cli/claude-conflict.test.ts
+```
+
+Expected:
+- `daemon-client.test.ts` — new tests prove `attachClaude(t, true)`
+  serializes `force: true`; `connectRejected` / `connectReplaced`
+  events fire on incoming frames.
+- `claude-conflict.test.ts` — `2 pass 0 fail`:
+  - second attach without `force` receives `connectRejected`
+  - second attach with `force: true` evicts the first, which sees
+    `connectReplaced` and a socket close.
+
+## 4. `a2a-bridge claude --force` CLI flag (P10.6)
+
+```bash
+cd /home/ubuntu/robtg/a2a-bridge
+bun test src/cli/claude-flags.test.ts
+```
+
+Expected: `4 pass 0 fail`. The parser strips `--force`, preserves
+argv order, rejects partial matches like `--forceful`.
+
+Manual sanity:
+
+```bash
+$TEST_DIR/node_modules/.bin/a2a-bridge claude --force 2>&1 | head -3
+```
+
+Should NOT fail with "unrecognized option". The CLI strips the
+flag and forwards the remaining argv to the native `claude`
+binary; if you don't have Claude Code installed, the error you
+get is about missing `claude`, not about `--force`.
+
+## 5. ACP `--target` flag (P10.4)
+
+```bash
+cd /home/ubuntu/robtg/a2a-bridge
+bun test src/cli/acp-cli.test.ts src/runtime-daemon/inbound/acp/turn-handler.test.ts
+```
+
+Expected:
+- `acp-cli.test.ts` — `--target`, `-t`, and `--target=` all parse;
+  invalid target exits 1 with a descriptive error.
+- `turn-handler.test.ts` — `19 pass`: unattached target →
+  `acp_turn_error`; attached target → turn forwards.
+
+## 6. A2A `contextId → TargetId` routing (P10.7)
+
+```bash
+cd /home/ubuntu/robtg/a2a-bridge
+bun test src/runtime-daemon/inbound/a2a-http/server.test.ts
+```
+
+Expected: the three P10.7 cases pass — mapped contextId routes to
+its TargetId, unmapped falls back to `claude:default`, malformed
+TargetId in the config is a startup error.
+
+Operator sanity: with a daemon running, set the env var and
+verify via `daemon logs`:
+
+```bash
+A2A_BRIDGE_CONTEXT_ROUTES='{"ctx-smoke":"claude:default"}' \
+  $TEST_DIR/node_modules/.bin/a2a-bridge daemon start
+```
+
+The daemon should start without logging an `ignored` line — if
+you see `A2A_BRIDGE_CONTEXT_ROUTES ignored`, the JSON was
+malformed.
+
+## 7. Outbound `reply` tool target (P10.8)
+
+```bash
+cd /home/ubuntu/robtg/a2a-bridge
+bun test src/cli/reply-target.test.ts
+```
+
+Expected: `2 pass 0 fail`.
+- **forward**: CC-A replies with `target: claude:ws-b`; CC-B
+  receives the text.
+- **unknown target**: descriptive error.
+- **omit target**: falls through to the legacy codex path (errors
+  with "Codex is not ready" since the test daemon has no Codex
+  adapter attached — proves the absent-target path is unchanged).
+- **malformed target**: error.
+
+## 8. Cross-target isolation — the big one (P10.10)
+
+This is the Phase 10 acceptance test. Two ACP subprocesses, two
+stub CCs, ensures no cross-talk.
+
+```bash
+cd /home/ubuntu/robtg/a2a-bridge
+bun test src/cli/multi-target.test.ts
+```
+
+Expected: `1 pass 0 fail`. Subprocess A sees only `CC-A:` prefixed
+chunks; subprocess B sees only `CC-B:`; no fallback to the echo
+executor.
+
+## 9. Full check:ci one more time
+
+```bash
+cd /home/ubuntu/robtg/a2a-bridge
+bun run check:ci
+```
+
+Expected: `455 pass 0 fail`, smoke tarball OK, smoke-e2e OK.
+
+## 10. Docs review
+
+Quick eyeball pass on the updated docs:
+
+- [`README.md`](../../README.md) — "Multi-workspace routing
+  (v0.2)" section + env vars table has `WORKSPACE_ID`,
+  `FORCE_ATTACH`, `CONTEXT_ROUTES`.
+- [`docs/design/multi-target-routing.md`](../design/multi-target-routing.md)
+  — status line says "implemented in v0.2.0".
+- [`docs/guides/rooms.md`](../guides/rooms.md) — TargetId
+  precedence table + outbound reply routing section present.
+- [`docs/join.md`](../join.md) — "Multi-workspace (v0.2,
+  optional)" section at the bottom.
+- [`CHANGELOG.md`](../../CHANGELOG.md) — `[0.2.0]` block drafted
+  with Added / Changed / Deferred / Wire additions.
+
+## After the checklist — version bump + publish
+
+Once every step above passes:
+
+1. Bump `package.json`, `plugins/a2a-bridge/plugin.json`, and
+   `plugins/marketplace.json` from `0.1.1` to `0.2.0`.
+2. Change the CHANGELOG header from `## [0.2.0] — unreleased`
+   to `## [0.2.0] — <today>`.
+3. Follow [`publish.md`](./publish.md) from step 1 (bump check) —
+   it covers `bun scripts/check-plugin-versions.js`, commit + tag
+   + push, GitHub Actions release workflow, npm 2FA OTP, and the
+   post-publish smoke.
+
+Per CLAUDE.md iron law: none of the bump / publish steps run
+under the autonomous loop.
+
+## Rollback
+
+If publish lands but smoke fails:
+
+```bash
+npm unpublish a2a-bridge@0.2.0      # must be within 72h
+git tag -d v0.2.0
+git push origin :refs/tags/v0.2.0
+```
+
+(Unpublish only works in the 72-hour window — after that, cut
+`0.2.1` instead.)