Background work that comes back after the lead's turn has ended: whether it picked its discussion up, joined a run that was still working, was held with a line saying why, or was dropped because the discussion was stopped; helpers kept running past their run; and the watchers the lead set. background.wake itself is on the first page, with the runs.
Background work and watchers
| Type | Reported by | When | Detail carries |
|---|---|---|---|
background.wake_joined | Mac | Background work finished while the discussion was running, and joined that run at its next step. | kinds, count |
background.wake_held | Mac | Background work finished but did not pick its discussion up — a cap, a ceiling, a lapsed team — and a line says why. | why, count |
background.wake_dropped | Mac | Background work finished in a discussion that was stopped or is gone, so nothing happened. | why, kinds |
delegate.detached | Mac | A run ended with background helpers still working; they carry on and pick the discussion up when they finish. | jobs |
delegate.message | Mac | A lead and a helper messaged each other mid-run. | parent, child, from, chars |
watcher.started | Mac | The lead set a watcher on something outside (lib/watchers.js). | id, kind, interval, time limit |
watcher.ended | Mac | A watcher saw what it waited for, or gave up at its time limit. | id, kind, state, checks |
watcher.stopped | Mac | A watcher was stopped, from Background Tasks or by the lead. | id |
background.wake_off | Mac | Don't Pick Up Background Results was turned on or off for a discussion. | on |
watcher.stopped_all | Mac | Stop on the discussion stopped all its watchers. | why |
discussion.relayed | Mac and server | A seat sent a message from one of the person's discussions to another, which started its room or joined its run. | from, to, by, hop |
memory.seat_changed | Mac and server | A seat saved, reworded or forgot a note in project or personal memory with its memory tool. | action, scope, review |
What these do not carry
Kinds and counts, never a report: what a helper wrote, what a command printed or what a watcher read stays in the discussion. A watcher is named by its id and its kind, never its command or its address.