@jhizzard/termdeck-stack 0.2.8 → 0.3.1

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 +64 -0
  2. package/package.json +1 -1
package/CHANGELOG.md CHANGED
@@ -5,6 +5,70 @@ 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.1] — 2026-04-26
9
+
10
+ ### Documentation
11
+ - Audit-trail update: validated against `@jhizzard/termdeck@0.7.1`,
12
+ the patch release that closes one of two converging bugs that made
13
+ Flashback go silent for the most common Unix shell errors. Sprint 33
14
+ (4+1 forensic orchestration, ~24 minutes wall-clock) traced the
15
+ silence to a regex coverage gap in `PATTERNS.error` — the session.js
16
+ comment claimed Unix tool errors were covered, the code never
17
+ enforced it. Pure "documentation is not verification" miss. v0.7.1
18
+ ships the analyzer regex fix + 17 regression fixtures + e2e
19
+ instrumentation. The second root cause (a `chopin-nashville`
20
+ project-tag regression hiding TermDeck memories from the bridge's
21
+ project filter) is diagnosed in `docs/sprint-33-flashback-debug/POSTMORTEM.md`
22
+ and ships in v0.7.2 (Sprint 34) because it requires UPDATE
23
+ statements against the live Supabase store + writer-side source
24
+ review. See the root `CHANGELOG.md` v0.7.1 entry for the full
25
+ diagnosis.
26
+
27
+ ### Notes
28
+ - No installer behavior change. `npx @jhizzard/termdeck-stack` always
29
+ pulls `@jhizzard/termdeck@latest`. Mnestra (0.2.2) and Rumen (0.4.3)
30
+ unchanged through this bump.
31
+
32
+ ## [0.3.0] — 2026-04-26
33
+
34
+ ### Documentation
35
+ - Audit-trail update: validated against `@jhizzard/termdeck@0.7.0`,
36
+ the runtime-correctness companion to the v0.6.9 install-time
37
+ audit/verify framework. v0.7.0 ships three runtime-side fixes:
38
+ (1) theme persistence — `session.meta.theme` becomes a render-time
39
+ getter that resolves against the live config instead of a SQLite
40
+ snapshot, so editing `~/.termdeck/config.yaml` actually changes
41
+ existing terminals' themes; (2) auth cookie persists 30 days
42
+ (HttpOnly, SameSite=Lax, conditional Secure) so users don't re-type
43
+ the token at every browser session; (3) new `GET /api/health/full`
44
+ endpoint that answers "is this install actually healthy right now?"
45
+ by reusing the v0.6.9 preconditions helpers at runtime — Postgres,
46
+ pg_cron, pg_net, Vault, cron.job activity, SQLite, Mnestra webhook,
47
+ Rumen pool. Cached 30s. See the root `CHANGELOG.md` v0.7.0 entry
48
+ for the full check list and test counts.
49
+
50
+ ### Why a minor bump (not patch)
51
+ - v0.7.0 is a minor on the underlying TermDeck package — it adds two
52
+ new feature surfaces (`/api/health/full` and the cookie max-age
53
+ semantics) and changes a load-bearing internal contract (theme
54
+ resolution moves from snapshot to live). The meta-installer's
55
+ audit-trail bump matches that minor cadence so the published
56
+ versions read as a coordinated set: TermDeck 0.7.0 ↔
57
+ termdeck-stack 0.3.0, mirroring the 0.6.x ↔ 0.2.x correspondence.
58
+ - Strict reading of `docs/SEMVER-POLICY.md` would treat a docs-only
59
+ audit-trail bump as patch. We're stretching to minor here on
60
+ purpose, same way 0.2.0 was — to keep the published version
61
+ surface legible alongside the underlying TermDeck minor.
62
+
63
+ ### Notes
64
+ - No installer behavior change. `npx @jhizzard/termdeck-stack`
65
+ always pulls `@jhizzard/termdeck@latest`, so existing installs
66
+ pick up v0.7.0 automatically. Mnestra (0.2.2) and Rumen (0.4.3)
67
+ unchanged through this bump.
68
+ - This closes the v0.6.x → v0.7.0 narrative cleanly: v0.6.x =
69
+ install-time correctness, v0.7.0 = runtime correctness. The same
70
+ audit/verify principle locked into both.
71
+
8
72
  ## [0.2.8] — 2026-04-26
9
73
 
10
74
  ### Documentation
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jhizzard/termdeck-stack",
3
- "version": "0.2.8",
3
+ "version": "0.3.1",
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"