pi-braid 0.43.50 → 0.43.52
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,36 @@ Adding a thirteenth extension moves the counts six source claims pin to the mani
|
|
|
96
96
|
schema's recorded line for the `braid.contrib.*` reader; `check:doc-drift` and `check:schema` demanded
|
|
97
97
|
both repairs in the same commit.
|
|
98
98
|
|
|
99
|
+
## Release — three fixes that never left the monorepo (2026-11-12)
|
|
100
|
+
|
|
101
|
+
The publisher skips a workspace whose version is already on the registry, and three fixes landed in
|
|
102
|
+
workspaces whose versions did not move. Green CI, a published core tarball, and nothing shipping is the
|
|
103
|
+
result: the transport class in the provider's failure classifier, the poller heartbeat's non-fatal write,
|
|
104
|
+
and the contrib git tool were all on `main` and in no tarball anyone installs.
|
|
105
|
+
|
|
106
|
+
Steady versions do not mean steady content. The guard is now visible as a defect of the release process
|
|
107
|
+
rather than of any one change: before this entry, `pi-braid-providers` 1.0.6, `pi-braid-telegram` 0.1.9
|
|
108
|
+
and `pi-braid-contrib` 0.1.4 were each their published version and each carried a change the published
|
|
109
|
+
tarball did not have. All three move here, with the fixes they already hold:
|
|
110
|
+
|
|
111
|
+
- `pi-braid-providers` 1.0.7: a port is not an HTTP status, and a connect timeout or a reset classifies
|
|
112
|
+
as transport instead of a shape refusal, so the route walk stops rotating away from a provider that
|
|
113
|
+
refused nothing.
|
|
114
|
+
- `pi-braid-telegram` 0.1.10: a poller-lock write that cannot land is reported on the heartbeat handle
|
|
115
|
+
instead of throwing out of a timer and ending the process.
|
|
116
|
+
- `pi-braid-contrib` 0.1.5: the git tool, argv-only and read-only by default.
|
|
117
|
+
|
|
118
|
+
## Core — a prefix is ranked, never qualifying on its own (2026-11-11)
|
|
119
|
+
|
|
120
|
+
The same defect as the class noun, one leg over: `improve` starts `improvement`, so the token-prefix leg
|
|
121
|
+
of the matcher counted a plain English word as a qualifying name hit. Measured on the shipped scorer, a
|
|
122
|
+
design complaint ("please improve the landing page, it looks generic and flat") selected
|
|
123
|
+
`cv-improvement` with score 2 and reason `name`, while `visual-creator` scored zero. A prefix hit now
|
|
124
|
+
adds its points and is ranked, and it no longer sets the qualifying flag: a word that only starts a name
|
|
125
|
+
token cannot carry a match by itself, and the corpus-frequency gate still refuses a common prefix. The
|
|
126
|
+
design complaint scores zero against the same skill, the labelled set holds at recall@2 13/24 with the
|
|
127
|
+
same 2/7 slot spend, and a rare prefix beside a real token still contributes its two points.
|
|
128
|
+
|
|
99
129
|
## Core — a skill's class noun stopped qualifying it on its own (2026-11-11)
|
|
100
130
|
|
|
101
131
|
A question about search quality was answered with `cv-improvement`: the word `improvements` stems to 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.52",
|
|
4
|
+
"sha": "3a3de965131cd125b58a807b064a43d37b7f466f",
|
|
5
|
+
"shaShort": "3a3de965",
|
|
6
6
|
"branch": "detached",
|
|
7
7
|
"dirty": false,
|
|
8
|
-
"packedAt": "2026-11-
|
|
8
|
+
"packedAt": "2026-11-11T22:45:10.259Z"
|
|
9
9
|
}
|
|
@@ -521,15 +521,17 @@ export function matchSkill(skill, keywords, promptText, keywordDf) {
|
|
|
521
521
|
}
|
|
522
522
|
continue;
|
|
523
523
|
}
|
|
524
|
-
// Token-prefix match in name ("engine" starting "engineer"
|
|
525
|
-
//
|
|
524
|
+
// Token-prefix match in name ("engine" starting "engineer", "improve"
|
|
525
|
+
// starting "improvement"): ranked evidence, never a qualifying signal on its
|
|
526
|
+
// own. A prefix is a shorter word that happens to start a longer one, and
|
|
527
|
+
// the ordinary word is usually the prefix ("improve" for "improvement"), so
|
|
528
|
+
// a prefix alone is exactly the one-shared-word case the bar exists to
|
|
529
|
+
// refuse. The rarity gate stays: a corpus-common prefix earns nothing.
|
|
526
530
|
if (occurrence?.form === "prefix" && df < COMMON_KEYWORD_DF) {
|
|
527
531
|
score += 2;
|
|
528
532
|
signals++;
|
|
529
533
|
evidenceDf += df;
|
|
530
534
|
noteReason("name");
|
|
531
|
-
nameHit = true;
|
|
532
|
-
qualifying++;
|
|
533
535
|
continue;
|
|
534
536
|
}
|
|
535
537
|
// Corpus-common keyword: the weak legs score nothing for it, so a prompt
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pi-braid",
|
|
3
|
-
"version": "0.43.
|
|
3
|
+
"version": "0.43.52",
|
|
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",
|
|
@@ -694,15 +694,17 @@ export function matchSkill(
|
|
|
694
694
|
}
|
|
695
695
|
continue;
|
|
696
696
|
}
|
|
697
|
-
// Token-prefix match in name ("engine" starting "engineer"
|
|
698
|
-
//
|
|
697
|
+
// Token-prefix match in name ("engine" starting "engineer", "improve"
|
|
698
|
+
// starting "improvement"): ranked evidence, never a qualifying signal on its
|
|
699
|
+
// own. A prefix is a shorter word that happens to start a longer one, and
|
|
700
|
+
// the ordinary word is usually the prefix ("improve" for "improvement"), so
|
|
701
|
+
// a prefix alone is exactly the one-shared-word case the bar exists to
|
|
702
|
+
// refuse. The rarity gate stays: a corpus-common prefix earns nothing.
|
|
699
703
|
if (occurrence?.form === "prefix" && df < COMMON_KEYWORD_DF) {
|
|
700
704
|
score += 2;
|
|
701
705
|
signals++;
|
|
702
706
|
evidenceDf += df;
|
|
703
707
|
noteReason("name");
|
|
704
|
-
nameHit = true;
|
|
705
|
-
qualifying++;
|
|
706
708
|
continue;
|
|
707
709
|
}
|
|
708
710
|
// Corpus-common keyword: the weak legs score nothing for it, so a prompt
|