@antelopejs/dms 0.3.4 → 0.3.6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@antelopejs/dms",
-  "version": "0.3.4",
+  "version": "0.3.6",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/AntelopeJS/dms.git"
@@ -51,7 +51,7 @@
     "zod": "~3.24.2"
   },
   "devDependencies": {
-    "@antelopejs/core": ">=1.7.0 <2",
+    "@antelopejs/core": ">=1.8.0 <2",
     "@antelopejs/tooling-configs": ">=0.0.6 <1.0.0",
     "@types/archiver": "^6.0.4",
     "@types/chai": "^4.3.20",
@@ -100,7 +100,7 @@
     "@antelopejs/interface-redis": ">=0.0.8 <1.0.0"
   },
   "peerDependencies": {
-    "@antelopejs/core": ">=1.7.0 <2"
+    "@antelopejs/core": ">=1.8.0 <2"
   },
   "peerDependenciesMeta": {
     "@antelopejs/core": {

package/skills/dms/REFERENCE.md

@@ -10,7 +10,7 @@ List a section to see its files:
 | Doc | Covers |
 | --- | --- |
 | `docs/01.getting-started/` | Intro, installation, quickstart, tutorial, **architecture**, the built-in dashboard |
-| `docs/02.building/` | Project setup (**the common case**), every config key, pages & components, navigation, actions, backend services (hooks, notifications, realtime, replayable jobs, HTML/email rendering, export jobs), localization, frontend layer & `ajs-dms` CLI, distributable modules, deployment, troubleshooting |
+| `docs/02.building/` | Project setup (**the common case**), every config key, pages & components, navigation, actions, backend services (hooks, notifications, realtime, replayable jobs, HTML/email rendering, export jobs), localization, frontend layer & `ajs dms` CLI, distributable modules, deployment, troubleshooting |
 | `docs/03.auth-and-tenancy/` | Auth flows (JWT, 2FA, invites), decorators & RBAC, multi-tenant data, SaaS mode |
 | `docs/04.components/` | Component catalog: charts/widgets, layout, forms, tables, tree, DataTypes, DataController, file storage |
 | `docs/05.extending-the-dashboard/` | Dashboard chrome, theming, custom DataTypes (frontend side), table-view displays, component events, period filtering |

package/skills/dms/SKILL.md

@@ -20,9 +20,9 @@ For the framework underneath (the core, `ajs` CLI, interfaces as versioned contr
 - **Two coupled packages.** **`@antelopejs/dms`** is the backend: an AntelopeJS module
   providing the page system, component builders, DataTypes, auth, and platform services,
   auto-registering its **base Vue dashboard frontend** (`frontend-vue/`). **`@antelopejs/dms-frontend`**
-  is the frontend loader (the `ajs-dms` CLI): an Inertia SSR app whose single catch-all
+  is the frontend loader (the `ajs dms` CLI): an Inertia SSR app whose single catch-all
   route renders the component tree the backend describes. In dev: two processes, `ajs project dev -w`
-  (legacy alias: `ajs project run`) and `ajs-dms dev` (auto-discovers a backend; `-b <url>` optional) —
+  (legacy alias: `ajs project run`) and `ajs dms dev` (auto-discovers a backend; `-b <url>` optional) —
   see **Running**.
 - **Two ways to build — usually a project.** Most commonly you build a **project**: your own app
   loading the DMS via `antelope.config.ts`, registering *its own* pages and data — **dms-project**.

package/skills/dms-dev/SKILL.md

@@ -26,9 +26,9 @@ script is for local shells, not managed orbs: its processes do not survive orb u
 The DMS has two coupled processes, both started from the DMS backend package directory:
 
 - **Backend**: the AntelopeJS project — `ajs project dev -w` (`ajs project run` is the legacy alias). Listens on `http://localhost:5010`. Ready when the log emits `Server started, listening on http://localhost:5010`.
-- **Frontend**: the `@antelopejs/dms-frontend` loader — `ajs-dms dev`. It auto-discovers the running backend via `.antelope/dev.json`, so `-b <backend-url>` is optional. Listens on `http://localhost:3001`. Ready when the log emits `Local: http://localhost:3001/`.
+- **Frontend**: the `@antelopejs/dms-frontend` loader — `ajs dms dev`. It auto-discovers the running backend via `.antelope/dev.json`, so `-b <backend-url>` is optional. Listens on `http://localhost:3001`. Ready when the log emits `Local: http://localhost:3001/`.
 
-By default the script runs each via the project's `pnpm dev` / `pnpm frontend:dev` scripts — a convention our playground projects adopt that expands to the two commands above. Those script names aren't shipped by the DMS, so if a project starts its servers differently, override the actual commands with the `DMS_BACK_CMD` / `DMS_FRONT_CMD` env vars (the script reads them; readiness detection and process cleanup already cover `ajs`, `ajs-dms`, and the loader's Node entry point directly).
+By default the script runs each via the project's `pnpm dev` / `pnpm frontend:dev` scripts — a convention our playground projects adopt that expands to the two commands above. Those script names aren't shipped by the DMS, so if a project starts its servers differently, override the actual commands with the `DMS_BACK_CMD` / `DMS_FRONT_CMD` env vars (the script reads them; readiness detection and process cleanup already cover `ajs`, `ajs dms`, and the loader's Node entry point directly).
 
 Order matters: start the backend first and wait for ready, **then** start the frontend. The frontend materializes the backend's layers into a `~/.antelopejs/dms-frontend/` workspace at startup; starting it before the backend is up produces stale or empty layer copies.
 
@@ -96,12 +96,12 @@ The script writes the long-running server logs to `/tmp/dms-back.log` and `/tmp/
 - **Frontend's "auth redirect" 302** on `/modules/...` URLs is **normal** — it's the auth-protected admin routes. The frontend layer is loaded correctly even when curl returns 302. Don't restart on this alone; have the user log in.
 - **Don't run `start` or `restart` more than once concurrently** in a single session — the second invocation will hit a port/lock conflict. If multiple background Bash tasks are queued, use the foreground `restart`.
 - **Stale `dms-back-path` memory.** If the saved path no longer exists or the user has switched projects, the script will fail fast with a clear error. Re-prompt the user and overwrite the memory entry.
-- **Stubbornly stale frontend after restarts.** The loader serves layers from physical copies under `~/.antelopejs/dms-frontend/<hash>/`. If a layer edit still doesn't show after a full restart, reset the workspaces with `ajs-dms clean --all` (run in the backend package dir — bare `ajs-dms clean` exits with an error asking for `-b` or `--all`, and `-b <url>` misses autodiscovered workspaces, which are keyed by project path), then `restart`.
-- **`ajs-dms` reports a refused credential (401), or the backend logs "no valid bootstrap credential".** The frontend authenticates to the layer endpoints with the ephemeral secret a dev backend publishes to `<project>/.antelope/dms-dev.json`. A 401 means that file is absent (backend not in dev mode), or stale — it outlives the backend that wrote it, exactly like `dev.json`, so a stopped instance leaves one behind whose pid no longer resolves. `restart` rewrites it. If the frontend runs outside the project tree, give it `DMS_BOOTSTRAP_SECRET` explicitly.
+- **Stubbornly stale frontend after restarts.** The loader serves layers from physical copies under `~/.antelopejs/dms-frontend/<hash>/`. If a layer edit still doesn't show after a full restart, reset the workspaces with `ajs dms clean --all` (run in the backend package dir — bare `ajs dms clean` exits with an error asking for `-b` or `--all`, and `-b <url>` misses autodiscovered workspaces, which are keyed by project path), then `restart`.
+- **`ajs dms` reports a refused credential (401), or the backend logs "no valid bootstrap credential".** The frontend authenticates to the layer endpoints with the ephemeral secret a dev backend publishes to `<project>/.antelope/dms-dev.json`. A 401 means that file is absent (backend not in dev mode), or stale — it outlives the backend that wrote it, exactly like `dev.json`, so a stopped instance leaves one behind whose pid no longer resolves. `restart` rewrites it. If the frontend runs outside the project tree, give it `DMS_BOOTSTRAP_SECRET` explicitly.
 
 ## Don't
 
 - Don't try to hot-reload by editing files and refreshing the browser without `restart`. It will work intermittently and waste debugging cycles on phantom issues.
-- Don't `pkill -9 node` — it kills unrelated processes. The script targets specific patterns (`antelope-runner`, `ajs project run|dev`, `ajs-dms dev`, and paths ending in `dms-frontend/dist/index.js dev`).
+- Don't `pkill -9 node` — it kills unrelated processes. The script targets specific patterns (`antelope-runner`, `ajs project run|dev`, `ajs dms dev`, and paths ending in `dms-frontend/dist/index.js dev`).
 - Don't hardcode a backend path into a session. Always resolve via memory-or-prompt so the skill works across projects.
 - Don't ask the user to start or restart the servers themselves before manual testing. You have the script — run it, wait for ready, then hand off. Asking the user to do it defeats the point of the skill and breaks the testing loop.

package/skills/dms-dev/scripts/dms-dev.sh

@@ -3,7 +3,7 @@
 # Run from the DMS backend package dir (DMS_BACK_DIR). By default it invokes that project's
 # `pnpm dev` / `pnpm frontend:dev` scripts — a convention our playground projects adopt, which
 # expand to `ajs project dev …` (the AntelopeJS backend; `ajs project run` is the legacy
-# alias) and `ajs-dms dev` (the Inertia frontend loader — it auto-discovers the backend, -b optional).
+# alias) and `ajs dms dev` (the Inertia frontend loader — it auto-discovers the backend, -b optional).
 # Those script names aren't shipped by the DMS, so override the actual commands with
 # DMS_BACK_CMD / DMS_FRONT_CMD when a project starts its servers differently.
 # Dev watchers cover many edits, but the deterministic recipe when verifying a change is:
@@ -24,7 +24,7 @@ BACK_ERROR_PATTERN='Failed to load module|Module load failed|Error loading modul
 FRONT_ERROR_PATTERN='Cannot find module|Failed to compile|Vite error|ENOENT.*package\.json|EADDRINUSE'
 WAIT_TIMEOUT="${DMS_DEV_TIMEOUT:-180}"
 
-PROC_PATTERN='antelope-runner|ajs project (run|dev)|(^|[[:space:]/])ajs-dms dev|dms-frontend/dist/index\.js dev'
+PROC_PATTERN='antelope-runner|ajs project (run|dev)|(^|[[:space:]/])(ajs dms|ajs-dms) dev|dms-frontend/dist/index\.js dev'
 
 log() { printf '[dms-dev] %s\n' "$*"; }
 
@@ -48,7 +48,7 @@ stop_servers() {
   log "stopping dev servers…"
   pkill -9 -f "antelope-runner" 2>/dev/null || true
   pkill -9 -f "ajs project (run|dev)" 2>/dev/null || true
-  pkill -9 -f "(^|[[:space:]/])ajs-dms dev" 2>/dev/null || true
+  pkill -9 -f "(^|[[:space:]/])(ajs dms|ajs-dms) dev" 2>/dev/null || true
   pkill -9 -f "dms-frontend/dist/index\.js dev" 2>/dev/null || true
   sleep 2
   if pgrep -af "$PROC_PATTERN" >/dev/null 2>&1; then
@@ -112,7 +112,7 @@ start_frontend() {
   # shellcheck disable=SC2086  # word-splitting of the command is intentional
   ( cd "$DMS_BACK_DIR" && setsid nohup $FRONT_CMD >> "$FRONT_LOG" 2>&1 < /dev/null & )
   wait_for "$FRONT_LOG" "$FRONT_READY_PATTERN" "frontend (http://localhost:3001)" \
-    "$FRONT_ERROR_PATTERN" 'pnpm.*frontend:dev|(^|[[:space:]/])ajs-dms dev|dms-frontend/dist/index\.js dev'
+    "$FRONT_ERROR_PATTERN" 'pnpm.*frontend:dev|(^|[[:space:]/])(ajs dms|ajs-dms) dev|dms-frontend/dist/index\.js dev'
 }
 
 status() {
@@ -141,7 +141,7 @@ Environment:
   DMS_BACK_CMD    Command to start the backend, run in DMS_BACK_DIR (default: "pnpm dev",
                   the playground convention for "ajs project dev -w" / legacy "run -w").
   DMS_FRONT_CMD   Command to start the frontend, run in DMS_BACK_DIR (default:
-                  "pnpm frontend:dev", the playground convention for "ajs-dms dev").
+                  "pnpm frontend:dev", the playground convention for "ajs dms dev").
   DMS_BACK_LOG    (default: /tmp/dms-back.log)
   DMS_FRONT_LOG   (default: /tmp/dms-front.log)
   DMS_DEV_TIMEOUT (default: 180 seconds per server)

package/skills/dms-project/SKILL.md

@@ -29,7 +29,7 @@ An AntelopeJS app whose `antelope.config.ts` loads **`@antelopejs/dms`** (+ the
 infrastructure it needs) and whose own `src/` is the `local` module. It provides no interfaces, so
 its `package.json` has **no `antelopeJs.implements`** (that field marks a distributable module);
 deps are `@antelopejs/dms` + the interface libs, plus `@antelopejs/dms-frontend` (the
-`ajs-dms` CLI) as a dependency — the template keeps it in `dependencies`; a devDependency also works
+`ajs dms` CLI) as a dependency — the template keeps it in `dependencies`; a devDependency also works
 since it is only a CLI. The frontend attaches at runtime with `AddFrontendModule`, and the DMS
 **auto-registers its base dashboard layer** (shell, login, component vocabulary) — a pages-only
 project needs no `frontend-vue/` of its own.
@@ -114,9 +114,9 @@ under the built-in `pagesCategory` (`RegisterModule` is for distributable module
 
 - Backend: `ajs project dev -w` (`ajs project run` is the legacy alias; `-e STAGING` picks an
   environment). Projects often start Mongo/Redis in Docker first (`docker-compose up -d`).
-- Frontend: the `@antelopejs/dms-frontend` loader, `ajs-dms dev` — auto-discovers the running
+- Frontend: the `@antelopejs/dms-frontend` loader, `ajs dms dev` — auto-discovers the running
   backend via `.antelope/dev.json`, so `-b <apiBaseUrl>` is optional.
 
 The `pnpm dev` / `frontend:dev` script names are **your project's conventions** — they expand to
-`ajs project dev` and `ajs-dms dev`. Whenever a change doesn't show (or you're about to verify one),
+`ajs project dev` and `ajs dms dev`. Whenever a change doesn't show (or you're about to verify one),
 full-restart both, backend first — see **dms-dev**. Production: `docs/02.building/11.deployment.md`.