@jhizzard/termdeck-stack 0.3.1 → 0.3.3
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 +58 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,64 @@ 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.3] — 2026-04-27
|
|
9
|
+
|
|
10
|
+
### Documentation
|
|
11
|
+
- Audit-trail update: validated against `@jhizzard/termdeck@0.7.3`, the Sprint 35 reconciliation patch. v0.7.3 closes the personal-vs-product asymmetry that surfaced in Brad's 2026-04-27 overnight crash by (a) flipping `init --mnestra` default to `rag.enabled: false` (MCP-only mode), (b) shipping the legacy RAG schema as bundled migration `008_legacy_rag_tables.sql` so opt-in users no longer hit silent 404 cascades on `mnestra_session_memory` etc., (c) extending `termdeck doctor` with a Supabase schema-check section + `--no-schema` flag, (d) adding a boot banner RAG state line, (e) porting stale-port reclaim and transcript-table-missing hint from `scripts/start.sh` into the published CLI, and (f) closing a packaging gap that left `config/transcript-migration.sql` out of the npm tarball since v0.6.8. No installer-side code changes — this is an audit-trail-only bump aligning the stack-installer's published trail with the underlying `@jhizzard/termdeck` version it validates against.
|
|
12
|
+
|
|
13
|
+
## [0.3.2] — 2026-04-26
|
|
14
|
+
|
|
15
|
+
### Documentation
|
|
16
|
+
- Audit-trail update: validated against `@jhizzard/termdeck@0.7.2`,
|
|
17
|
+
the patch release that closes the second of two converging bugs
|
|
18
|
+
diagnosed in Sprint 33's *"Flashbacks are vaporware"* investigation.
|
|
19
|
+
v0.7.1 fixed the analyzer regex; v0.7.2 repairs the mis-tagged
|
|
20
|
+
corpus and pins TermDeck-side resolver behavior against future
|
|
21
|
+
drift. Sprint 34's 4+1 audit (~15 minutes wall-clock) reset the
|
|
22
|
+
framing: **the chopin-nashville source is not in TermDeck.** The
|
|
23
|
+
resolver in `packages/server/src/rag.js` is correct (longest-prefix
|
|
24
|
+
wins with explicit `path.sep` boundary; verified against the live
|
|
25
|
+
15-project `~/.termdeck/config.yaml`); every TermDeck-side writer
|
|
26
|
+
routes through `_projectFor`; Sprint 21 T2's fix landed and is
|
|
27
|
+
intact. The 1,165 mis-tagged `memory_items` rows came from
|
|
28
|
+
`~/.claude/hooks/memory-session-end.js:17` — Josh's user-owned
|
|
29
|
+
global Claude Code harness hook, outside any package — which
|
|
30
|
+
pattern-matches `/ChopinNashville|ChopinInBohemia/i` first-match-wins
|
|
31
|
+
on cwd with no `termdeck` entry above it. Rumen `extract.ts:62`
|
|
32
|
+
(`(ARRAY_AGG(m.project))[1]`) then propagates the bad tag every
|
|
33
|
+
15 minutes via synthesis writeback.
|
|
34
|
+
- **What ships in v0.7.2 (within-repo).** TermDeck-side writer-side
|
|
35
|
+
observability: `[rag] write project=<tag> source=<...>` and
|
|
36
|
+
`[mnestra-bridge] query project=<tag> source=<...> mode=<...>`
|
|
37
|
+
log lines on every event/query (~30 LOC across `rag.js` and
|
|
38
|
+
`mnestra-bridge/index.js`). NEW `tests/project-tag-resolution.test.js`
|
|
39
|
+
with 12 cases pinning the resolver contract — leaf wins over
|
|
40
|
+
ancestor, explicit `meta.project` beats cwd, `path.sep` boundary
|
|
41
|
+
guards against false-prefix matches, the regression pin
|
|
42
|
+
(`.../ChopinNashville/SideHustles/TermDeck/termdeck` resolves to
|
|
43
|
+
`termdeck`). One-time corpus repair shipped as
|
|
44
|
+
`scripts/migrate-chopin-nashville-tag.sql` (~210 LOC,
|
|
45
|
+
three-block dry-run / UPDATE / REVERT layout, conservative
|
|
46
|
+
multi-branch heuristic, reversible via a `metadata.rebrand_v0_7_2_from`
|
|
47
|
+
stash). Live-corpus regression catches in
|
|
48
|
+
`tests/project-tag-invariant.test.js` (6 tests) and a project-bound
|
|
49
|
+
extension to `tests/flashback-e2e.test.js` (now 3 tests).
|
|
50
|
+
- **What v0.7.2 deliberately does NOT fix.** The harness hook
|
|
51
|
+
is Josh-owned and out of any package; v0.7.2 documents the
|
|
52
|
+
one-paste fix in the root `CHANGELOG.md` and POSTMORTEM. A
|
|
53
|
+
prospective `@jhizzard/rumen@0.4.4` would harden the
|
|
54
|
+
`(ARRAY_AGG)[1]` synthesis tag inheritance, but fixing the
|
|
55
|
+
hook first heals Rumen on next tick.
|
|
56
|
+
|
|
57
|
+
### Notes
|
|
58
|
+
- No installer behavior change. `npx @jhizzard/termdeck-stack` always
|
|
59
|
+
pulls `@jhizzard/termdeck@latest`. Mnestra (0.2.2) and Rumen (0.4.3)
|
|
60
|
+
unchanged through this bump.
|
|
61
|
+
- Live-store backfill execution: deferred to orchestrator + Josh
|
|
62
|
+
decision after Block 1 sample inspection. Script ships in the
|
|
63
|
+
TermDeck package; runs via
|
|
64
|
+
`psql "$DATABASE_URL" -f scripts/migrate-chopin-nashville-tag.sql`.
|
|
65
|
+
|
|
8
66
|
## [0.3.1] — 2026-04-26
|
|
9
67
|
|
|
10
68
|
### Documentation
|
package/package.json
CHANGED