Fix #1199: Recommend workspace start for unregistered workspaces

[mohidmakhdoomi]

Summary

Corrects afx status guidance when Tower is already running but the current workspace is not registered. The command now directs users to activate the workspace rather than redundantly starting Tower.

Fixes #1199

Root Cause

The Tower-running/unregistered-workspace branch retained a stale hard-coded afx tower start recommendation after workspace activation moved to afx workspace start. The separate Tower-not-running branch was already correct.

Fix

• Recommend afx workspace start only when Tower is running and the workspace is unregistered.
• Preserve the afx tower start recommendation when the Tower daemon is not running.
• Add regression coverage for both branches and their distinct messages.

Test Plan

• Focused regression suite: pnpm --filter @cluesmith/codev test --run src/agent-farm/__tests__/spec-1057-status-owner.test.ts (17 passed)
• Build: porch check bugfix-1199
• Full test suite: porch check bugfix-1199

[mohidmakhdoomi]

Architect Integration Review

Risk: Medium by raw file count (4 files), though the substantive scope is low: one production-line correction, focused regression coverage, and two protocol artifacts.

Root cause: The Tower-running / unregistered-workspace branch retained stale guidance to run afx tower start, even though Tower is already running.

Fix: The branch now recommends afx workspace start; the separate Tower-not-running branch remains unchanged and continues to recommend afx tower start.

Verification:

• Reviewed the complete diff and surrounding branch logic.
• Ran spec-1057-status-owner.test.ts: 17/17 passed.
• Independent Claude integration review: APPROVE (high confidence).
• Builder CMAP: Gemini, Codex, and Claude all APPROVE.

No integration, security, API, or dependency concerns found. Architect review approves the change; required GitHub checks are still in progress.

---

Architect integration review