crewbus 10.0.7 → 10.0.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,26 @@
1
1
  # Changelog
2
2
 
3
+ ## 10.0.9 (2026-10-17)
4
+
5
+ MINOR RELEASE: Workbench compound-memory layer (artifacts, lessons, needs-by) + opencode respawn capture fix. No board-schema change (`board.json` stays v2); the additive `artifacts/` and `lessons/` directories appear on first write — old boards pick them up lazily, nothing to migrate.
6
+
7
+ - **Artifacts with adoption (L2)**: `crewbus artifact publish|list|show|adopt|verify`. Spent outputs compound instead of dissipating: `publish --path <path-or-url> [--summary ...] [--deps <art-id,art-id>]` records the reference on the board (deps must exist — publish the dependency first); `adopt`/`verify` stamp the artifact object itself (`adoptedBy`/`verifiedBy` entries with ≤200-char notes), so records move *with the thing* as it gets reused across crews and tasks. Dependency records form feed-forward edges (a message consumed by someone other than the producer), so listing artifacts shows what shipped and what downstream crews actually picked up. `verify` rides the existing `ack --verify` execution ground truth — `works` incidents are inadmissible without output.
8
+ - **Lessons paid forward (L3)**: `crewbus lesson post --scope <group-or-task> --text "..."` (≤800 chars; scope missing = `global`) stores one-liners in `lessons/`; later spawn briefs auto-select matching lessons (this board's groups + global, freshest first, ≤8) into a **Workbench block** alongside recent artifacts. A lesson learned once need not be learned again. Selecting, not caching: nothing rides a cache TTL, and lessons can expire by budget, never by staleness (a strong lesson is more load-bearing than a big one).
9
+ - **Handoff deadlines (L4)**: `send`/`spawn` `--needs-by 30m` stamps a handoff deadline on the DM (positive duration) — *if* an unclaimed brief still matters, deadline math makes it a filter rather than a feeling. `crewbus inbox --overdue` lists still-open briefs past deadline (paired shape `--overdue --unacked` = retry-able work; overdue `--checkpoint` progress notes are skipped — they never need ack). `inbox` shows a `needs-by:` line; digests tag late items with `[OVERDUE]`. Workers triage unacknowledged handoffs on awaken instead of re-polling.
10
+ - **Exact-recipient pinning in spawn briefs**: briefs now say "send to EXACTLY `--to <lead>`" — never invent a recipient name like `<worker>-lead` or `lead` — killing the hallucinated-reply-lane failure mode in auto-named crews.
11
+ - **Gather workbench metrics**: the reduce footer adds workbench counters (`-- workbench: 3 artifact(s) referenced, 4 feed-forward edge(s), 1 adopted, 1 verified --`), and JSON includes a `workbench` metric; an empty board prints a unique "no artifacts referenced" additive line so replayed gathers never wrong-foot a reducer.
12
+ - **Respawn session-capture fix (L1 repair)**: opencode spawn boots the real exe with argv verbatim (no `cmd /c` shim — the session id capture line is no longer swallowed by shell buffering); when the log ends up empty, the spawn record falls back to reading the opencode SQLite session DB (`~/.local/share/opencode/opencode.db`, read-only). `crewbus doctor --harness opencode` now checks opencode drift (binary present, `--format json` supported, session DB readable), so `respawn` reliably lands its catch-up brief in the same conversation.
13
+ - New tests: `test/crewbus.workbench.mjs` (33 checks) + `test/crewbus.opencode-respawn.mjs`.
14
+
15
+ ## 10.0.8 (2026-10-16)
16
+
17
+ PATCH RELEASE: Launch composer UI refinements & desktop companion. No board-schema change (`board.json` stays v2).
18
+
19
+ - **Streamlined Launch Composer**: Removed explicit worker target UI so all launches default to automatic agent naming (`w-1`, `w-2`, ...).
20
+ - **Clearer agent count stepper**: Renamed 'Count' to 'No. of Agents' with improved tooltips for clarity.
21
+ - **Flattened composer aesthetic**: Removed the box-shadow depth effect on the Launch Composer card for a clean, flat panel style.
22
+ - **Cleaned launch console**: Removed redundant static headers ("Launch & Chat") and introductory welcome message ("CrewBus Studio") for a compact, distraction-free console.
23
+
3
24
  ## 10.0.7 (2026-10-14)
4
25
 
5
26
  PATCH RELEASE: Design refresh + icon fix. No board-schema change (`board.json` stays v2).
package/README.md CHANGED
@@ -1,4 +1,4 @@
1
- # crewbus v10.0.6 — DM bus
1
+ # crewbus v10.0.9 — DM bus
2
2
 
3
3
  [![CI](https://github.com/eamonpluto/crewbus/actions/workflows/ci.yml/badge.svg)](https://github.com/eamonpluto/crewbus/actions/workflows/ci.yml)
4
4
 
@@ -55,7 +55,7 @@ env overrides below.)
55
55
  Layout: `board.json`, `agents/<name>.json`, `dm/<recipient>/<id>.json`,
56
56
  `delivered/<recipient>/<id>.json` (push markers, written by the plugin).
57
57
 
58
- Versions: `package.json` (currently 10.0.6) is the source of truth for the
58
+ Versions: `package.json` (currently 10.0.9) is the source of truth for the
59
59
  release version. `board.json`'s `version: 2` is the **board schema version**
60
60
  (a different number on purpose — do not "align" them). New to the project?
61
61
  Start with `docs/QUICKSTART.md` (5 minutes).
@@ -138,7 +138,9 @@ reply across inboxes — feed it to a reducer agent or aggregate it yourself.
138
138
  Group management is CLI-only; agents address groups via `--to-group`
139
139
  (CLI/spawn), `to_group` (MCP, `dm-send` tool). Unknown groups fail loudly so
140
140
  a typo never half-sends. `gather` also prints a telemetry footer
141
- (msgs, ~tokens as chars/4, contributing groups).
141
+ (msgs, ~tokens as chars/4, contributing groups) plus **workbench
142
+ metrics** — artifacts referenced, feed-forward edges, adopted, verified
143
+ (`--json` adds a `workbench` object).
142
144
 
143
145
  Outcomes are native (replaces the old one-group-per-approach +
144
146
  `RESULT:`-subject + verifier-agent + `gather --json` script workaround):
@@ -312,11 +314,38 @@ it. Leads ack workers' replies, and `spawn status` reports the ack state:
312
314
  crewbus ack --from ui-lead --id msg-260924-081159-dedcc7 # handled it
313
315
  crewbus ack --from ui-lead --all # inbox zero
314
316
  crewbus ack --from ui-lead --id <reply> --verify "node test/check.mjs" # verifier hook: exit 0 acks+stores verified:true, else no ack (docs/VERIFIER.md)
315
- crewbus send --from w1 --to ui-lead --reply <brief> --artifact out/w1.json --body "done" # checkable artifact, shown by inbox/gather/thread
316
- crewbus inbox --from ui-lead --unacked # only open items
317
+ crewbus send --from w1 --to ui-lead --reply <brief> --artifact out/w1.json --needs-by 2h --body "done" # artifact + handoff deadline
318
+ crewbus inbox --from ui-lead --unacked --overdue # still-open briefs past --needs-by ([OVERDUE] in digests)
317
319
  crewbus thread --id msg-260924-081159-dedcc7 # brief + all replies, across inboxes
318
320
  ```
319
321
 
322
+ ## Workbench (output that compounds)
323
+
324
+ `artifact publish|list|show|adopt|verify` keeps spent output load-bearing
325
+ for teammates: artifacts are board objects (a `--path` reference + summary
326
+ + deps edges, never inline data) with adoption and verification recorded
327
+ *on the object*, so the next crew starts where this one ended. `lesson
328
+ post|list` stores scoped one-liners that later spawn briefs auto-select
329
+ into a **Workbench block** (this board's groups + global scope, freshest
330
+ first, both bounded) — a lesson learned once need not be learned again:
331
+
332
+ ```powershell
333
+ crewbus artifact publish --from alice --path out/parser.md --summary "40ms parse table" --deps <art-id> # deps must exist; publish upstream first
334
+ crewbus artifact list --from bob # what exists, with adoption/verification state
335
+ crewbus artifact adopt --from bob --id <art-id> --note "wired into prefetch" # records move with the thing
336
+ crewbus lesson post --from alice --scope ui-crew --text "Windows spawns need a real workdir root, not a drive-relative path."
337
+ crewbus gather --batch <batch-id> # footer adds: N artifact(s) referenced, N feed-forward edge(s), N adopted, N verified
338
+ ```
339
+
340
+ `verify` pairs with the verifier hook — checker-verified claims only; a
341
+ bare "works" incident with no captured output is inadmissible (see
342
+ `docs/VERIFIER.md`). Feed-forward edges (a downstream agent consumed an
343
+ artifact its producer did not post) make cross-crew reuse auditable.
344
+ Handoff deadlines (`send`/`spawn --needs-by 30m`) turn stale unclaimed
345
+ briefs into a filter instead of a feeling: `inbox --overdue` (often
346
+ paired with `--unacked`) lists the retry-able set, `needs-by:` shows on
347
+ message reads, and digests tag late items `[OVERDUE]`.
348
+
320
349
  ## Fanning work out (the DM *is* the task)
321
350
 
322
351
  There is deliberately no task object. To "assign N agents", broadcast one
@@ -389,7 +418,11 @@ counted — `--max-spawn N` overrides it when you have the compute.
389
418
 
390
419
  Caps at 20 workers/call by default (`--max-spawn N` overrides — a whole harness each, so budget it like compute); bigger crews
391
420
  get a broadcast DM for live agents to pick up. `--to @all` is refused
392
- (membership is dynamic). Children run with your user privileges — same trust
421
+ (membership is dynamic). Every spawned brief carries a **Workbench block**
422
+ (board lessons matching the crew's scopes + recent artifacts, both
423
+ bounded) and pins the reply lane to the literal `--to <lead>` so
424
+ auto-named workers never invent recipient names. Children run with your
425
+ user privileges — same trust
393
426
  boundary as hooks. Detached children can't answer permission prompts, hence
394
427
  the defaults above; `--auto` means each harness's fully-unattended mode
395
428
  (dangerous — isolated runners only).
@@ -657,7 +690,7 @@ primaries by weight (`serve --weight`, `crew survey`, `crew dispatch`
657
690
  ## Publishing (maintainer)
658
691
 
659
692
  ```powershell
660
- npm test # 20 suites (smoke + harness + compact + tokenfile + digest + control-plane + launch + web-launch + pair-api + web-panel + web-approot + client-runtime + runtime-wiring + desktop-sidecar + mobile-client + approvals x3 + fault-injection + integration), all must pass
693
+ npm test # 24 suites (smoke + harness + opencode-respawn + compact + tokenfile + digest + workbench + control-plane + launch + pair-api + web-launch + web-panel + web-approot + client-runtime + runtime-wiring + desktop-sidecar + mobile-client + holds-quotas + grok-hooks + approval-protocol + approvals-init + approvals-web + fault-injection + integration), all must pass
661
694
  npm publish # ships bin/ + opencode/ + docs (see "files" in package.json)
662
695
  ```
663
696
 
@@ -668,7 +701,7 @@ and verify with `npm test`. `init` prefers the repo files when run from a
668
701
  checkout, so the embed only matters for `npm i -g` installs.
669
702
 
670
703
  Code layout: `bin/crewbus.js` is a dispatcher + `cmd*` wrappers; domain
671
- logic lives in `bin/lib/` (12 modules). See `docs/SPLIT.md` for the module
704
+ logic lives in `bin/lib/` (13 modules). See `docs/SPLIT.md` for the module
672
705
  map, dependency rules, and how to add a command.
673
706
 
674
707
  After publishing, projects can skip the checkout entirely: