Merge pull request #16 from BootNodeDev/feat/canton-stack

feat: retarget the canton stack and split stack config into modules

Author: gabitoesmiapodo

.github/workflows/pr.yml

@@ -47,16 +47,16 @@ jobs:
       - uses: ./.github/actions/setup
       - run: pnpm test
 
-  test-node-22:
-    name: 3 - test (node 22)
+  test-node-floor:
+    name: 3 - test (node 24.15.0)
     runs-on: ubuntu-latest
     if: ${{ github.event.action != 'edited' || github.event.changes.base != null }}
-    # engines.node says >=22, so the floor gets the same test run as .nvmrc does.
+    # engines.node says >=24.15.0, so the floor gets the same test run as .nvmrc does.
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
       - uses: ./.github/actions/setup
         with:
-          node-version: 22
+          node-version: 24.15.0
       - run: pnpm test
       - run: pnpm build
 

CLAUDE.md

@@ -10,9 +10,9 @@
 
 A CLI installer tool for dAppBooster projects. It supports two **stacks** and two **modes**:
 
-- **Stacks:** `evm` (the original dAppBooster for EVM chains) and `canton` (dAppBooster for Canton: Daml ledger, Carpincho wallet, off-chain services). Each stack declares its own source repository, ref strategy (tag-latest vs branch), package manager, env files, optional `removeAfterClone` paths, and features.
-- **Interactive** (default): React + Ink TUI that prompts for the project name first, then the stack, then the installation mode (Canton offers **default** / full / custom; EVM offers full / custom) → optional packages → install → cleanup → post-install. The stack prompt is skipped when `--canton`, `--evm`, or `--stack` is supplied.
-- **Non-interactive**: Flag-driven (`--ni` or auto-detected when not a TTY) for AI agents and CI. Outputs JSON to stdout. Run `--info` for stack + feature discovery, then `--canton`/`--evm` (or `--stack`) + `--name` + `--mode` [+ `--features`]. Canton supports `--mode default` (the recommended set: keeps `carpincho` + `llm`, removes `github` + `precommit`); `default` is rejected for EVM. Omitting a stack flag in non-interactive mode defaults to `evm` for backward compatibility.
+- **Stacks:** `evm` (the original dAppBooster for EVM chains) and `canton` (dAppBooster for Canton: Daml ledger, off-chain services). Each stack declares its own source repository, an optional `ref` to clone (without it the newest tag wins), package manager, env files, an optional `prepare` step, and features. Only EVM has features; Canton has none, so it takes neither `--mode` nor `--features`, and the wizard asks it nothing but the project name.
+- **Interactive** (default): React + Ink TUI that prompts for the project name first, then the stack, then — for a stack that has features — the installation mode, the optional packages and a review step, then clone → cleanup → install → post-install. The stack prompt is skipped when `--canton`, `--evm`, or `--stack` is supplied.
+- **Non-interactive**: Flag-driven (`--ni` or auto-detected when not a TTY) for AI agents and CI. Outputs JSON to stdout. Run `--info` for stack + feature discovery, then `--canton`/`--evm` (or `--stack`) + `--name`, plus `--mode` [+ `--features`] when the stack's `modes` list is not empty. Omitting a stack flag in non-interactive mode defaults to `evm` for backward compatibility.
 
 ## Stack & Conventions
 
@@ -27,7 +27,7 @@ A CLI installer tool for dAppBooster projects. It supports two **stacks** and tw
 | Dead code | knip | `pnpm knip` fails on unused files, exports, and dependencies |
 | Secret scanning | gitleaks | Pinned in `.gitleaks-version`; the hooks install it into `bin/` |
 | Git hooks | husky + lint-staged + commitlint | Installed by `pnpm i`; see [Git hooks](#git-hooks) |
-| Node | v22+ | `engines.node` is the published floor; `.nvmrc` (24) is what CI and development use |
+| Node | v24.15.0+ | `engines.node` is the published floor, matched to what the scaffolded stacks need; `.nvmrc` (24) is what CI and development use |
 | Naming | camelCase vars/functions, PascalCase components/types | Biome enforces the same two cases for filenames |
 
 ## Code Style
@@ -41,10 +41,11 @@ A CLI installer tool for dAppBooster projects. It supports two **stacks** and tw
 
 ## Working Rules
 
-- Use **pnpm** only for this installer (never npm or yarn). The Canton stack scaffolds an npm project; that's a property of the generated project, not this installer.
+- Use **pnpm** only (never npm or yarn), for this installer and for both scaffolded projects
 - Treat `dist/` as build output — never edit directly
 - User input (`projectName`) must never be interpolated into shell command strings — use `execFile` (args array) instead
-- `source/constants/config.ts` is the single source of truth for stack and feature metadata — all programmatic consumers read it through `getStackConfig(stack)`. CLI `--help` text maintains its own copy.
+- `source/stacks/` is the single source of truth for stack and feature metadata: one module per stack, with `source/stacks/index.ts` holding the record and the accessors. All programmatic consumers read it through `getStackConfig(stack)`. CLI `--help` text maintains its own copy.
+- No file outside `source/stacks/` and `source/cli.tsx` may test a stack by name. Add a `StackConfig` field instead.
 - Stack overrides come from env vars `DAPPBOOSTER_<STACK>_REPO_URL` and `DAPPBOOSTER_<STACK>_REF` (read inside `getStackConfig`) — useful for forks and pre-release testing.
 - Components are presentation-only — business logic lives in `source/operations/`. Every operation that varies per stack takes `stack` as its first argument.
 
@@ -64,6 +65,52 @@ Key directories:
 - `source/components/` — reusable UI components (Ask, Divider, MainTitle, Multiselect)
 - `source/__tests__/` — vitest test suite
 
+## Commands
+
+| Command | Purpose |
+|---------|---------|
+| `pnpm build` | Compile `source/` to `dist/` |
+| `pnpm dev` | The same, in watch mode |
+| `pnpm typecheck` | Types only, no output. Two passes: `source/` for the build, then the tests |
+| `pnpm test` | Run the vitest suite |
+| `pnpm test:coverage` | The same, with a coverage report |
+| `pnpm lint` | Biome check, warnings included |
+| `pnpm lint:fix` | Biome check with `--write` |
+| `pnpm knip` | Report unused files, exports, and dependencies |
+
+Run the built CLI from a scratch directory. It scaffolds the new project into the folder it is
+started from, so `node dist/cli.js` in this repo would write into the repo itself.
+
+## Demo recording
+
+`demo.svg` in the readme is an animated SVG of a real wizard run. Regenerate it after any change to
+the terminal UI:
+
+```shell
+pnpm build
+./scripts/record-demo.py
+```
+
+The script scaffolds a real EVM project into a temporary directory, so it needs network and takes a
+few minutes. It cleans up after itself and overwrites `demo.svg`.
+
+Things worth knowing before touching it:
+
+- The conversion is [svg-term-cli](https://github.com/marionebl/svg-term-cli), run through
+  `pnpm dlx`. It is not a dependency. The flags `--window --width 92 --height 23 --padding 10`
+  produce the committed geometry; change them and the readme's `<img>` size needs to change too.
+- `asciinema` cannot be scripted here. It ignores piped stdin, `script` refuses to start unless its
+  own stdin is a tty, and `node-pty` has no prebuilt binary for this machine. The script uses
+  Python's standard-library `pty` instead, which needs nothing installed.
+- It waits for each prompt to appear in the output rather than sleeping a fixed time, so it does not
+  break when a step gets slower.
+- A `pnpm` shim on `PATH` makes `pnpm dlx dappbooster` run `dist/cli.js`. The recorded command line
+  is the real one while the code being demoed is the working tree.
+- The recording is trimmed to 15 seconds so the loop stays short. Beyond that it is the package
+  install, which is a long stretch of near-static output and reads as a frozen image.
+- Output within 150ms is merged into one frame. That cuts the file roughly five-fold, because the
+  spinner redraws every 80ms. It changes when bytes are flushed, never which bytes.
+
 ## Testing
 
 - **Framework:** Vitest + V8 coverage
@@ -97,7 +144,7 @@ the history by hand:
 ## Continuous integration
 
 `.github/workflows/pr.yml` runs on every pull request: Biome, then typecheck and build and knip,
-then the test suite on `.nvmrc` and again on the Node 22 floor, then commitlint over both the commit
+then the test suite on `.nvmrc` and again on the Node 24.15.0 floor, then commitlint over both the commit
 range and the PR title, then gitleaks over the full history. A retitle only re-runs commitlint.
 
 `pr-assign.yml` assigns the author to their own pull request. `add-to-project.yml` adds new issues