l0ng-ai b48bb0ada1 feat(daemon): pane facts flow from the pane server into the machine tree ...

The tree's pane records are only worth reviving from if they hold what
the machine itself observed, so the pane server now publishes into the
MachineStore the daemon serves: the reader thread reports OSC 7 / probed
cwd changes and the sniffer's agent facts (identity, native session id,
launch argv, coarse status) after each chunk that changed them, and
DeathReporter::report flips the record to live == false however the
death was noticed — that flag is the client-visible 'awaiting revival'
state, and it now comes from the process that owns the PTYs on the very
event, not only from the next restart.

The store rides a process-wide slot (installed by control_services,
same shape as the control event observer) so the three pane-spawn paths
need not thread it through; without one installed, observing is a
no-op, which keeps unit tests and tree-less servers quiet. Facts are
published outside the pane state lock and only on a real change, so the
reader's hot path pays two clones and a compare. AgentFacts.status
tightens from a free string to the existing AgentStatus enum while no
wire client depends on it.

2026-07-29 21:10:57 +08:00

..

tty7-core

feat(daemon): pane facts flow from the pane server into the machine tree

2026-07-29 21:10:57 +08:00

tty7-server

feat(control): machine-tree verbs and incremental Layout deltas

2026-07-29 21:01:58 +08:00