pi-braid 0.43.19 → 0.43.20

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
@@ -53,6 +53,57 @@ record; the tag scheme above applies unchanged.
53
53
 
54
54
  ---
55
55
 
56
+ ## Core — 0.43.20 (2026-11-03: the gates learn to see what is being written)
57
+
58
+ - **The doc gates see the file being written.** `trackedMarkdown` enumerates untracked, non-ignored
59
+ files as well as tracked ones, so a new page no longer passes the local chain and then fails on the
60
+ commit, or worse on CI after the push. A fixture proves an ignored file stays out of the scan.
61
+ - **A fixture's own date is data, not provenance.** `check-placement` keeps its ISO-date rule
62
+ everywhere except inside a `test/` tree, where the literal is what the test reads rather than a
63
+ process timestamp nothing reads.
64
+ - **The poller lock's exit hook releases only a lock it still holds.** It unlinked by path, so a
65
+ process exiting after a handover deleted the successor's lock and two seats could each believe they
66
+ owned the channel. `releaseHeldLockAtExit` goes through the ownership-checked release; two tests
67
+ cover the successor case and the ordinary one.
68
+ - **The journal writer continues its sequence across a rotated archive.** Rotation moves a prefix out
69
+ of the live file, and a writer reading only that file restarted the chain at one, which breaks the
70
+ checker's archive boundary. The writer now reads `journal-YYYY.jsonl` for its floor; a fixture
71
+ covers the first entry after a rotation.
72
+
73
+ - **The version also satisfies the release gate.** `release:check` derives an iteration version from
74
+ the manifest and refuses a tree whose derived version sorts at or below the highest tag in the
75
+ namespace, so a commit past `v0.43.19` turns the chain red until the manifest moves. The publish
76
+ workflow runs that chain before it publishes anything, so a sibling release landing between core
77
+ tags has to reopen the core line rather than carry a gate it cannot satisfy.
78
+
79
+ ## Skills — 0.2.4 (2026-11-03: the pack learns to bring a tunnel back)
80
+
81
+ - **A tunnel-recovery skill, generalized past one machine.** `tunnel-control` states the failure before
82
+ the fix: a GUI client's network extension can die while the app stays up, leaving routes through a
83
+ device that no longer carries traffic, so one service times out while everything else resolves. The
84
+ procedure puts reachability ahead of the client's own status, gives a probe ladder per platform, and
85
+ recovers through the client's own control surface, never by killing a process or touching the system
86
+ extension. The arm table is the load-bearing part: a row is usable only with the date its facts were
87
+ derived from an install, and the pack's content scan now refuses a row that claims VALIDATED without
88
+ one, so a capability cannot be promoted by editing prose.
89
+ - **One arm is measured and the rest say so.** The macOS row carries the date its facts were derived;
90
+ Happ, Incy, Windows and Linux ship as `UNVALIDATED` with the reason, and the skill's first rule is
91
+ that an unvalidated arm is probe-only.
92
+
93
+ ## Skills — 0.2.3 (2026-11-03: the pack learns to read a CV)
94
+
95
+ - **A skill for CV work, prose only.** `cv-improvement` carries a metric set with the formula and the failing
96
+ value for each, a failure catalogue keyed to the shape a wrong draft takes, the order to fix them in, and
97
+ the honesty rules that keep a rewrite from inventing a claim. It ships no code and declares no tool family,
98
+ because the judgment is the deliverable. Its phrase list is drawn from wording a user types rather than
99
+ from the subject: the recorded CV prompt that motivated the skill scored zero against the first draft, since
100
+ `cv` is below the matcher's keyword floor and no phrase occurred verbatim, so `my own cv` is a phrase now
101
+ and the near-misses that share its vocabulary still return nothing.
102
+ - **The pack's own docs are derived rather than remembered.** `AGENTS.md` names the trigger cap the reader
103
+ actually enforces, the README table lists every shipped skill with its status, `Unvalidated` among them,
104
+ and the README's heading count is a gated claim that fails when the stated number and the directory census
105
+ disagree.
106
+
56
107
  ## Core — 0.43.19 (2026-11-03: the pack learns how to write a skill)
57
108
 
58
109
  - **A skill for writing skills, taken from the two best public teachers and finished with this repository's
package/build-info.json CHANGED
@@ -1,9 +1,9 @@
1
1
  {
2
2
  "name": "pi-braid",
3
- "version": "0.43.19",
4
- "sha": "50acf1bbbf5a1eb4faee48aeba2f766190c25f9c",
5
- "shaShort": "50acf1bb",
3
+ "version": "0.43.20",
4
+ "sha": "b798e2c75a33ca00f83818784d8552b4ee35531f",
5
+ "shaShort": "b798e2c7",
6
6
  "branch": "detached",
7
7
  "dirty": false,
8
- "packedAt": "2026-11-03T05:41:48.545Z"
8
+ "packedAt": "2026-11-03T14:31:32.266Z"
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 - 103 of the core suite's 338 fixtures already use `node:test` - so the
141
+ file uses - 105 of the core suite's 340 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.19",
3
+ "version": "0.43.20",
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",