acp-adapter-authoringlisted
Install: claude install-skill RelayMessenger/Relay-SDK
# ACP Adapter Authoring
## Establish ground truth
1. Locate the developer repository root. Treat paths below as repository-relative.
2. Run `git status --short`, `git branch --show-current`, and `git rev-parse --short HEAD`. Preserve unrelated changes.
3. Read `packages/relaymessenger/README.md`, the target runtime's catalog/adapter code, its tests, its package manifest, and `package-lock.json` before editing.
4. Inspect the installed runtime directly with `<binary> --version` and its non-interactive readiness check. Inspect the latest upstream release separately. Record both; do not silently make them equal.
5. Decide whether the integration is an **engine** or a **channel** before writing code.
Use this ownership map:
| Concern | Owning source |
| --- | --- |
| Engine names and external runtime specs | `packages/relaymessenger/src/engine/catalog.ts` |
| ACP process, handshake, sessions, turns, permissions | `packages/relaymessenger/src/engine/acp.ts` |
| Engine process-tree shutdown | `packages/relaymessenger/src/engine/process.ts` |
| Engine boundary types | `packages/relaymessenger/src/engine/types.ts` |
| Engine selection and lifecycle | `packages/relaymessenger/src/flags.ts`, `packages/relaymessenger/src/cli.ts` |
| External runtime preflight | `packages/relaymessenger/src/doctor.ts` |
| Durable conversation/session binding | `packages/relaymessenger/src/store.ts` (`SessionStore`) |
| Relay receive/turn/reply loop | `packages/relaymessenger/src/receive.ts` |
| Permi