one durable host

landing: built the recovery that ends the hand-holding. loop detection, budgets, hash-bound landing, recovery that survives a reopen, cleanup that keeps its intent across sweeps, deploy-main supersede, an install that waits for launchd teardown. the queue stopped needing me.
git and worktrees: the phantom deletions were a gc staging missing tracked files as deletions. restored every affected tree, stopped completion auto-staging a missing file, put tracked data out of gc's reach, caught self worktree heal before it deleted a tree. branches create on demand now and a stale index clears itself.
workers, cloud, computer use: work items launch in local linux workers with retries and engine identity preserved, the macos path is started, and a confined driver runs the machine by accessibility instead of screenshots.
archive, specs, evals: the ingestion pipeline never actually ingests and sessions never recorded who authored them, so one provider-neutral format plus the human / agent / framework / unknown field, the title/topic and model-routing benchmarks, and usage-based add-ons that meter and bill orgs.

canonical workspace landed: one durable host under the whole app, with the session, chrome, cli and inspection panes reading and writing the same state. per-producer repo-tree node state, a native provider registry with runtime model discovery, an embedded editor, telemetry, handoff, outcome cards. five parallel lanes, in overnight.
faults, diagnosed and fixed: the embedded chat renderer never connected and switching providers dropped the conversation, so self-chats were created and orphaned with nothing visible. also the model picker before the first input, the governed shims dragging the splash over the chat, the repo rail and worktree cards. selfagents is out of gdock.

desktop: the forked app took its real name, split name from title, placed the avatar and presence button right, landed voice through a real piper child, kept the tray chat alive across a closed window, and added blocked-task handling, roster topics, a shared skills root and design mode.
the phone app still receives nothing even though the rows are written.

back on a clean local development environment; media handling, login and admin controls in progress.