pi-braid 0.43.0 → 0.43.2
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 +38 -0
- package/build-info.json +4 -4
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -43,6 +43,44 @@ reader-facing record; the tag scheme above applies unchanged.
|
|
|
43
43
|
|
|
44
44
|
---
|
|
45
45
|
|
|
46
|
+
## Core — 0.43.2 (2026-10-28: the artifact check waits out the publish it is checking)
|
|
47
|
+
|
|
48
|
+
- **A 404 seconds after our own publish is a lag, not absence.** npm acknowledged the `0.43.1` publish, a read forty
|
|
49
|
+
seconds later answered 404, and the version became servable four minutes forty-six seconds after the
|
|
50
|
+
acknowledgement. The packument is served with `cache-control: max-age=300`, so that window is a cache refresh rather
|
|
51
|
+
than a broken publish. The comparison step read the 404 as "not on the registry, nothing to compare", exited 0, and
|
|
52
|
+
the job went green without comparing anything. The read is now retried inside a bounded grace window (360 seconds
|
|
53
|
+
over 15-second intervals: 25 reads, 24 sleeps of the window, both parameters env-overridable). The bound is a count
|
|
54
|
+
of reads, not a deadline, so a slow read cannot hide an attempt.
|
|
55
|
+
- **A green run can no longer be read as a verified one.** Every branch that cannot obtain the artifact emits
|
|
56
|
+
`::warning title=Registry artifact not verified::` naming the fact and the reads spent, and appends one line to the
|
|
57
|
+
run summary that distinguishes verified equal, differs, and not verified. A failure that is not a 404 is reported at
|
|
58
|
+
once: waiting does not change what it says about the registry, and the window covers propagation only.
|
|
59
|
+
- **The artifact's own verdict is now on the run page.** A run whose step skipped its comparison carries a warning and a
|
|
60
|
+
summary line that say so, which is the difference between "the release was checked" and "the step ran".
|
|
61
|
+
- **The package description names the suite the way the repository names it.** One character, no behaviour.
|
|
62
|
+
|
|
63
|
+
## Core — 0.43.1 (2026-10-28: the artifact check says what it ignored instead of failing silently)
|
|
64
|
+
|
|
65
|
+
- **A step that cannot fail the job can no longer fail it silently.** The runner invokes the artifact-check body as
|
|
66
|
+
`bash -e`, and the body read the comparison's exit status on the line after the comparison. A difference returned 1,
|
|
67
|
+
`-e` ended the step there, and the `::warning::` the step exists to print was never reached: the `0.43.0` run went
|
|
68
|
+
red with no output at all. The body now opts out of the runner's shell options explicitly and captures every status
|
|
69
|
+
it inspects inside an `if`. A fixture drives the body extracted from `.github/workflows/publish.yml` itself under
|
|
70
|
+
`bash -e`, so a copy of the body cannot pass while the workflow runs something else.
|
|
71
|
+
- **The comparison ignores three environment-derived fields, and names each with its reason.** `branch` says how the
|
|
72
|
+
packer checked the tree out (a tag is detached in CI), `packedAt` is a clock, and `shaShort` is git's abbreviation
|
|
73
|
+
length, which is a property of the clone's object database: 8 characters here, 7 in a fresh checkout of one commit.
|
|
74
|
+
The equality line now prints the fields it replaced and why, so an equality reached by normalising reads differently
|
|
75
|
+
from one reached by comparing everything. A field present on only one side stays a difference, which keeps "delete a
|
|
76
|
+
field to make a pair compare equal" itself a difference. `name`, `version`, `sha` and `dirty` are still substance.
|
|
77
|
+
- **The short sha has a stated length.** The provenance writer asks git for exactly eight characters instead of
|
|
78
|
+
inheriting whatever abbreviation the clone needed. The comparison normalises the field anyway, because artifacts
|
|
79
|
+
packed before this release carry seven.
|
|
80
|
+
- Three other places read bare `git rev-parse --short` for a version suffix, a prerelease tag and a placement stamp.
|
|
81
|
+
None of them is compared against another environment's value, so they are left alone and named here rather than
|
|
82
|
+
changed in passing.
|
|
83
|
+
|
|
46
84
|
## Core — 0.43.0 (2026-10-28: a long session stops killing itself, and the pages stop describing what is not there)
|
|
47
85
|
|
|
48
86
|
One release for everything after `0.42.1`. The versions between were base bumps: they were never tagged, so no reader
|
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.2",
|
|
4
|
+
"sha": "c177e9e1828e376fbabfc1b89fd7129454d95017",
|
|
5
|
+
"shaShort": "c177e9e1",
|
|
6
6
|
"branch": "detached",
|
|
7
7
|
"dirty": false,
|
|
8
|
-
"packedAt": "2026-10-
|
|
8
|
+
"packedAt": "2026-10-28T10:49:28.384Z"
|
|
9
9
|
}
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pi-braid",
|
|
3
|
-
"version": "0.43.
|
|
4
|
-
"description": "Adds memory, plan tracking, and completion checks
|
|
3
|
+
"version": "0.43.2",
|
|
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",
|
|
7
7
|
"types": "./dist/index.d.ts",
|