@jhizzard/termdeck-stack 0.3.0 → 0.3.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.
Files changed (2) hide show
  1. package/CHANGELOG.md +77 -0
  2. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -5,6 +5,83 @@ underlying packages (`@jhizzard/termdeck`, `@jhizzard/mnestra`,
5
5
  `@jhizzard/rumen`) ship on their own cadences and have their own
6
6
  changelogs — see the root `CHANGELOG.md` for `@jhizzard/termdeck`.
7
7
 
8
+ ## [0.3.2] — 2026-04-26
9
+
10
+ ### Documentation
11
+ - Audit-trail update: validated against `@jhizzard/termdeck@0.7.2`,
12
+ the patch release that closes the second of two converging bugs
13
+ diagnosed in Sprint 33's *"Flashbacks are vaporware"* investigation.
14
+ v0.7.1 fixed the analyzer regex; v0.7.2 repairs the mis-tagged
15
+ corpus and pins TermDeck-side resolver behavior against future
16
+ drift. Sprint 34's 4+1 audit (~15 minutes wall-clock) reset the
17
+ framing: **the chopin-nashville source is not in TermDeck.** The
18
+ resolver in `packages/server/src/rag.js` is correct (longest-prefix
19
+ wins with explicit `path.sep` boundary; verified against the live
20
+ 15-project `~/.termdeck/config.yaml`); every TermDeck-side writer
21
+ routes through `_projectFor`; Sprint 21 T2's fix landed and is
22
+ intact. The 1,165 mis-tagged `memory_items` rows came from
23
+ `~/.claude/hooks/memory-session-end.js:17` — Josh's user-owned
24
+ global Claude Code harness hook, outside any package — which
25
+ pattern-matches `/ChopinNashville|ChopinInBohemia/i` first-match-wins
26
+ on cwd with no `termdeck` entry above it. Rumen `extract.ts:62`
27
+ (`(ARRAY_AGG(m.project))[1]`) then propagates the bad tag every
28
+ 15 minutes via synthesis writeback.
29
+ - **What ships in v0.7.2 (within-repo).** TermDeck-side writer-side
30
+ observability: `[rag] write project=<tag> source=<...>` and
31
+ `[mnestra-bridge] query project=<tag> source=<...> mode=<...>`
32
+ log lines on every event/query (~30 LOC across `rag.js` and
33
+ `mnestra-bridge/index.js`). NEW `tests/project-tag-resolution.test.js`
34
+ with 12 cases pinning the resolver contract — leaf wins over
35
+ ancestor, explicit `meta.project` beats cwd, `path.sep` boundary
36
+ guards against false-prefix matches, the regression pin
37
+ (`.../ChopinNashville/SideHustles/TermDeck/termdeck` resolves to
38
+ `termdeck`). One-time corpus repair shipped as
39
+ `scripts/migrate-chopin-nashville-tag.sql` (~210 LOC,
40
+ three-block dry-run / UPDATE / REVERT layout, conservative
41
+ multi-branch heuristic, reversible via a `metadata.rebrand_v0_7_2_from`
42
+ stash). Live-corpus regression catches in
43
+ `tests/project-tag-invariant.test.js` (6 tests) and a project-bound
44
+ extension to `tests/flashback-e2e.test.js` (now 3 tests).
45
+ - **What v0.7.2 deliberately does NOT fix.** The harness hook
46
+ is Josh-owned and out of any package; v0.7.2 documents the
47
+ one-paste fix in the root `CHANGELOG.md` and POSTMORTEM. A
48
+ prospective `@jhizzard/rumen@0.4.4` would harden the
49
+ `(ARRAY_AGG)[1]` synthesis tag inheritance, but fixing the
50
+ hook first heals Rumen on next tick.
51
+
52
+ ### Notes
53
+ - No installer behavior change. `npx @jhizzard/termdeck-stack` always
54
+ pulls `@jhizzard/termdeck@latest`. Mnestra (0.2.2) and Rumen (0.4.3)
55
+ unchanged through this bump.
56
+ - Live-store backfill execution: deferred to orchestrator + Josh
57
+ decision after Block 1 sample inspection. Script ships in the
58
+ TermDeck package; runs via
59
+ `psql "$DATABASE_URL" -f scripts/migrate-chopin-nashville-tag.sql`.
60
+
61
+ ## [0.3.1] — 2026-04-26
62
+
63
+ ### Documentation
64
+ - Audit-trail update: validated against `@jhizzard/termdeck@0.7.1`,
65
+ the patch release that closes one of two converging bugs that made
66
+ Flashback go silent for the most common Unix shell errors. Sprint 33
67
+ (4+1 forensic orchestration, ~24 minutes wall-clock) traced the
68
+ silence to a regex coverage gap in `PATTERNS.error` — the session.js
69
+ comment claimed Unix tool errors were covered, the code never
70
+ enforced it. Pure "documentation is not verification" miss. v0.7.1
71
+ ships the analyzer regex fix + 17 regression fixtures + e2e
72
+ instrumentation. The second root cause (a `chopin-nashville`
73
+ project-tag regression hiding TermDeck memories from the bridge's
74
+ project filter) is diagnosed in `docs/sprint-33-flashback-debug/POSTMORTEM.md`
75
+ and ships in v0.7.2 (Sprint 34) because it requires UPDATE
76
+ statements against the live Supabase store + writer-side source
77
+ review. See the root `CHANGELOG.md` v0.7.1 entry for the full
78
+ diagnosis.
79
+
80
+ ### Notes
81
+ - No installer behavior change. `npx @jhizzard/termdeck-stack` always
82
+ pulls `@jhizzard/termdeck@latest`. Mnestra (0.2.2) and Rumen (0.4.3)
83
+ unchanged through this bump.
84
+
8
85
  ## [0.3.0] — 2026-04-26
9
86
 
10
87
  ### Documentation
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jhizzard/termdeck-stack",
3
- "version": "0.3.0",
3
+ "version": "0.3.2",
4
4
  "description": "One-command installer for the TermDeck developer memory stack: TermDeck + Mnestra + Rumen + Supabase MCP",
5
5
  "bin": {
6
6
  "termdeck-stack": "./src/index.js"