create-qs 0.8.23 → 0.8.24

package/index.js

@@ -1804,7 +1804,7 @@ async function processFiles(options) {
   variables.set("WEB_PACKAGE_NAME", options.webModulePackage);
   variables.set("API_PACKAGE", options.apiPackage);
   variables.set("API_ARTIFACT_ID", options.apiArtifactId);
-  variables.set("QUICKSILVER_VERSION", "0.8.23");
+  variables.set("QUICKSILVER_VERSION", "0.8.24");
   variables.set("MODULE_ID", randomUUID());
   variables.set("DB_PREFIX", toDbPrefix(options.name));
   const menu = renderModuleMenu(options.moduleMenu, options.platformModules);
@@ -1866,7 +1866,7 @@ if (process.argv.some((arg) => arg === "--version" || arg === "-v")) {
   console.log(getCliVersion());
   process.exit(0);
 }
-var program = new Command().name("create-qs").description("Create a new Quicksilver application").version("0.8.23", "-v, --version").argument("[project-name]", "Name of the project").option("-c, --module-code <code>", "Full module code (e.g., power_crm.sales)").option("-d, --module-directory <directory>", "Module directory name (e.g., sales)").option("-n, --module-namespace <code>", "Prefix of unit/table, defaults to the initials of the module code (e.g., pcs)").option("-p, --api-package <package>", "JVM package for Kotlin files (e.g., com.company.crm)").option("-a, --api-artifact-id <artifactId>", "Module artifact ID in repository (e.g., power-crm-module-sales)").option("-w, --web-module-package <package>", "Web module package name (e.g., @powercrm/module-sales-web)").option("-m, --modules <codes>", "Modules to depend on, comma separated (e.g., quicksilver.org)").option("--module-menu <name>", "Create the module's top-level menu in the left nav, with this label").option("--no-module-menu", "Do not create a top-level menu").option("-y, --yes", "Skip prompts and use defaults").action(async (projectName, options) => {
+var program = new Command().name("create-qs").description("Create a new Quicksilver application").version("0.8.24", "-v, --version").argument("[project-name]", "Name of the project").option("-c, --module-code <code>", "Full module code (e.g., power_crm.sales)").option("-d, --module-directory <directory>", "Module directory name (e.g., sales)").option("-n, --module-namespace <code>", "Prefix of unit/table, defaults to the initials of the module code (e.g., pcs)").option("-p, --api-package <package>", "JVM package for Kotlin files (e.g., com.company.crm)").option("-a, --api-artifact-id <artifactId>", "Module artifact ID in repository (e.g., power-crm-module-sales)").option("-w, --web-module-package <package>", "Web module package name (e.g., @powercrm/module-sales-web)").option("-m, --modules <codes>", "Modules to depend on, comma separated (e.g., quicksilver.org)").option("--module-menu <name>", "Create the module's top-level menu in the left nav, with this label").option("--no-module-menu", "Do not create a top-level menu").option("-y, --yes", "Skip prompts and use defaults").action(async (projectName, options) => {
   applyPromptTexts();
   console.log(chalk4.cyan(`
 ${t("banner")}`));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-qs",
-  "version": "0.8.23",
+  "version": "0.8.24",
   "description": "Create a full-stack Quicksilver project with a single command",
   "type": "module",
   "bin": {

package/template/default/AGENTS.md

@@ -105,6 +105,7 @@ Project scripts (see `scripts` in `package.json`; the database dialect scripts l
 ```bash
 pnpm dev                    # Full dev environment (API + web), ports 6286 / 6288
 pnpm dev:h2                 # A second, isolated instance (own database and Atomikos directory)
+pnpm dev:fresh              # A separate instance (ports 6280 / 6281) whose own database is rebuilt from init and demo data at every start
 pnpm build                  # Full build (backend + frontend)
 pnpm test:api               # Backend tests
 pnpm lint                   # ESLint (pnpm lint:fix to autofix)
@@ -175,16 +176,17 @@ you are unsure what a target would actually do.
 **An AI agent starts `pnpm dev:h2`, never `pnpm dev`.**
 
 `pnpm dev` (web 6286 / api 6288) belongs to the person you are working with. It may well be running
-already, and it is backed by the H2 file database `run/api/local/data/h2/database1`, which keeps
+already, and it is backed by the H2 file database `run/api/local/data/h2/dev`, which keeps
 their data between starts: with `auto-init.draft-sync: true`, every start runs the upgrade drafts that
 changed since the last one. Starting or restarting it yourself interrupts them and runs your
 half-finished drafts against their data, so taking it over does not just steal a port.
 
-`pnpm dev:h2` (6210 / 6211) is the isolated instance: its own database (`database2`), its own log
+`pnpm dev:h2` (6210 / 6211) is the isolated instance: its own database (`h2`), its own log
 directory and its own Atomikos directory, so it can run side by side with theirs. The other dialect
 scripts (`dev:postgresql` 6220/6221, `dev:mariadb` 6230/6231, `dev:mssql` 6240/6241, `dev:oracle`
 6250/6251) are equally isolated, but they need a real server: fill in the placeholders in
-`run/api/config/application-<dialect>.yaml` first.
+`run/api/config/application-<dialect>.yaml` first. `pnpm dev:fresh` (6280 / 6281) is isolated in the
+same way, on the H2 database `fresh`, which it drops and rebuilds from init and demo data at every start.
 
 Two more rules:
 
@@ -194,6 +196,9 @@ Two more rules:
   something in 9000–9999; if it is still taken, Vite fails outright — pick another.
 - **Stop the server you started.** Especially after Playwright: leaving it running holds the port
   and the database file.
+- **Rebuild when the database no longer matches the branch.** After switching branches, or when
+  earlier experiments left the database in a state you cannot explain, start once with
+  `pnpm dev:h2 --fresh`. Draft sync never undoes a change that was taken out of a draft.
 
 ## Signing in locally
 
@@ -219,8 +224,8 @@ The profile file is the source of truth for where the data actually lives. Read
 started) and take the datasource from there; note that paths in it are relative to `run/api`, which
 is the working directory of the API process.
 
-For the default H2 profiles that means a file — `run/api/local/data/h2/database1` for `pnpm dev`,
-`database2` for `pnpm dev:h2` — which you can open with any H2 client. For the other dialects,
+For the default H2 profiles that means a file — `run/api/local/data/h2/dev` for `pnpm dev`,
+`h2` for `pnpm dev:h2` — which you can open with any H2 client. For the other dialects,
 connect with your usual client using the host, port, user and password from that same file.
 
 The development database is kept between starts. With `auto-init.draft-sync: true`, every start runs
@@ -233,8 +238,8 @@ existing data, such as filling a new column, goes into the draft only. Changes t
 out of the draft, since demo data runs on fresh installs only. Imperative commands in a draft (`@sql`,
 `$update`, `$delete` ...) run once per `$key`; to run a changed one again, give it a new `$key`.
 `$place` is the exception: it runs again whenever its draft runs. To rebuild the database from the
-data files under `data/init/` and `data/demo/`, set `drop-first: true` in a profile override for one
-start, then set it back.
+data files under `data/init/` and `data/demo/`, add `--fresh` to the start command for one start
+(`pnpm dev:h2 --fresh`). It changes no config file, and the next start without it keeps the data again.
 
 ## Development skills
 

package/template/default/modules/{{MODULE_DIRECTORY}}/api/data/demo/README.md

@@ -5,7 +5,7 @@ This folder holds demo data, rows that exist only to show and test the product,
 - Put the rows in `.jsons` files in this folder or in subfolders of it. Other files, such as this README, are skipped.
 - On a fresh install of the module, the files run after everything in `data/init/`, sorted by name level by level with each subfolder run where it sorts, and they can refer to rows written there.
 - Development and test profiles load demo data, as set by `quicksilver.datasource.auto-init.demo-data` in `run/api/config/application-dev.yaml`. On a production install the installer asks first, and does not load it by default.
-- A module that is already installed never loads demo data. Draft sync does not run these files either, so an existing database does not pick up files added or changed here. To load them, set `drop-first: true` for one start, then set it back to `false`. The rebuild clears the whole development database, including rows entered through the UI.
+- A module that is already installed never loads demo data. Draft sync does not run these files either, so an existing database does not pick up files added or changed here. To load them, start once with `pnpm dev --fresh`, or add `--fresh` to the dialect script you use. The rebuild clears the whole development database, including rows entered through the UI.
 - Do not copy demo rows into `data/upgrade/draft.jsons`. Upgrades never load demo data.
 
 The rules for data files are in section 10 of [`.agents/skills/qs-jsons/references/json-command.md`](../../../../../.agents/skills/qs-jsons/references/json-command.md), and in the developer manual at [`.quicksilver/manual/en-US/06-data.md`](../../../../../.quicksilver/manual/en-US/06-data.md). Both are written by `pnpm install`.

package/template/default/package.json

@@ -10,6 +10,7 @@
   "scripts": {
     "// --- start dev servers -------------------------------------------": "",
     "dev": "quicksilver dev",
+    "dev:fresh": "PORT=6280 API_PORT=6281 SPRING_PROFILES_ACTIVE=dev,fresh quicksilver dev --fresh",
     "dev:h2": "PORT=6210 API_PORT=6211 SPRING_PROFILES_ACTIVE=dev,h2 quicksilver dev",
     "dev:postgresql": "PORT=6220 API_PORT=6221 SPRING_PROFILES_ACTIVE=dev,postgresql quicksilver dev",
     "dev:mariadb": "PORT=6230 API_PORT=6231 SPRING_PROFILES_ACTIVE=dev,mariadb quicksilver dev",

package/template/default/pnpm-workspace.yaml

@@ -25,13 +25,13 @@ catalogs:
   client:
     "@qs-charts/adapter-preact": "0.2.11"
     "@qs-charts/core": "0.2.11"
-    "@qs-elements/web": "1.0.158"
-    "@qs-elements/web-preact": "1.0.158"
+    "@qs-elements/web": "1.0.163"
+    "@qs-elements/web-preact": "1.0.163"
   quicksilver:
-    "@qs-platform/cli": "0.8.23"
-    "@qs-platform/preset-vite-web": "0.8.23"
-    "@qs-platform/web-module-core": "0.8.23"
-    "@qs-platform/web-module-org": "0.8.23"
+    "@qs-platform/cli": "0.8.24"
+    "@qs-platform/preset-vite-web": "0.8.24"
+    "@qs-platform/web-module-core": "0.8.24"
+    "@qs-platform/web-module-org": "0.8.24"
   tooling:
     "@types/node": "^26.4.0"
     "sass": "^1.103.1"

package/template/default/run/api/config/README.md

@@ -33,7 +33,7 @@ database after this project — a project called `power-crm` gets `power_crm_dev
 Quicksilver products can share one database server without colliding. Two files sit outside that
 rule: Oracle, whose "database" is a PDB with a name fixed by the container image (`FREEPDB1`), and
 the H2 profiles, whose databases are plain files under this project's own `local/data/h2/`
-(`database1` for `dev`, `database2` for `dev:h2`) and so have nothing to collide with. The
+(`dev` for `pnpm dev`, `h2` for `pnpm dev:h2`) and so have nothing to collide with. The
 datasource list is replaced as a whole, so when you change one entry, keep the other one listed
 as well.
 
@@ -60,16 +60,16 @@ dialects. Every other dialect listed above ships with its driver.
 
 The `dev` profile turns on `draft-sync` and turns off `drop-first`. Every start runs the upgrade
 drafts that changed since the last start, and keeps the data already in the dev database. To
-rebuild the database from init and demo data, set `drop-first: true` for one start and then set it
-back. Switching `draft-sync` on or off also needs one such rebuild: the two modes record drafts
-differently, and startup refuses a database built in the other mode.
+rebuild the database from init and demo data, start once with `pnpm dev --fresh`, or add `--fresh` to
+a dialect script, as in `pnpm dev:h2 --fresh`. The option turns `drop-first` on for that start only
+and changes no config file. Switching `draft-sync` on or off also needs one such rebuild: the two
+modes record drafts differently, and startup refuses a database built in the other mode.
 
 ## Local edits
 
 `application-dev.yaml` is committed, but **by convention your local edits to it are not** — a
-different database host, `drop-first` turned on for a rebuild, a different
-`fail-on-unregistered-data-source`. Commit it only when you are deliberately changing the team
-default, and say so in the commit message.
+different database host, a different `fail-on-unregistered-data-source`. Commit it only when you
+are deliberately changing the team default, and say so in the commit message.
 
 For an override that never enters version control, point `QUICKSILVER_CONFIG_LOCATION` at a config
 directory of your own: it is appended to the tail of `spring.config.location`, so it wins over

package/template/default/run/api/config/application-dev.yaml

@@ -10,11 +10,11 @@ quicksilver:
     # Keep the quotes around passwords: special characters (# : @ ...) then paste in as is.
     items:
       - code: metadata
-        url: "jdbc:h2:./local/data/h2/database1;DB_CLOSE_ON_EXIT=FALSE;DATABASE_TO_UPPER=false;MODE=MySQL"
+        url: "jdbc:h2:./local/data/h2/dev;DB_CLOSE_ON_EXIT=FALSE;DATABASE_TO_UPPER=false;MODE=MySQL"
         user: sa
         password: "sa"
       - code: business
-        url: "jdbc:h2:./local/data/h2/database1;DB_CLOSE_ON_EXIT=FALSE;DATABASE_TO_UPPER=false;MODE=MySQL"
+        url: "jdbc:h2:./local/data/h2/dev;DB_CLOSE_ON_EXIT=FALSE;DATABASE_TO_UPPER=false;MODE=MySQL"
         user: sa
         password: "sa"
     # Each ac_table row records the datasource its table lives in. When a row names a code that is
@@ -27,15 +27,16 @@ quicksilver:
       # only when quicksilver.application.mode is development. In production the installer does it.
       enabled: true
       # Drop the tables and views that Quicksilver manages before provisioning, so the database is
-      # rebuilt from init and demo data. Set drop-first: true for one start, then set it back to false.
+      # rebuilt from init and demo data. Keep it false here. To rebuild, start once with
+      # `pnpm dev --fresh`, or add --fresh to a dialect script, which turns it on for that start only.
       drop-first: false
       # Draft sync. Every start runs the upgrade drafts that changed since the last start. Data in
       # the dev database is kept, including rows entered through the UI. Switching draft-sync on or
-      # off needs one rebuild with drop-first.
+      # off needs one rebuild with --fresh.
       draft-sync: true
       # Demo data: on a fresh install of a module, the .jsons files in its data/demo/ run after its
       # init. A database that already exists does not pick up demo files added later, rebuild it with
-      # drop-first as described above.
+      # --fresh as described above.
       demo-data: true
   webhook:
     # Webhook targets that resolve to a private or loopback address (10.0.0.0/8, 127.0.0.0/8, ...)

package/template/default/run/api/config/application-fresh.yaml

@@ -0,0 +1,23 @@
+#
+# Overlay for the `fresh` profile used by `pnpm dev:fresh`: only the keys that differ from
+# application-dev.yaml, everything else is inherited key by key. It has a database of its own, which
+# the script drops and rebuilds from init and demo data at every start, so the `pnpm dev` database
+# is never touched.
+#
+logging:
+  file.path: local/log/application/fresh
+
+quicksilver:
+  datasource:
+    # Keep the quotes around passwords: special characters (# : @ ...) then paste in as is.
+    items:
+      - code: metadata
+        url: "jdbc:h2:./local/data/h2/fresh;DB_CLOSE_ON_EXIT=FALSE;DATABASE_TO_UPPER=false;MODE=MySQL"
+        user: sa
+        password: "sa"
+      - code: business
+        url: "jdbc:h2:./local/data/h2/fresh;DB_CLOSE_ON_EXIT=FALSE;DATABASE_TO_UPPER=false;MODE=MySQL"
+        user: sa
+        password: "sa"
+    atomikos:
+      log_base_dir: local/log/atomikos/fresh

package/template/default/run/api/config/application-h2.yaml

@@ -11,11 +11,11 @@ quicksilver:
     # Keep the quotes around passwords: special characters (# : @ ...) then paste in as is.
     items:
       - code: metadata
-        url: "jdbc:h2:./local/data/h2/database2;DB_CLOSE_ON_EXIT=FALSE;DATABASE_TO_UPPER=false;MODE=MySQL"
+        url: "jdbc:h2:./local/data/h2/h2;DB_CLOSE_ON_EXIT=FALSE;DATABASE_TO_UPPER=false;MODE=MySQL"
         user: sa
         password: "sa"
       - code: business
-        url: "jdbc:h2:./local/data/h2/database2;DB_CLOSE_ON_EXIT=FALSE;DATABASE_TO_UPPER=false;MODE=MySQL"
+        url: "jdbc:h2:./local/data/h2/h2;DB_CLOSE_ON_EXIT=FALSE;DATABASE_TO_UPPER=false;MODE=MySQL"
         user: sa
         password: "sa"
     atomikos: