brainclaw 1.7.1 → 1.7.3

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.
@@ -19,7 +19,7 @@ guarantees this changelog follows.
19
19
  to `sha256:860fbaa30a486093` (zod 4). No tool was added, removed,
20
20
  renamed, or had its required arguments change.
21
21
 
22
- **Changed — `bclaw_loop(intent: 'open')` anti-pattern gate (pln#461)**
22
+ **Changed — `bclaw_loop(intent: 'open')` anti-pattern gate (pln#461)**
23
23
  - New optional field `allow_orphan: boolean` on `BclawLoopOpenSchema`.
24
24
  - Default (absent / `false`) — handler rejects with `validation_error`
25
25
  and points to `bclaw_coordinate(intent: 'review', open_loop: true)`
@@ -28,9 +28,20 @@ guarantees this changelog follows.
28
28
  out in `CLAUDE.md`.
29
29
  - `allow_orphan: true` — explicit acknowledgement that the caller
30
30
  will drive `turn()` + dispatch manually (advanced / test use only).
31
- - Internal callers (`bclaw_coordinate`, `bclaw_dispatch`) are not
32
- affected — they bypass `handleBclawLoop` and invoke the core
33
- `openLoop()` directly.
31
+ - Internal callers (`bclaw_coordinate`, `bclaw_dispatch`) are not
32
+ affected — they bypass `handleBclawLoop` and invoke the core
33
+ `openLoop()` directly.
34
+
35
+ **Changed — sequence tools promoted to default discovery (pln#522)**
36
+ - `bclaw_list_sequences`, `bclaw_create_sequence`,
37
+ `bclaw_update_sequence`, and `bclaw_delete_sequence` move from
38
+ `advanced` to `standard`, so fresh agents see them in the default
39
+ `tools/list` catalog. Sequences are a core agent-first coordination
40
+ primitive for parallel dispatch, not an advanced-only admin surface.
41
+ - `bclaw_create_sequence.items` and `bclaw_update_sequence.items` now
42
+ expose the full item shape in JSON Schema: `planId`, optional
43
+ `stepId`, `rank`, `hard_after`, `soft_after`, `lane`, `scope_hint`,
44
+ and `rationale`.
34
45
 
35
46
  ---
36
47
 
@@ -82,7 +93,7 @@ will still succeed. A follow-up PR will strip the dead handler code.
82
93
  changelog records the published MCP surface fingerprint. When a tool
83
94
  name, tier, category, or input schema changes, the test fails until
84
95
  this section is updated.
85
- - MCP public surface fingerprint: `sha256:4a6f612ad952fb52`
96
+ - MCP public surface fingerprint: `sha256:a1881ff57ddce377`
86
97
  (updated 2026-05-27: added the `ref` property to the bclaw_coordinate
87
98
  inputSchema — pln#520 Tier 2 / trp#371, the scope-aware dirty guard;
88
99
  `ref` lets a dispatch build its worktree from an explicit git ref.
@@ -48,11 +48,13 @@ These rules apply to any feature that touches this audience:
48
48
  - `bclaw_check_policy` — scope compliance with glob matching, returns blocks + warnings
49
49
  - `bclaw_who` — list all active agent sessions on the workspace
50
50
 
51
- ### Planning & Sequencing
52
- - `bclaw_create(entity="plan", data)` / `bclaw_update(entity="plan", id, patch)` / `bclaw_transition(entity="plan", id, to)` — shared work planning with priority/effort/assignee/status
53
- - `bclaw_find(entity="plan", filter?)` — list plans
54
- - `bclaw_add_step` / `bclaw_complete_step` / `bclaw_update_step` / `bclaw_delete_step` — plan sub-steps for granular tracking
55
- - `bclaw_create_sequence` / `bclaw_list_sequences` / `bclaw_update_sequence` — multi-step coordination sequences with lane analysis
51
+ ### Planning & Sequencing
52
+ - `bclaw_create(entity="plan", data)` / `bclaw_update(entity="plan", id, patch)` / `bclaw_transition(entity="plan", id, to)` — shared work planning with priority/effort/assignee/status
53
+ - `bclaw_find(entity="plan", filter?)` — list plans
54
+ - `bclaw_add_step` / `bclaw_complete_step` / `bclaw_update_step` / `bclaw_delete_step` — plan sub-steps for granular tracking
55
+ - `bclaw_create_sequence` / `bclaw_list_sequences` / `bclaw_update_sequence` — multi-step coordination sequences with lane analysis
56
+
57
+ Sequence items are explicit lane records: `{ planId, stepId?, rank, hard_after?, soft_after?, lane?, scope_hint?, rationale? }`. `planId` and `rank` are required; `stepId` lets a sequence dispatch a specific plan step instead of the whole plan. A normal parallel flow is: create sequence as `draft`, update it to `active`, run `bclaw_dispatch(intent="analysis")`, then run `bclaw_dispatch(intent="execute", agents=[...])`.
56
58
 
57
59
  ### Multi-Agent Dispatch
58
60
  - `bclaw_dispatch(intent)` — `analysis` analyses an active sequence (ready/active/blocked/done per lane), `execute` fans out parallel work across lanes, `review` dispatches code reviews for completed handoffs
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "brainclaw",
3
- "version": "1.7.1",
3
+ "version": "1.7.3",
4
4
  "description": "Shared project memory for humans and coding agents.",
5
5
  "type": "module",
6
6
  "bin": {