fleet enable/disable/config/inherit always fail: relaycast#212 removed the fleet-nodes API

[khaliqgant]

Problem

agent-relay fleet enable, fleet disable, fleet config and fleet inherit always fail on 12.4.1:

$ agent-relay fleet enable
RelaycastMessagingClient.workspace.fleetNodes requires @relaycast/sdk with the workspace fleet nodes API.

Seen live on 2026-09-22 with a fresh workspace (workspace create) on agent-relay 12.4.1, @relaycast/sdk 8.11.7 (latest).

Root cause

relaycast#212 (8f24574b, "Add first-class node delivery contracts") removed the per-workspace fleet rollout flag completely: the GET/PUT /v1/workspace/fleet-nodes endpoint, packages/engine/src/middleware/fleetNodes.ts, and the TS SDK's workspace.fleetNodes.get/set/inherit helpers (added in relaycast#199). Relay's CLI still calls them:

• packages/cli/src/cli/commands/fleet.ts:1122-1156 (config / enable / disable / inherit)
• packages/sdk/src/facade.ts:207 (fleetNodes on the workspace facade)
• packages/sdk/src/messaging/relaycast.ts:1294 (requireWorkspaceFleetNodes, the throw)

Fleet placement now works without the flag. In the same run, two nodes (node up) registered as online/live with spawn:* capabilities and accepted targeted spawns, all without fleet enable.

Expected

These four commands shouldn't dead-end on an SDK-internal error. Suggested fix:

• Remove fleet enable|disable|inherit, or keep them as hidden no-ops that print "fleet nodes are always on; this command is no longer needed" and exit 0, for back-compat with scripts and docs that still run fleet enable.
• Remove fleet config or repoint it at something real. Drop workspace.fleetNodes from the SDK facade and RelaycastMessagingClient.
• Update tests (fleet.test.ts) and any docs or CLI help that say fleet is "off by default".

Acceptance

• agent-relay fleet enable on a fresh workspace exits 0 (or the command is gone) and never prints the requires @relaycast/sdk error.
• No remaining fleetNodes references in packages/sdk/src or packages/cli/src.
• A changelog entry under [Unreleased].

[khaliqgant]

Direction: remove, don't restore. Removing the flag was intentional. It came from relaycast#194 as a Phase 6 rollout gate for node-based delivery. relaycast#212 then removed it in its "Make node delivery unconditional" commit, once node delivery became the only delivery path (the broker only delivers over node-control since 9.1.x). A workspace with fleet "disabled" would get no delivery at all, so there's no meaningful off switch left.

Don't re-add /v1/workspace/fleet-nodes or the SDK helpers. Fix it on the relay side: make fleet enable|disable|inherit hidden no-ops (or remove them), remove or repoint fleet config, and delete the workspace.fleetNodes facade.

[khaliqgant]

Fixed by #1842, merged as 12ce647.

agent-relay fleet config|enable|disable|inherit now exit successfully as hidden compatibility no-ops instead of failing on the workspace rollout API that relaycast#212 removed. workspace.fleetNodes and RelayWorkspaceFleetNodesConfig are removed from @agent-relay/sdk, with the pending release raised to Major and migration guidance in the changelog.

Closing manually: #1842 was opened by the Software Garden before the flow carried a closing reference, so GitHub could not auto-close this issue.