Desktop/CLI setup friction found while setting up groot + MBP

Found during setup on 2026-10-14 and 2026-10-23 (report data/operations/t3code-setup.md) and later use.

#	Problem	State
1	Nightly on Arch: the AUR `t3code-bin` / `t3code-nightly-bin` packages can't self-update, so we switched to a writable AppImage.	Worked around. Docs could say this.
2	`t3 update` downloaded 0.1.2 but left `t3` pointing at the old desktop-managed Electron wrapper. The official `install.sh` fixed it.	Similar to upstream `14609`. Add a repro there.
3	The `claude-history-home` provider instance (second Claude home) reports `error` while canonical Claude is ready.	Open, undiagnosed.
4	Usage misses OMP (`~/.omp/agent/sessions`; T3 reads only `~/.pi/agent/sessions`) and has no Hermes reader.	A patch for the OMP path exists but isn't tested or deployed. Hermes counters are cumulative per session, so they need care.
5	No CLI for settings or providers. Disabling Codex/Claude meant editing `~/.t3/userdata/settings.json` by hand. Still true on upstream main (`apps/server/src/cli` has no settings command).	Feature gap, needs Ideas approval.
6	Delegation picked Claude Code/Codex workers when the owner wanted everything in Hermes ("how can we stop t3code from launching codex or claude code").	Resolved by disabling those providers in settings.
7	The MBP's Hermes doesn't advertise ACP, and OMP `session/new` hangs while its MCP servers start.	Harness-side, not T3.
8	The owner is on stable 0.1.2; upstream main has moved far ahead (`doctor`, `triage`, `update` changes).	Update before reporting anything that may already be fixed.

T3 Connect login, S25 push, and desktop load-balancing were left as an owner checklist on 10-23 and are still unverified.

Acceptance