pi-braid 0.43.32 → 0.43.33
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 +16 -0
- package/build-info.json +4 -4
- package/docs/LOCAL_DEV.md +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -96,6 +96,22 @@ 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.33 (2026-11-07: a refusal that names the cell moves the model, not the key)
|
|
100
|
+
|
|
101
|
+
- **The serving cell's capacity is a fact about the model, not about a credential.** Two refusals —
|
|
102
|
+
`prefill_cap_refused`, `the cell is at capacity` — were unclassified; the ring read the status beside
|
|
103
|
+
them and spent a key, then rotated onto a second route that refused the same turn identically, burning
|
|
104
|
+
that quota too. `classifyFailure` now answers `capacity` before the key test, `isKeyRotationError`
|
|
105
|
+
refuses the vocabulary, and the route the turn lands on is chosen by model id through the route
|
|
106
|
+
table's own translation.
|
|
107
|
+
- **A per-model death, and it is short.** When no other route serves the id the walk records a
|
|
108
|
+
`model-capacity` death scoped to that id with its own freshness bound, so the diagnostic names the cell
|
|
109
|
+
and the minutes instead of asking an operator to fix a credential.
|
|
110
|
+
- **The structural harvest ships beside it.** `mechanism-harvest.mjs` reads pi's session JSONL and emits
|
|
111
|
+
repair-shaped windows — a failing tool result, then a mutation naming the same file or token — with a
|
|
112
|
+
census that adds up (7,933 windows over the corpus, 417 of them file-backed). It is repo-only and never
|
|
113
|
+
published. Its known blind edge is pinned by a fixture rather than rounded off.
|
|
114
|
+
|
|
99
115
|
## Core — 0.43.32 (2026-11-06: the identity says what makes a sentence noise)
|
|
100
116
|
|
|
101
117
|
- **Four rules, one of them a test.** The writing block now carries what the reader pays for: a
|
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.33",
|
|
4
|
+
"sha": "a0a4432ed5510a3b89184583838a314103855a5f",
|
|
5
|
+
"shaShort": "a0a4432e",
|
|
6
6
|
"branch": "detached",
|
|
7
7
|
"dirty": false,
|
|
8
|
-
"packedAt": "2026-11-
|
|
8
|
+
"packedAt": "2026-11-07T09:26:18.671Z"
|
|
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 - 111 of the core suite's 345 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.33",
|
|
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",
|