#700 fix(sdk): accept @agent-relay/sdk and harness-driver 16 as optional peers

Why

The agent-relay 16.0.0 release (publish run 41807496212) failed in Build & Version. Relay's packages/cli/src/cli/relayflows-peer-compat.test.ts installs the pinned @relayflows/sdk@2.0.60 beside @agent-relay/sdk and @agent-relay/harness-driver at the version being released. 2.0.60's optional peer range is >=12.3.1 <13 || >=15.1.0 <16, so npm rejects 16.0.0 with ERESOLVE. Nothing was published.

Change

• packages/sdk peers @agent-relay/sdk and @agent-relay/harness-driver: >=12.3.1 <13 || >=15.1.0 <17 (the lockfile's root entry is updated to match).

Compatibility

git diff v15.1.1 origin/main -- packages/sdk packages/harness-driver in relay is empty. The 16.0.0 major is the desktop core (agent-relay-probe) contract, so the SDK surface flows uses is the same as 15.1.x. The relay test still requires the next major (17) to be rejected, and <17 does that.

Tests

packages/sdk vitest on this Mac: the same 18 files fail on origin/main without this change (live, kernel and CLI tests that need a local relayflowd or cloud sign-in). With the change, one more live test failed once (authored-parallel-run-live, "f.run after done()", a local runtime flake). A peer range in package.json can't change runtime behavior.

After merge

1. Publish @relayflows/sdk (patch: 2.0.61).
2. In relay, bump the @relayflows/sdk pin in the root package.json (dependency and overrides) and in packages/cli/package.json.
3. Re-dispatch agent-relay publish.yml with custom_version=16.0.0.

🤖 Generated with Claude Code

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}