#67 fix(core): accept @agent-relay/* 17 alongside 12 and 16

Why

agent-relay 17.0.0 is about to ship from relay main. It includes relay #2069, where the core becomes agent-relay-node. @relayflows/core 1.1.9 accepts @agent-relay/* ^12.2.2 || ^16.0.0, so a 17 install would nest a separate 16.0.0 tree and broker under core instead of sharing the CLI's packages.

Change

• packages/core: @agent-relay/{sdk,cloud,config,harness-driver,harnesses} -> ^12.2.2 || ^16.0.0 || ^17.0.0.
• The lockfile changes only those range strings plus the workspace versions synced to 1.1.9. The resolved packages stay at 16.0.0, because 17 isn't published yet.

Compatibility with 17 (#2069)

• git diff v16.0.0 main in relay, across the sdk, cloud, config, harness-driver and harnesses sources, touches only harness-driver/src/install-paths.ts, which renames the PROBE_* exports to RELAY_NODE_*.
• Core imports none of those. It also doesn't reference agent-relay-probe or AGENT_RELAY_PROBE_PATH, and calls none of the removed bridge methods. (In core, "probe" only appears in unrelated file and module checks.)

Tests (local)

• npm run typecheck passes.
• npm test: 65 files, 1130/1130 pass.

🤖 Generated with Claude Code

---

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