pi-braid 0.43.19 → 0.43.21

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,66 @@ record; the tag scheme above applies unchanged.
53
53
 
54
54
  ---
55
55
 
56
+ ## Core — 0.43.21 (2026-11-03: a failed synthesizer falls back to text, not to a worse voice)
57
+
58
+ - **The voice skill stops offering the offline voices as a substitute for a reply.** When the primary
59
+ synthesizer fails, the reply goes out as text with the outage named in one clause, and voice is
60
+ retried on the next turn. The rule is the owner's judgement measured the hard way: a fallback voice
61
+ note was rejected by ear ("не работает так"), while the outage it was covering had already cleared
62
+ on its own. The offline paths stay documented for audio that is not the reply to a message, which is
63
+ what they were always good for.
64
+
65
+ ## Core — 0.43.20 (2026-11-03: the gates learn to see what is being written)
66
+
67
+ - **The doc gates see the file being written.** `trackedMarkdown` enumerates untracked, non-ignored
68
+ files as well as tracked ones, so a new page no longer passes the local chain and then fails on the
69
+ commit, or worse on CI after the push. A fixture proves an ignored file stays out of the scan.
70
+ - **A fixture's own date is data, not provenance.** `check-placement` keeps its ISO-date rule
71
+ everywhere except inside a `test/` tree, where the literal is what the test reads rather than a
72
+ process timestamp nothing reads.
73
+ - **The poller lock's exit hook releases only a lock it still holds.** It unlinked by path, so a
74
+ process exiting after a handover deleted the successor's lock and two seats could each believe they
75
+ owned the channel. `releaseHeldLockAtExit` goes through the ownership-checked release; two tests
76
+ cover the successor case and the ordinary one.
77
+ - **The journal writer continues its sequence across a rotated archive.** Rotation moves a prefix out
78
+ of the live file, and a writer reading only that file restarted the chain at one, which breaks the
79
+ checker's archive boundary. The writer now reads `journal-YYYY.jsonl` for its floor; a fixture
80
+ covers the first entry after a rotation.
81
+
82
+ - **The version also satisfies the release gate.** `release:check` derives an iteration version from
83
+ the manifest and refuses a tree whose derived version sorts at or below the highest tag in the
84
+ namespace, so a commit past `v0.43.19` turns the chain red until the manifest moves. The publish
85
+ workflow runs that chain before it publishes anything, so a sibling release landing between core
86
+ tags has to reopen the core line rather than carry a gate it cannot satisfy.
87
+
88
+ ## Skills — 0.2.4 (2026-11-03: the pack learns to bring a tunnel back)
89
+
90
+ - **A tunnel-recovery skill, generalized past one machine.** `tunnel-control` states the failure before
91
+ the fix: a GUI client's network extension can die while the app stays up, leaving routes through a
92
+ device that no longer carries traffic, so one service times out while everything else resolves. The
93
+ procedure puts reachability ahead of the client's own status, gives a probe ladder per platform, and
94
+ recovers through the client's own control surface, never by killing a process or touching the system
95
+ extension. The arm table is the load-bearing part: a row is usable only with the date its facts were
96
+ derived from an install, and the pack's content scan now refuses a row that claims VALIDATED without
97
+ one, so a capability cannot be promoted by editing prose.
98
+ - **One arm is measured and the rest say so.** The macOS row carries the date its facts were derived;
99
+ Happ, Incy, Windows and Linux ship as `UNVALIDATED` with the reason, and the skill's first rule is
100
+ that an unvalidated arm is probe-only.
101
+
102
+ ## Skills — 0.2.3 (2026-11-03: the pack learns to read a CV)
103
+
104
+ - **A skill for CV work, prose only.** `cv-improvement` carries a metric set with the formula and the failing
105
+ value for each, a failure catalogue keyed to the shape a wrong draft takes, the order to fix them in, and
106
+ the honesty rules that keep a rewrite from inventing a claim. It ships no code and declares no tool family,
107
+ because the judgment is the deliverable. Its phrase list is drawn from wording a user types rather than
108
+ from the subject: the recorded CV prompt that motivated the skill scored zero against the first draft, since
109
+ `cv` is below the matcher's keyword floor and no phrase occurred verbatim, so `my own cv` is a phrase now
110
+ and the near-misses that share its vocabulary still return nothing.
111
+ - **The pack's own docs are derived rather than remembered.** `AGENTS.md` names the trigger cap the reader
112
+ actually enforces, the README table lists every shipped skill with its status, `Unvalidated` among them,
113
+ and the README's heading count is a gated claim that fails when the stated number and the directory census
114
+ disagree.
115
+
56
116
  ## Core — 0.43.19 (2026-11-03: the pack learns how to write a skill)
57
117
 
58
118
  - **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.21",
4
+ "sha": "f13e588cb743121baf9c952b51dbeafd59c67f55",
5
+ "shaShort": "f13e588c",
6
6
  "branch": "detached",
7
7
  "dirty": false,
8
- "packedAt": "2026-11-03T05:41:48.545Z"
8
+ "packedAt": "2026-11-03T17:19:45.993Z"
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.21",
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",
@@ -2,7 +2,7 @@
2
2
  name: voice-replies
3
3
  description: "Reply to Telegram voice messages with synthesized speech: edge-tts (RU/EN/HE voices) → ffmpeg ogg/opus → Bot API sendVoice, matching the incoming message's language. Use when a voice message arrived and the reply should be a voice note in the same language, or when asked to send a Telegram voice reply. Triggers: voice reply, voice message, sendVoice, TTS, text-to-speech, edge-tts, Telegram audio reply. Includes offline fallbacks (piper, macOS say)."
4
4
  trigger: "voice replies, voice message reply, sendVoice, TTS, text-to-speech, edge-tts, piper, Telegram audio reply, responding in voice"
5
- validated: 2026-09-09
5
+ validated: 2026-11-03
6
6
  verdict: UNVALIDATED
7
7
  ---
8
8
 
@@ -17,6 +17,14 @@ Reply in the same modality **and language** as received:
17
17
  voice message in → voice reply in the same language. Text received → text reply.
18
18
  RU voiced in → Dmitry (RU). EN voiced in → Guy (EN). HE voiced in → Avri (HE).
19
19
 
20
+ **A failed primary synthesizer falls back to TEXT, not to a worse voice.** The owner rejects the
21
+ offline voices by ear: piper's output drew "у тебя чё-то с голосом не то, не работает так" the one
22
+ time it was sent, while edge-tts failures are transient: `NoAudioReceived` on six consecutive attempts
23
+ across the in-process and manual paths, then the first attempt succeeded minutes later with no
24
+ intervention. So a synthesizer outage is a delay, not an occasion to trade quality: send the reply as
25
+ text, name the outage in one clause, and retry voice on the next turn. A degraded voice note costs the
26
+ reader more than the delay does.
27
+
20
28
  ## Install
21
29
 
22
30
  Primary: `uvx edge-tts` (ephemeral, zero install) - OR a persistent venv you
@@ -95,7 +103,9 @@ uvx edge-tts --list-voices | grep -i <lang> # voice exists
95
103
 
96
104
  ## Offline Alternatives (lower priority)
97
105
 
98
- edge-tts is the primary zero-key path for RU/EN/HE. Offline fallbacks:
106
+ edge-tts is the primary zero-key path for RU/EN/HE. These fallbacks are for audio you are not sending
107
+ as the reply to a message (drafts, local artifacts, a transcript you want to hear), or for an owner who
108
+ explicitly asks for voice during an outage. They are not the substitute for a reply (see Modality Rule).
99
109
 
100
110
  **piper** (offline, RU only):
101
111
 
@@ -113,8 +123,8 @@ say -v Milena -o out.aiff "<text>" # Milena = ru-female
113
123
  ffmpeg -y -v error -i out.aiff -c:a libopus -b:a 40k -ar 48000 -ac 1 out.ogg
114
124
  ```
115
125
 
116
- In code, `say` is emergency-only (the owner dislikes its quality) and stays
117
- behind an explicit config choice (`source: "say"` or `"edge-tts+say"`).
126
+ In code, `say` is emergency-only and both offline voices stay behind an explicit config choice
127
+ (`source: "say"` or `"edge-tts+say"`); neither is a suitable default for an owner-facing reply.
118
128
 
119
129
  ## Dependency Note
120
130