pi-braid 0.43.25 → 0.43.26

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/AGENTS.md CHANGED
@@ -108,6 +108,7 @@ Event handlers receive `(event, ctx: ExtensionContext)`. Tool execute functions
108
108
  - Tools added by extensions are auto-enabled on first session, except where the active-set owner says otherwise: `context-management` applies a curated default profile, so a registered tool is only active if the profile (or the operator's saved `/tools` list) names it
109
109
  - Prompt-builder overrides the system prompt entirely (no native loading)
110
110
  - Decompose large handlers into `handlers/*.ts` sub-modules
111
+ - **New fixtures import `node:test`.** 278 of the 440 test files under `packages/` carry hand-rolled runners, each re-deciding exit codes, failure reporting and whether to await a case; a census of them could not reliably tell a discarded async case from one handled by `.then(fn)`, which is exactly the shape where a failing case is counted green. An existing hand-rolled runner moves to `node:test` only when another change already opens that file, so this is a rule for new work, not a backlog.
111
112
 
112
113
  ## Doc Discipline
113
114
 
package/CHANGELOG.md CHANGED
@@ -96,6 +96,27 @@ 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.26 (2026-11-05: a new fixture imports node:test, and a worktree resolves what the primary resolves)
100
+
101
+ - **A rule where there was only habit.** 278 of the 440 test files under
102
+ `packages/` carry hand-rolled runners, each re-deciding exit codes, failure
103
+ reporting and whether to await a case. A census of them could not reliably tell
104
+ a discarded async case from one handled through `.then(fn)`, which is the shape
105
+ where a failing case is counted green.
106
+ - **New work only.** An existing hand-rolled runner moves to `node:test` when
107
+ another change already opens that file, so the convention does not turn into a
108
+ 278-file backlog nobody finishes.
109
+ - **A prepared worktree resolves what the primary resolves.**
110
+ `packages/core/scripts/prepare-worktree.mjs` links every `node_modules` the primary carries,
111
+ including the package-local installs under `packages/*/node_modules`, then
112
+ proves each link by asking node to resolve a real dependency from inside the
113
+ package directory. A detached worktree carries source only, so a chain that
114
+ spawns a package-local `tsc` failed with `MODULE_NOT_FOUND` for a reason the
115
+ change was not, and three workers in one day read that as a broken branch.
116
+ The fixture's control checks out the same ref with plain `git worktree add` and
117
+ requires resolution to fail there, so a passing run cannot be the
118
+ environment's doing.
119
+
99
120
  ## Core — 0.43.25 (2026-11-04: the context backstop leaves a countable trace)
100
121
 
101
122
  - **The 0.90W backstop records that it fired.** The site called the drain and
package/build-info.json CHANGED
@@ -1,9 +1,9 @@
1
1
  {
2
2
  "name": "pi-braid",
3
- "version": "0.43.25",
4
- "sha": "7aeba3aae0e1eee74da2330661e89f78161f0b66",
5
- "shaShort": "7aeba3aa",
3
+ "version": "0.43.26",
4
+ "sha": "41a1a6d79780d94ab878547ee2b620c41882e8e1",
5
+ "shaShort": "41a1a6d7",
6
6
  "branch": "detached",
7
7
  "dirty": false,
8
- "packedAt": "2026-11-05T05:46:15.761Z"
8
+ "packedAt": "2026-11-05T17:17:27.329Z"
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 - 105 of the core suite's 340 fixtures already use `node:test` - so the
141
+ file uses - 106 of the core suite's 341 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.25",
3
+ "version": "0.43.26",
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",