pi-braid 0.43.25 → 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/AGENTS.md +1 -0
- package/CHANGELOG.md +39 -0
- package/build-info.json +4 -4
- package/docs/LOCAL_DEV.md +1 -1
- package/package.json +1 -1
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,45 @@ 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
|
+
|
|
117
|
+
## Core — 0.43.26 (2026-11-05: a new fixture imports node:test, and a worktree resolves what the primary resolves)
|
|
118
|
+
|
|
119
|
+
- **A rule where there was only habit.** 278 of the 440 test files under
|
|
120
|
+
`packages/` carry hand-rolled runners, each re-deciding exit codes, failure
|
|
121
|
+
reporting and whether to await a case. A census of them could not reliably tell
|
|
122
|
+
a discarded async case from one handled through `.then(fn)`, which is the shape
|
|
123
|
+
where a failing case is counted green.
|
|
124
|
+
- **New work only.** An existing hand-rolled runner moves to `node:test` when
|
|
125
|
+
another change already opens that file, so the convention does not turn into a
|
|
126
|
+
278-file backlog nobody finishes.
|
|
127
|
+
- **A prepared worktree resolves what the primary resolves.**
|
|
128
|
+
`packages/core/scripts/prepare-worktree.mjs` links every `node_modules` the primary carries,
|
|
129
|
+
including the package-local installs under `packages/*/node_modules`, then
|
|
130
|
+
proves each link by asking node to resolve a real dependency from inside the
|
|
131
|
+
package directory. A detached worktree carries source only, so a chain that
|
|
132
|
+
spawns a package-local `tsc` failed with `MODULE_NOT_FOUND` for a reason the
|
|
133
|
+
change was not, and three workers in one day read that as a broken branch.
|
|
134
|
+
The fixture's control checks out the same ref with plain `git worktree add` and
|
|
135
|
+
requires resolution to fail there, so a passing run cannot be the
|
|
136
|
+
environment's doing.
|
|
137
|
+
|
|
99
138
|
## Core — 0.43.25 (2026-11-04: the context backstop leaves a countable trace)
|
|
100
139
|
|
|
101
140
|
- **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.
|
|
4
|
-
"sha": "
|
|
5
|
-
"shaShort": "
|
|
3
|
+
"version": "0.43.27",
|
|
4
|
+
"sha": "ad2a5b832b4b8f03ef2bc7eeffcb090eac793a35",
|
|
5
|
+
"shaShort": "ad2a5b83",
|
|
6
6
|
"branch": "detached",
|
|
7
7
|
"dirty": false,
|
|
8
|
-
"packedAt": "2026-11-
|
|
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 -
|
|
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.
|
|
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",
|