Merge pull request #7 from BootNodeDev/release/v3.3.1

Release v3.3.1 — Canton docs: lead with dev-stack.sh, fix landing URL

Author: fernandomg

docs/architecture/data-flow.md

@@ -83,4 +83,4 @@ Operations (disk):    CloneRepo → Install → FileCleanup → PostInstall
 
 Once operations begin, `CloneRepo` calls `beginInstall` (see [abstractions → installGuard](./abstractions.md#interrupt-safety-installguard)) and `FileCleanup` calls `completeInstall` on success, so a Ctrl+C mid-scaffold removes the partial directory while a finished project is left intact.
 
-Components are presentation-only — they call operations via `useEffect` and render status. Components receive `MultiSelectItem[]` for feature selection (TUI concern), then derive the kept-feature `FeatureName[]` via `resolveModeFeatures(stack, mode, selected)` before calling operations — so `full`/`default` resolve correctly even though the multiselect is skipped. The `OptionalPackages` multiselect pre-checks `default: true` features and enforces feature dependencies live via `applyFeatureToggle`. `PostInstall` renders stack-specific instructions; the EVM branch shows the subgraph warning when applicable, the Canton branch always shows the `canton:up`/`app:dev` commands and — when the `carpincho` feature is in the resolved set — the Carpincho extension build/load instructions.
+Components are presentation-only — they call operations via `useEffect` and render status. Components receive `MultiSelectItem[]` for feature selection (TUI concern), then derive the kept-feature `FeatureName[]` via `resolveModeFeatures(stack, mode, selected)` before calling operations — so `full`/`default` resolve correctly even though the multiselect is skipped. The `OptionalPackages` multiselect pre-checks `default: true` features and enforces feature dependencies live via `applyFeatureToggle`. `PostInstall` renders stack-specific instructions; the EVM branch shows the subgraph warning when applicable, the Canton branch leads with the one-command `./scripts/dev-stack.sh up` bring-up and keeps the manual `canton:up`/`app:dev` commands as a fallback — adding the Carpincho extension build/load instructions (handled by `dev-stack.sh up`, with `carpincho:build:extension` as the manual fallback) when the `carpincho` feature is in the resolved set.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "dappbooster",
-  "version": "3.3.0",
+  "version": "3.3.1",
   "description": "Agent-friendly dAppBooster installer that scaffolds Web3 dApps via TUI or non-interactive CLI/CI.",
   "keywords": [
     "dappbooster",

readme.md

@@ -7,7 +7,7 @@ agents.
 
 - **EVM** — the original [dAppBooster](https://dappbooster.dev/) for Ethereum, Polygon, Base, and
   other EVM chains.
-- **Canton** — [dAppBooster for Canton](https://dappbooster-canton-landing.vercel.app/): Daml
+- **Canton** — [dAppBooster for Canton](https://www.dappbooster.cc/): Daml
   ledger, Carpincho wallet, off-chain services.
 
 ## Choose your stack
@@ -150,10 +150,19 @@ the "Removing a feature" guide in the generated `dapp/frontend/README.md` — th
 deletes demo source itself.
 
 The Canton scaffold uses **npm** (a property of the generated project, not this installer). After
-install: review `canton-barebones/.env`, run `npm run canton:up` to start the local Canton stack,
-and `npm run app:dev` to run the dapp frontend. When `carpincho` is included, build the extension
-with `npm run carpincho:build:extension` and load `carpincho-wallet/dist-extension` as an unpacked
-browser extension.
+install, review `canton-barebones/.env`, then bring the whole local stack up with a single command:
+`./scripts/dev-stack.sh up` (Docker must be running). It starts the Canton + Postgres +
+wallet-service containers, runs the health checks, builds and deploys the quickstart-counter DAR,
+launches the dapp frontend (`:3012`), and — when `carpincho` is included — builds the Carpincho
+extension and copies it to `~/Desktop/dist-extension` (load it via `chrome://extensions`, Developer
+mode → Load unpacked). Run `./scripts/dev-stack.sh` with no arguments for an interactive arrow-key
+menu; `mock-up` brings up a Docker-free mocked wallet-service + Carpincho web app, and `down` tears
+everything back down.
+
+Prefer to run the pieces by hand? The underlying npm scripts still work: `npm run canton:up` to
+start the local Canton stack and `npm run app:dev` for the dapp frontend, and when `carpincho` is
+included build the extension with `npm run carpincho:build:extension` and load
+`carpincho-wallet/dist-extension` as an unpacked browser extension.
 
 **What gets stripped:**
 
@@ -176,10 +185,10 @@ browser extension.
   "path": "/absolute/path/to/my_canton_dapp",
   "postInstall": [
     "Review canton-barebones/.env (created from the example)",
-    "Run npm run canton:up to start the local Canton stack",
-    "Run npm run app:dev to start the dapp frontend",
-    "Build the Carpincho extension with npm run carpincho:build:extension",
-    "Load carpincho-wallet/dist-extension as an unpacked browser extension"
+    "Run ./scripts/dev-stack.sh up to bring up the whole local stack in one command — Docker must be running (run ./scripts/dev-stack.sh with no arguments for an interactive menu)",
+    "Fallback — start each piece manually: npm run canton:up for the Canton stack, then npm run app:dev for the dapp frontend",
+    "./scripts/dev-stack.sh up also builds the Carpincho extension and copies it to ~/Desktop/dist-extension (load it via chrome://extensions, Developer mode -> Load unpacked)",
+    "Fallback — build it manually with npm run carpincho:build:extension, then load carpincho-wallet/dist-extension as an unpacked browser extension"
   ]
 }
 ```

source/__tests__/nonInteractive.test.ts

@@ -295,6 +295,24 @@ describe('nonInteractive — canton execution', () => {
     const postInstall = output.postInstall as string[]
     expect(postInstall.some((msg) => msg.includes('canton:up'))).toBe(true)
   })
+
+  it('canton post-install leads with the dev-stack.sh one-command bring-up before the manual canton:up fallback', async () => {
+    await runNonInteractive({
+      stack: 'canton',
+      name: 'my_app',
+      mode: 'custom',
+      features: 'llm',
+    })
+
+    const output = getLastJsonOutput()
+    const postInstall = output.postInstall as string[]
+    const devStackIndex = postInstall.findIndex((msg) => msg.includes('dev-stack.sh'))
+    const cantonUpIndex = postInstall.findIndex((msg) => msg.includes('canton:up'))
+
+    expect(devStackIndex).toBeGreaterThanOrEqual(0)
+    expect(cantonUpIndex).toBeGreaterThanOrEqual(0)
+    expect(devStackIndex).toBeLessThan(cantonUpIndex)
+  })
 })
 
 describe('nonInteractive — default mode', () => {

source/components/steps/PostInstall.tsx

@@ -106,11 +106,10 @@ const CantonPostInstallMessage: FC<{
           created from the example — review it.
         </Text>
         <Text>
-          3- Start the local Canton stack with <Text color={'gray'}>npm run canton:up</Text>
-        </Text>
-        <Text>
-          4- In a separate terminal, run the dapp frontend:{' '}
-          <Text color={'gray'}>npm run app:dev</Text>
+          3- Bring up the whole local stack with one command:{' '}
+          <Text color={'gray'}>./scripts/dev-stack.sh up</Text> (Docker must be running). Run{' '}
+          <Text color={'gray'}>./scripts/dev-stack.sh</Text> with no arguments for an interactive
+          menu.
         </Text>
       </Box>
       {carpinchoEnabled && (
@@ -123,13 +122,29 @@ const CantonPostInstallMessage: FC<{
           padding={1}
         >
           <Text color={'yellow'}>
-            {figures.info} <Text bold>Carpincho Wallet</Text>: build it with{' '}
-            <Text color={'gray'}>npm run carpincho:build:extension</Text> and load{' '}
-            <Text color={'gray'}>carpincho-wallet/dist-extension</Text> as an unpacked browser
-            extension {figures.info}
+            {figures.info} <Text bold>Carpincho Wallet</Text>:{' '}
+            <Text color={'gray'}>./scripts/dev-stack.sh up</Text> also builds the extension and
+            copies it to <Text color={'gray'}>~/Desktop/dist-extension</Text> — load it via{' '}
+            <Text color={'gray'}>chrome://extensions</Text> (Developer mode, Load unpacked){' '}
+            {figures.info}
           </Text>
         </Box>
       )}
+      <Box flexDirection={'column'}>
+        <Text color={'whiteBright'}>Prefer to run the pieces by hand?</Text>
+        <Text>
+          - Start the Canton stack with <Text color={'gray'}>npm run canton:up</Text>, then run the
+          dapp frontend with <Text color={'gray'}>npm run app:dev</Text>.
+        </Text>
+        {carpinchoEnabled && (
+          <Text>
+            - Build the Carpincho extension with{' '}
+            <Text color={'gray'}>npm run carpincho:build:extension</Text> and load{' '}
+            <Text color={'gray'}>carpincho-wallet/dist-extension</Text> as an unpacked browser
+            extension.
+          </Text>
+        )}
+      </Box>
       <Text>See the Canton stack README inside the project for full instructions.</Text>
     </Box>
   )

source/constants/config.ts

@@ -111,8 +111,8 @@ export const stackDefinitions: Record<Stack, StackConfig> = {
     removeAfterClone: [],
     postInstall: [
       'Review canton-barebones/.env (created from the example)',
-      'Run npm run canton:up to start the local Canton stack',
-      'Run npm run app:dev to start the dapp frontend',
+      'Run ./scripts/dev-stack.sh up to bring up the whole local stack in one command — Docker must be running (run ./scripts/dev-stack.sh with no arguments for an interactive menu)',
+      'Fallback — start each piece manually: npm run canton:up for the Canton stack, then npm run app:dev for the dapp frontend',
     ],
     envFiles: [
       { from: 'canton-barebones/.env.example', to: 'canton-barebones/.env' },
@@ -145,8 +145,8 @@ export const stackDefinitions: Record<Stack, StackConfig> = {
         default: true,
         paths: ['carpincho-wallet'],
         postInstall: [
-          'Build the Carpincho extension with npm run carpincho:build:extension',
-          'Load carpincho-wallet/dist-extension as an unpacked browser extension',
+          './scripts/dev-stack.sh up also builds the Carpincho extension and copies it to ~/Desktop/dist-extension (load it via chrome://extensions, Developer mode -> Load unpacked)',
+          'Fallback — build it manually with npm run carpincho:build:extension, then load carpincho-wallet/dist-extension as an unpacked browser extension',
         ],
       },
       llm: {