afx status recommends `afx tower start` instead of `afx workspace start` for an unregistered workspace

[mohidmakhdoomi]

Bug

When Tower is already running but the current workspace is not registered with it, afx status prints:

Workspace: not active in tower
Run 'afx tower start' to activate this workspace

The suggested command is incorrect: afx tower start starts the shared Tower daemon, which is already running in this branch. It does not activate the current workspace.

Source

packages/codev/src/agent-farm/commands/status.ts contains the stale recommendation in the towerRunning === true / getWorkspaceStatus(workspacePath) === null path:

logger.kv('Workspace', chalk.gray('not active in tower'));
logger.info(`Run 'afx tower start' to activate this workspace`);

The separate Tower-not-running path correctly recommends afx tower start and should remain unchanged.

Expected behavior

For a running Tower where the current workspace is not registered, afx status should print:

Run 'afx workspace start' to activate this workspace

Acceptance criteria

• The unregistered-workspace message recommends afx workspace start.
• The Tower-not-running message continues to recommend afx tower start.
• A regression test covers both branches and their distinct recommendations.

Protocol

BUGFIX — isolated user-facing CLI wording correction with a focused regression test.

[mohidmakhdoomi]

On it! Working on a fix now.