feat(home): port Home agent onto stable v0.1.6 - #15

Port pingdotgg#15975 onto the fork's main. Built from the v0.1.6
port (fork PR #15), replayed onto main with four conflicts resolved.

Restores what the v0.1.6 port dropped:
- mod+shift+0 opens Home (handler in shortcuts/commandPaletteCommands).
- Watch reports render as "Sent by T3 Code", not as the user's own message.
- Messages Home sent are labeled "Home" even when its thread lives on another
  environment, and "Open thread" opens it on the hub.

Fixes Home settings offering no model when the first enabled provider is not
ready (for example Codex enabled but not installed).

Co-Authored-By: Claude Opus 5.5 <[email protected]>

…nes (#16)

* feat(home): add Home, an agent that manages threads across your machines

Port pingdotgg#15975 onto the fork's main. Built from the v0.1.6
port (fork PR #15), replayed onto main with four conflicts resolved.

Restores what the v0.1.6 port dropped:
- mod+shift+0 opens Home (handler in shortcuts/commandPaletteCommands).
- Watch reports render as "Sent by T3 Code", not as the user's own message.
- Messages Home sent are labeled "Home" even when its thread lives on another
  environment, and "Open thread" opens it on the hub.

Fixes Home settings offering no model when the first enabled provider is not
ready (for example Codex enabled but not installed).

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* fix(home): Home's calls to other environments use its relay, not peer links

Main forwards every tool that takes a linked environment through PeerForwarding
and strips environmentId first, so Home's routing never saw the target. When
Home names another environment, the tools that route Home now reach its own
routing, and its other linked-environment tools refuse instead of using a peer
link. That also keeps a full-access peer link from bypassing Home's no-delete
rule. delegate_task keeps its own environment field and is unchanged.

Also from review: a watch report needs createdBy "system" to show as T3 Code,
and "Open thread" for a Home sender opens it in whichever environment has it.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* fix(home): the desktop relay runs each request once

HomeRelay built a new consumer atom whenever its registration changed. A
new consumer started with an empty handled set and an immediate read, and
consumers could stay live after a reconnect, so one Home call ran on the
other environment two or three times. Launches then failed with "failed
during create-thread" even though the thread was created.

The relay now keeps one consumer. A new registration rebuilds it through
an atom, and the handled set lives with the relay.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

* fix(home): relayed calls survive re-registration, retries, and bursts

From review of the relay fix:
- The same window re-registering no longer fails the calls it still owes.
  They move to its new queue, along with anything not yet delivered.
- A retried Home launch keeps its command id, so it replays instead of
  failing because the thread already exists.
- The relay stream publishes every request. Stream atoms keep only the last
  value of a chunk, which could drop one of two parallel calls.
- A long Home thread title is cut by code point, so it cannot split an emoji.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

---------

Co-authored-by: Claude Opus 5.5 <[email protected]>