#2081 chore(cli): pin @relayflows/cli 1.1.9 so flows run on the Relay 16 broker

Why

@relayflows/cli 1.1.8's core depends on @agent-relay/{sdk,cloud,config,harness-driver,harnesses} ^12.2.2.

• A stock agent-relay@16.0.0 install therefore nests the 12.4.1 packages under core, and agent-relay cloud worker starts flows on the 12.4.1 broker.
• On the self-hosted proof (gcp-proof), that broker fails at startup: failed to initialize relaycast session / HTTP error: error decoding response body. The same worker with a 16.0.0 broker in that slot completes the run.

Change

• Pin @relayflows/cli 1.1.9 (AgentWorkforce/relayflows#66). Its core accepts ^12.2.2 || ^16.0.0, so it dedupes onto this repo's 16 packages and broker. No @agent-relay 12.x entries remain in the lockfile.
• The lockfile also syncs the workspace versions that the v16.0.0 release commit left at 15.1.1. The release workflow discards lockfile changes, so main's lock still said 15.1.1.
• CHANGELOG: one line under [Unreleased - Major] / Fixed.

Note: this lands on main after #2069, so it ships in the next release from main (17.0.0).

Tests (local)

• npm ci is clean.
• npm run typecheck passes.
• peer-compat, cloud-worker and cloud-worker-cli-credentials tests: 31/31 pass.
• A worker image built as agent-relay 16.0.0 with an override to @relayflows/cli 1.1.9 resolves a single @agent-relay/sdk 16.0.0 (deduped) and a single 16.0.0 broker.

🤖 Generated with Claude Code

---

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