company: replace the Desks console surface with an org hierarchy tree

[oxoxDev]

Context

#302 removes the Desk nav entry for the v1 IA cut. Every desk route, store and test stays — only the way in closes. The consequence, stated plainly there: desk creation and membership editing become unreachable, because those dialogs are console-only. From #302 onward, desks are editable by hand in the manifest and nowhere else.

That is accepted as a temporary state, not a destination.

What this issue is for

The roadmap's terminology map already has the successor: Desks become nodes/teams on the Company org chart, with a hard limit of three levels. The org chart is the intended home for structure — a hierarchy tree where a seat (agent or human) is a node, rather than a flat desk list on its own page.

So the work is not "restore the Desks page". It is: build the hierarchy surface that makes the Desks page unnecessary, and route creation and membership editing through it.

Scope to settle when this is picked up

• Where the tree lives (a Company surface, or folded into Team).
• Whether the three-level cap is enforced in the host, the console, or both.
• Whether desk threads in Conversation (untouched by nav: remove Inbox, Desk, Brains and Finances from the sidebar #302, derived from the same data) keep their current shape or become a view of the tree.
• Migration: existing desks are already durable, so this is a new reader over existing data, not a data change.

Not in scope

Anything that re-adds a flat Desks nav entry. If desk management needs an interim home before the tree exists, say so explicitly and choose one — do not reintroduce the removed surface by default.

Related

• nav: remove Inbox, Desk, Brains and Finances from the sidebar #302 — the nav cut that creates the gap
• EPIC: the spine — prompt → task → plan → build → approve → output link #183 — MVP spec epic (§2 Navigation / IA)

---

Testing — required, and this one is bound to the UI

This issue has a user-facing surface, so it is verified on that surface. A green unit or component test is not evidence that this is fixed, and does not close it.

Before this is done:

• Run the console against a live host and walk the exact path described above, by hand, in a browser.
• Exercise the failure this issue describes, not only the happy path — the fix is that the described behaviour is gone, so the old behaviour is what you have to try to reproduce.
• If a Playwright spec covers it, that spec must actually run and pass in a lane that builds it. A suite that is compiled out of CI proves nothing (see ci: the integration suite runs nowhere — feature-gated out of one job, --lib'd out of the other #475).
• State in the PR what you ran it against and what you saw. "Tested" on its own is not a result.

Backend-only changes may be verified from the backend. Anything with a screen is verified on the screen.