@jhizzard/termdeck-stack 0.1.0 → 0.2.0
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 +47 -0
- package/README.md +29 -0
- package/package.json +2 -1
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,47 @@
|
|
|
1
|
+
# Changelog — `@jhizzard/termdeck-stack`
|
|
2
|
+
|
|
3
|
+
All notable changes to the meta-installer are tracked here. The
|
|
4
|
+
underlying packages (`@jhizzard/termdeck`, `@jhizzard/mnestra`,
|
|
5
|
+
`@jhizzard/rumen`) ship on their own cadences and have their own
|
|
6
|
+
changelogs — see the root `CHANGELOG.md` for `@jhizzard/termdeck`.
|
|
7
|
+
|
|
8
|
+
## [0.2.0] — 2026-04-25
|
|
9
|
+
|
|
10
|
+
### Documentation
|
|
11
|
+
- New **Known limitations** section: Tier 3 (Rumen) still requires a
|
|
12
|
+
manual `termdeck init --rumen` after the meta-installer finishes.
|
|
13
|
+
Auto-running this step is queued as Sprint 31 T2.
|
|
14
|
+
- New **Version vs. the rest of the stack** section: explains that
|
|
15
|
+
this package's version tracks the meta-installer surface, not the
|
|
16
|
+
underlying packages, and that the installer always pulls each
|
|
17
|
+
layer's `latest` dist-tag at install time.
|
|
18
|
+
|
|
19
|
+
### Why this is a minor bump (not patch)
|
|
20
|
+
Codex's 2026-04-25 audit flagged that `0.1.0` looked like the least-
|
|
21
|
+
mature published surface next to `termdeck 0.6.1 / mnestra 0.2.1 /
|
|
22
|
+
rumen 0.4.3`. The README was also silent on (a) why this package's
|
|
23
|
+
version is decoupled from the underlying layers and (b) the manual
|
|
24
|
+
`termdeck init --rumen` step that Tier 3 users still need. The bump
|
|
25
|
+
signals "actively maintained, validated against the v0.6.x stack."
|
|
26
|
+
|
|
27
|
+
The strict reading of `docs/SEMVER-POLICY.md` would treat a docs-only
|
|
28
|
+
refresh as patch-level. We're stretching to minor here on purpose —
|
|
29
|
+
this is the "we know it's been sitting at 0.1.0 too long, here's the
|
|
30
|
+
intentional refresh" release. Future docs-only updates will revert
|
|
31
|
+
to patch.
|
|
32
|
+
|
|
33
|
+
### Notes
|
|
34
|
+
- Installer code in `src/index.js` is byte-for-byte identical to
|
|
35
|
+
v0.1.0. The published 0.1.0 already wires Tiers 1–4 against the
|
|
36
|
+
current stack — no behavior change in this release.
|
|
37
|
+
|
|
38
|
+
## [0.1.0] — 2026-04-25
|
|
39
|
+
|
|
40
|
+
### Initial release
|
|
41
|
+
- One-command meta-installer: `npx @jhizzard/termdeck-stack`.
|
|
42
|
+
- Four-layer overview, detection of already-installed packages,
|
|
43
|
+
tier prompt (default 4), `npm install -g` for missing layers,
|
|
44
|
+
merges Mnestra and Supabase MCP entries into `~/.claude/mcp.json`
|
|
45
|
+
without clobbering existing servers.
|
|
46
|
+
- Modes: interactive (default), `--tier N`, `--dry-run`, `--yes`.
|
|
47
|
+
- Zero runtime deps beyond Node built-ins.
|
package/README.md
CHANGED
|
@@ -33,6 +33,35 @@ npx @jhizzard/termdeck-stack --dry-run # print plan, don't install
|
|
|
33
33
|
npx @jhizzard/termdeck-stack --yes # accept defaults (combine with --tier)
|
|
34
34
|
```
|
|
35
35
|
|
|
36
|
+
## Known limitations
|
|
37
|
+
|
|
38
|
+
Tier 3 (Rumen) currently still requires one manual command after the
|
|
39
|
+
installer finishes:
|
|
40
|
+
|
|
41
|
+
```
|
|
42
|
+
termdeck init --rumen
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
That command deploys the Rumen Supabase Edge Function, applies the
|
|
46
|
+
migration, and installs the `pg_cron` schedule. Auto-running it from
|
|
47
|
+
the meta-installer is queued — until then the wizard prints it as an
|
|
48
|
+
explicit next step.
|
|
49
|
+
|
|
50
|
+
## Version vs. the rest of the stack
|
|
51
|
+
|
|
52
|
+
This package's version tracks the meta-installer surface, not the
|
|
53
|
+
underlying packages. Each layer ships on its own release cadence:
|
|
54
|
+
|
|
55
|
+
| Package | Where to look |
|
|
56
|
+
|---------|---------------|
|
|
57
|
+
| `@jhizzard/termdeck` | https://www.npmjs.com/package/@jhizzard/termdeck |
|
|
58
|
+
| `@jhizzard/mnestra` | https://www.npmjs.com/package/@jhizzard/mnestra |
|
|
59
|
+
| `@jhizzard/rumen` | https://www.npmjs.com/package/@jhizzard/rumen |
|
|
60
|
+
|
|
61
|
+
The installer always pulls each layer's `latest` dist-tag, so a fresh
|
|
62
|
+
`npx @jhizzard/termdeck-stack` run picks up the most recent published
|
|
63
|
+
version of every layer regardless of this package's own version.
|
|
64
|
+
|
|
36
65
|
## Why this exists
|
|
37
66
|
|
|
38
67
|
The TermDeck stack used to be a 15-step install: provision Supabase, run six SQL migrations, mint API keys, paste them into `secrets.env`, edit `config.yaml`, install Mnestra globally, deploy Rumen, install the Supabase MCP, wire `~/.claude/mcp.json`. Most testers bounced before step 5.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@jhizzard/termdeck-stack",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.2.0",
|
|
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"
|
|
@@ -9,6 +9,7 @@
|
|
|
9
9
|
"files": [
|
|
10
10
|
"src/**",
|
|
11
11
|
"README.md",
|
|
12
|
+
"CHANGELOG.md",
|
|
12
13
|
"LICENSE"
|
|
13
14
|
],
|
|
14
15
|
"keywords": [
|