jason.woltje
3225536adc
feat(bus,cli,plugins,webui): harness-watch-w3: the bus plugins answer carries harnessWatch, one entry per harness (name, state, version, checkedAt, changedAt, failed, line) read from the host's <org dataRoot>/state/harness-watch.json by readWatchView (packages/plugins/src/harness-watch.mjs): read only, no link, FIFO or file over 1 MiB, and a missing, unreadable or wrong-shape file or record gives "not checked yet", never a throw or a guess; the read redacts again with the org and instance roots as known paths; Settings > Routing shows one line per harness under Save harnesses, red and missing in the warning colour, not checked yet never as fit, and one plain line when the answer has no list; the host's watch loads harness plugins from the instance root when there is one, as the launcher does, and keeps state under the org root; new tests: bus start starts the watch through deps.harnessWatch and --no-launch does not (#1873, lane harness-watch-w3)
2026-11-20 10:26:35 -06:00
..
2026-11-11 01:04:15 -06:00
2026-11-11 01:04:15 -06:00
2026-11-10 18:25:54 -06:00
2026-11-11 08:49:15 -06:00
feat(cli,plugins,harness): harness-watch-w2: the bus host runs the harness watch on a timer (a full pass at start, a stat-key pass every 5 minutes, a full pass when the key changes or once a day, none while processing is halted or invalid and one on resume, never two at once, stop aborts the pass) and writes <org dataRoot>/state/harness-watch.json (temp then rename) and harness-watch.jsonl (one line per transition), checked for host paths and env values first; claude-code's fit rule: every flag adapter.sh passes (read from two recorded adapter runs) is in --help and --version answers, captured under unshare -r -n with pi-fit's fallback, a miss is fit fail with the flag as rule id, and preflight refuses harness-feature-missing on that kept verdict; pi-fit failures carry digest and undecided, pi's inspect reads them and its --version capture stops with the signal; the watch takes a signal and keeps flag rule ids (#1873, lane harness-watch-w2)
2026-11-20 07:29:22 -06:00
fix(cli,seat,discord,organization,control-board,harness,plugins,webui): review round: launcher reasons, session, discord reads, mosaic-config and keys by label (#1873)
2026-11-11 08:53:31 -06:00
2026-11-11 14:16:09 -06:00
2026-11-10 21:38:17 -06:00
2026-11-11 01:04:15 -06:00
2026-11-09 11:47:48 -06:00
2026-11-13 20:14:21 -06:00
2026-11-09 19:25:44 -06:00
2026-11-11 01:04:15 -06:00
feat(bus,cli,plugins,webui): harness-watch-w3: the bus plugins answer carries harnessWatch, one entry per harness (name, state, version, checkedAt, changedAt, failed, line) read from the host's <org dataRoot>/state/harness-watch.json by readWatchView (packages/plugins/src/harness-watch.mjs): read only, no link, FIFO or file over 1 MiB, and a missing, unreadable or wrong-shape file or record gives "not checked yet", never a throw or a guess; the read redacts again with the org and instance roots as known paths; Settings > Routing shows one line per harness under Save harnesses, red and missing in the warning colour, not checked yet never as fit, and one plain line when the answer has no list; the host's watch loads harness plugins from the instance root when there is one, as the launcher does, and keeps state under the org root; new tests: bus start starts the watch through deps.harnessWatch and --no-launch does not (#1873, lane harness-watch-w3)
2026-11-20 10:26:35 -06:00
feat(bus,cli,plugins,webui): harness-watch-w3: the bus plugins answer carries harnessWatch, one entry per harness (name, state, version, checkedAt, changedAt, failed, line) read from the host's <org dataRoot>/state/harness-watch.json by readWatchView (packages/plugins/src/harness-watch.mjs): read only, no link, FIFO or file over 1 MiB, and a missing, unreadable or wrong-shape file or record gives "not checked yet", never a throw or a guess; the read redacts again with the org and instance roots as known paths; Settings > Routing shows one line per harness under Save harnesses, red and missing in the warning colour, not checked yet never as fit, and one plain line when the answer has no list; the host's watch loads harness plugins from the instance root when there is one, as the launcher does, and keeps state under the org root; new tests: bus start starts the watch through deps.harnessWatch and --no-launch does not (#1873, lane harness-watch-w3)
2026-11-20 10:26:35 -06:00
2026-11-12 19:19:22 -06:00
2026-11-20 01:17:33 -06:00
2026-11-09 11:47:48 -06:00
2026-11-11 16:32:31 -06:00
2026-11-11 01:04:15 -06:00
2026-11-11 01:04:15 -06:00
2026-11-09 12:58:29 -06:00
2026-11-13 20:14:21 -06:00
2026-11-13 20:14:21 -06:00
2026-11-13 20:14:21 -06:00
2026-11-13 20:14:21 -06:00
2026-11-09 11:47:48 -06:00
2026-11-19 13:13:05 -06:00
2026-11-11 00:11:13 -06:00
2026-11-11 00:11:13 -06:00
2026-11-12 21:02:46 -06:00
2026-11-11 16:32:31 -06:00
2026-11-11 01:04:15 -06:00
2026-11-11 20:47:35 -06:00
2026-11-09 13:17:33 -06:00
2026-11-13 20:14:21 -06:00
2026-11-19 20:41:55 -06:00