Follow-up direction for daemon process

[unive3sal]

Follow-up direction

• Add better TUI visibility for daemon/worker state: running status, worker port, pid, last
  restart, and recent error.
• Improve user-facing errors for common daemon cases: port in use, daemon start failure,
  worker start failure, stale socket recovery, and live config restore failure.
• Add more regression coverage for mixed TUI/CLI toggles, multi-app enable/disable order,
  daemon crash recovery, worker crash recovery, and old config migration.
• Add a short architecture note explaining daemon vs worker vs CLI/TUI responsibilities,
  desired state vs runtime state, and shutdown/recovery behavior.

Originally posted by @SaladDay in #189 (comment)