pi-braid 0.43.26 → 0.43.27

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
@@ -96,6 +96,24 @@ record; the tag scheme above applies unchanged.
96
96
  note that a clean disable releases it, because a refusal an operator cannot act on
97
97
  is a support ticket.
98
98
 
99
+ ## Core — 0.43.27 (2026-11-05: the ship list stays as it was, and a dropped promise is a failed gate)
100
+
101
+ - **A case nobody listens to is not a passing case.** Half the fixtures here
102
+ predate the `node:test` rule and carry a helper that calls `fn()` and moves on;
103
+ handed an `async` case it drops the promise, prints its green line and exits 0
104
+ before the case can fail. `packages/core/scripts/check-async-cases.mjs` scans
105
+ every fixture for that shape and fails on a call site that passes an async
106
+ case, while accepting a helper that chains or awaits. Measured before wiring:
107
+ 442 fixtures, 51 helpers that drop the promise, 0 async cases handed to one, so
108
+ the gate closes a shape rather than a current pile of failures.
109
+
110
+ - **A repository tool is not a package entry point.** 0.43.26's notes name
111
+ `packages/core/scripts/prepare-worktree.mjs`, which lives in the repository. An
112
+ attempt to add it to `files[]` was reverted: the fleet pack gate's rule is that
113
+ the tarball ships no `scripts/` entry from outside `scripts/fleet/**`, and the
114
+ gate failed on the addition with the extra path named. The note needs no
115
+ correction; the package needs no new file.
116
+
99
117
  ## Core — 0.43.26 (2026-11-05: a new fixture imports node:test, and a worktree resolves what the primary resolves)
100
118
 
101
119
  - **A rule where there was only habit.** 278 of the 440 test files under
package/build-info.json CHANGED
@@ -1,9 +1,9 @@
1
1
  {
2
2
  "name": "pi-braid",
3
- "version": "0.43.26",
4
- "sha": "41a1a6d79780d94ab878547ee2b620c41882e8e1",
5
- "shaShort": "41a1a6d7",
3
+ "version": "0.43.27",
4
+ "sha": "ad2a5b832b4b8f03ef2bc7eeffcb090eac793a35",
5
+ "shaShort": "ad2a5b83",
6
6
  "branch": "detached",
7
7
  "dirty": false,
8
- "packedAt": "2026-11-05T17:17:27.329Z"
8
+ "packedAt": "2026-11-05T18:36:49.717Z"
9
9
  }
package/docs/LOCAL_DEV.md CHANGED
@@ -138,7 +138,7 @@ before and after a full run. A non-zero delta is the leak this rule prevents.
138
138
  ### New fixtures: use `node:test`
139
139
 
140
140
  A new fixture is written on `node:test`. The runner does not care which style a
141
- file uses - 106 of the core suite's 341 fixtures already use `node:test` - so the
141
+ file uses - 107 of the core suite's 342 fixtures already use `node:test` - so the
142
142
  reason is the failure the other style produces. A hand-rolled helper that calls
143
143
  `fn()` without awaiting it discards the case's promise, so an `async` case runs
144
144
  detached and the file can print its green tally before that case settles, with
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-braid",
3
- "version": "0.43.26",
3
+ "version": "0.43.27",
4
4
  "description": "🥨 Braid - Metacognitive extension suite for pi coding agent: Adds memory, plan tracking, structured cognitive signals and completion checks on top of pi core loop, so long sessions keep their context and stop claiming unfinished work.",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",