Tower: workspace display names can collide — two workspaces named 'codev' are indistinguishable to controller clients #1391

Context

Live-hardware testing during #1347's dev-approval pass surfaced this (recorded in codev/reviews/1347-migrate-the-stream-deck-plugin.md, follow-up findings): with two registered workspaces both named codev, the Stream Deck workspace navigator's touch strip shows two identical entries — the operator cannot tell which one they are about to act on. Any controller client rendering TowerWorkspace summaries (Stream Deck today, mobile next) has the same problem; keys and dials fire real verbs (approve-gate, spawn), so acting on the wrong workspace is a live risk, not a cosmetic one.

Root cause

Tower workspace summaries carry no uniqueness guarantee for display names — the name derives from the directory basename, and distinct paths share basenames.

Possible directions (implementer/architect to choose)

1. Tower-side: disambiguate display names in the overview/workspace payloads when basenames collide (e.g. append the minimal distinguishing path suffix), so every client benefits with no client changes.
2. Client-side fallback: controller clients render a distinguishing suffix themselves from path. Weaker: every client re-implements it.

Option 1 keeps the single-source-of-truth posture.

Acceptance

Two workspaces with the same basename are visually distinguishable in the Stream Deck workspace navigator without plugin changes (if option 1) and in the dashboard's workspace list.