Spike: OpenBot on T3 (Computer tab, Bot as thread, mode toggle)

[lukemaj]

Outcome

Evidence for how OpenBot (toolboxmd/openbot) lands on this fork as a UI mode, measured the same way as spike #3.

Questions, each with evidence (verified / inference / unknown)

1. Computer tab: can OpenBot's Computer (one Docker Screen container, KasmVNC displays, proxy with injected basic auth, view-only preview and zoom-to-write) run as a right-panel tab next to Agents? Build it and prove it live.
2. Bot as a thread: can a Bot (name, title, description, harness, isolated or host, its own display) be a T3 thread plus a persona and provider instance? What does T3 lack?
3. Channels: what do group and Bot-to-Bot Channels need that T3 threads lack?
4. Mapping: Bot, Channel, Chat, Session, Home, Workspace onto T3 threads, projects and provider instances, as a table for OpenBot's CONTEXT.md.
5. Mode toggle: the smallest way to switch between the standard T3 UI and a chat-first OpenBot UI following OpenBot's DESIGN.md, reusing client-runtime.
6. Retired code: which parts of OpenBot's daemon/src (acp, harness, harness-home, supervise, bots, computer, kasm) T3 replaces, and which move into the fork.
7. Upstream cost: upstream files edited, lines, and their 90-day upstream churn.

Deliverables

A findings comment here with a go / go-with-changes / no-go recommendation, and one draft PR on a spike branch (never merged) splitting new files from edited upstream files.

Constraints

Never touch the user's running T3 instance (port 3773, ~/.t3/userdata); use an isolated T3 home and port. Never use host Kasm port 6901. No credentials in commits.

Blockers

Direction confirmation in #5 and toolboxmd/openbot#142.

Objective contribution

Third completion criterion of the draft Objective in #5.