Symptom
docs/activity-trace.md presents recv.subagent-spawned / recv.subagent-completed as the trace of subagent activity, but they stay at zero for every remote or local-transcript parent whatever the real activity: overnight trace on v0.0.79, 2 277 class.subagent running:true on one remote parent, 0 recv.subagent-spawned (.work-files/switchboard/trace-2026-09-13-nuit.md, measure 3).
Cause
The trace call sits in the local IPC handler in public/sidebar.js; public/remote-activity-ui.js and public/local-transcript-adapter.js call noteSubagentActivity() directly (#288), bypassing it.
Expected
The trace is emitted from noteSubagentActivity itself, with the source (local-ipc, remote-watch, local-transcript) in the payload, and the doc says so.
Symptom
docs/activity-trace.mdpresentsrecv.subagent-spawned/recv.subagent-completedas the trace of subagent activity, but they stay at zero for every remote or local-transcript parent whatever the real activity: overnight trace on v0.0.79, 2 277class.subagent running:trueon one remote parent, 0recv.subagent-spawned(.work-files/switchboard/trace-2026-09-13-nuit.md, measure 3).Cause
The trace call sits in the local IPC handler in
public/sidebar.js;public/remote-activity-ui.jsandpublic/local-transcript-adapter.jscallnoteSubagentActivity()directly (#288), bypassing it.Expected
The trace is emitted from
noteSubagentActivityitself, with the source (local-ipc,remote-watch,local-transcript) in the payload, and the doc says so.