@antelopejs/dms 0.9.7 → 0.10.0

package/frontend-vue/layers/dms-ui/i18n/locales/ui-en-GB.json

@@ -85,7 +85,8 @@
         "include": "Includes",
         "exclude": "Excludes",
         "contains": "Contains",
-        "not_contains": "Does not contain"
+        "not_contains": "Does not contain",
+        "array_contains_string": "Contains"
       },
       "filter": {
         "boolean": {
@@ -108,7 +109,7 @@
       "show_archived": "Show archived items",
       "archived": "Archived",
       "archive_toggle": "Archive",
-      "archived_count": "{count} archived",
+      "archived_count": "Archived: {count}",
       "archive_strip_title": "Viewing archived items.",
       "archive_strip_description": "They are hidden from the regular list until restored.",
       "archived_empty_title": "No archived items",
@@ -177,6 +178,8 @@
         "save_as": "Save as new view",
         "save_current": "Save current view",
         "delete": "Delete view",
+        "delete_title": "Delete this view?",
+        "delete_description": "\"{view}\" will be deleted for good. The table goes back to its default state if the view is open.",
         "save_as_title": "Save as a new view",
         "save_as_description": "Keep the current filters, search, sort, columns and display under a name. Only you will see it.",
         "save_as_confirm": "Save view",
@@ -257,6 +260,7 @@
       "reset": "Reset",
       "cancel": "Cancel",
       "save_changes": "Save changes",
+      "create": "Create",
       "refresh_data": "Refresh data",
       "export_data": "Export data"
     },
@@ -406,7 +410,8 @@
         "invalid": "No errors | 1 field to fix | {count} fields to fix"
       },
       "error_summary": {
-        "title": "No field to fix | 1 field needs your attention | {count} fields need your attention"
+        "title": "No field to fix | 1 field needs your attention | {count} fields need your attention",
+        "resolved": "Everything is fixed: the form can be saved."
       },
       "repeater": {
         "add": "Add a row",
@@ -515,7 +520,7 @@
       },
       "livetoggle": {
         "l": {
-          "description": "Switch the page between Direct and Pause"
+          "description": "Switch the page between Live and Pause"
         }
       }
     },
@@ -687,6 +692,9 @@
         "info": "note"
       }
     },
+    "flow_canvas": {
+      "delete_node": "Delete node"
+    },
     "password_rules": {
       "head": "{met} of {total} met",
       "verdict": {
@@ -750,6 +758,7 @@
       "show_new": "Show",
       "paused": "Paused",
       "resume": "Resume",
+      "refresh": "Refresh",
       "reason_hidden": "tab hidden",
       "polling": "no realtime, polling",
       "table_held": "Table on hold",
@@ -771,6 +780,9 @@
       "invalid_state": "The preview state could not be read.",
       "empty": "Nothing to preview yet.",
       "unsafe_method": "{name} was not drawn: a preview only reads its data, and {value} writes."
+    },
+    "drawer": {
+      "resize": "Resize the drawer"
     }
   }
 }

package/frontend-vue/layers/dms-ui/i18n/locales/ui-fr-FR.json

@@ -85,7 +85,8 @@
         "include": "contient",
         "exclude": "ne contient pas",
         "contains": "contient",
-        "not_contains": "ne contient pas"
+        "not_contains": "ne contient pas",
+        "array_contains_string": "contient"
       },
       "filter": {
         "boolean": {
@@ -108,7 +109,7 @@
       "show_archived": "Voir les éléments archivés",
       "archived": "Archivés",
       "archive_toggle": "Archives",
-      "archived_count": "{count} archivés",
+      "archived_count": "Archives : {count}",
       "archive_strip_title": "Éléments archivés.",
       "archive_strip_description": "Ils restent masqués de la liste habituelle jusqu’à leur restauration.",
       "archived_empty_title": "Aucun élément archivé",
@@ -177,6 +178,8 @@
         "save_as": "Enregistrer comme nouvelle vue",
         "save_current": "Enregistrer la vue actuelle",
         "delete": "Supprimer la vue",
+        "delete_title": "Supprimer cette vue ?",
+        "delete_description": "« {view} » sera supprimée définitivement. Si elle est ouverte, le tableau revient à son état par défaut.",
         "save_as_title": "Enregistrer comme nouvelle vue",
         "save_as_description": "Conservez les filtres, la recherche, le tri, les colonnes et l'affichage actuels sous un nom. Vous seul la verrez.",
         "save_as_confirm": "Enregistrer la vue",
@@ -257,6 +260,7 @@
       "reset": "Réinitialiser",
       "cancel": "Annuler",
       "save_changes": "Enregistrer les modifications",
+      "create": "Créer",
       "refresh_data": "Actualiser les données",
       "export_data": "Exporter les données"
     },
@@ -407,7 +411,8 @@
         "invalid": "Aucune erreur | 1 champ à corriger | {count} champs à corriger"
       },
       "error_summary": {
-        "title": "Aucun champ à corriger | 1 champ demande votre attention | {count} champs demandent votre attention"
+        "title": "Aucun champ à corriger | 1 champ demande votre attention | {count} champs demandent votre attention",
+        "resolved": "Tout est corrigé : le formulaire peut être enregistré."
       },
       "repeater": {
         "add": "Ajouter une ligne",
@@ -688,6 +693,9 @@
         "info": "note"
       }
     },
+    "flow_canvas": {
+      "delete_node": "Supprimer le nœud"
+    },
     "password_rules": {
       "head": "{met} sur {total} respectées",
       "verdict": {
@@ -719,7 +727,7 @@
     },
     "save_bar": {
       "unsaved": "Modifications non enregistrées",
-      "discard": "Annuler",
+      "discard": "Abandonner",
       "save": "Enregistrer",
       "saving": "Enregistrement",
       "saved": "Enregistré",
@@ -751,6 +759,7 @@
       "show_new": "Afficher",
       "paused": "En pause",
       "resume": "Reprendre",
+      "refresh": "Actualiser",
       "reason_hidden": "onglet masqué",
       "polling": "sans temps réel, relecture régulière",
       "table_held": "Tableau figé",
@@ -772,6 +781,9 @@
       "invalid_state": "L’état de l’aperçu est illisible.",
       "empty": "Rien à prévisualiser pour l’instant.",
       "unsafe_method": "{name} n’a pas été affiché : un aperçu ne fait que lire ses données, et {value} écrit."
+    },
+    "drawer": {
+      "resize": "Redimensionner le tiroir"
     }
   }
 }

package/frontend-vue/package.json

@@ -11,7 +11,7 @@
   "license": "Apache-2.0",
   "packageManager": "pnpm@10.6.5",
   "engines": {
-    "@antelopejs/dms-frontend": ">=0.6.3 <0.8.0"
+    "@antelopejs/dms-frontend": ">=0.8.0 <0.9.0"
   },
   "scripts": {
     "typecheck": "ajs dms verify-source --layer \"$PWD\" --local-package @antelopejs/dms=.. --local-package @antelopejs/interface-dms=../../interface-dms",
@@ -75,7 +75,7 @@
   },
   "devDependencies": {
     "@antelopejs/core": ">=1.16.0 <2",
-    "@antelopejs/dms-frontend": ">=0.6.3 <0.7.0",
+    "@antelopejs/dms-frontend": ">=0.8.0 <0.9.0",
     "@eslint/js": "^8.57.0",
     "@inertiajs/vue3": "^3.7.0",
     "@nuxt/ui": "4.10.0",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@antelopejs/dms",
-  "version": "0.9.7",
+  "version": "0.10.0",
   "description": "The AntelopeJS dashboard management system: admin dashboards declared in TypeScript, with auth and tenancy, data management, file uploads, notifications and realtime.",
   "keywords": [
     "antelopejs",
@@ -22,6 +22,7 @@
   },
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
+  "dmsFrontend": "dist/frontend-module.js",
   "files": [
     "dist",
     "!dist/.tsbuildinfo",
@@ -57,16 +58,15 @@
     "@antelopejs/interface-api": ">=0.0.15 <1.0.0",
     "@antelopejs/interface-api-util": ">=0.1.3 <1.0.0",
     "@antelopejs/interface-core": ">=0.2.4 <1.0.0",
-    "@antelopejs/interface-data-api": ">=0.2.2 <1.0.0",
+    "@antelopejs/interface-data-api": ">=0.3.0 <1.0.0",
     "@antelopejs/interface-database": ">=0.1.10 <1.0.0",
     "@antelopejs/interface-database-decorators": ">=0.1.9 <1.0.0",
-    "@antelopejs/interface-dms": ">=0.7.4 <0.8.0",
+    "@antelopejs/interface-dms": ">=0.8.0 <0.9.0",
     "@antelopejs/interface-email": ">=0.0.6 <1.0.0",
     "@antelopejs/interface-file-storage": ">=0.1.4 <1.0.0",
     "archiver": "^7.0.1",
     "csv-stringify": "^6.7.0",
     "defu": "^6.1.4",
-    "ignore": "^7.0.5",
     "jsonwebtoken": "^9.0.3",
     "mmdb-lib": "^3.0.3",
     "node-cron": "^4.2.1",
@@ -116,7 +116,7 @@
     "registry": "https://registry.npmjs.org/"
   },
   "optionalDependencies": {
-    "@antelopejs/interface-dms-automation": ">=0.2.1 <1.0.0",
+    "@antelopejs/interface-dms-automation": ">=0.4.0 <1.0.0",
     "@antelopejs/interface-redis": ">=0.0.9 <1.0.0"
   },
   "peerDependencies": {
@@ -145,6 +145,7 @@
     "knip:all": "knip",
     "docs:catalog": "node scripts/docs-catalog.mjs",
     "docs:catalog:check": "node scripts/docs-catalog.mjs --check",
-    "docs:screenshots": "node scripts/docs-screenshots.mjs"
+    "docs:screenshots": "node scripts/docs-screenshots.mjs",
+    "realtime:tabs-check": "node scripts/realtime-tabs-check.mjs"
   }
 }

package/skills/dms/SKILL.md

@@ -34,7 +34,7 @@ skill (shipped with `@antelopejs/core`).
   `pageRoutePath(slug, route)`); a plain `Controller` the frontend calls sits under
   `/api/<module>/`. A URL names the page's record with `{{params.id}}` /
   `{{query.X}}`; `periodScope` binds a block to a `PeriodSelector`; `realtimeTopic` re-fetches on a
-  `PublishMessage`. Texts are `$` i18n keys or `ComposedText`, never formatted server-side.
+  `PublishMessage` (publish tenant data with `{ tenantId }`). Texts are `$` i18n keys or `ComposedText`, never formatted server-side.
 - **It's interfaces all the way down.** Everything you consume is imported from an
   `@antelopejs/interface-dms/...` subpath; a distributable module exposes its own API from a companion
   `@antelopejs/interface-<name>` package listed in `antelopeJs.implements`.

package/skills/dms-auth/SKILL.md

@@ -78,7 +78,7 @@ RegisterPermission("cookbook.edit", {
   title: "$dms_cookbook.perm.edit",   // i18n key — add to every locale file
   icon: "i-ph-pencil",
   defaultGranted: false,
-  // dependencies: ["cookbook.view"],  // declarative metadata only — not enforced or auto-granted
+  // dependencies: ["cookbook.view"],  // enforced by HasPermission; granted with it by the roles editor and on save
 });
 ```
 
@@ -86,7 +86,9 @@ Then gate with `@AuthUserWithPermission(...)` or the page/component permission o
 check imperatively, use `dms/permissions`: `GetEffectiveUserPermissions`, `HasPermission`,
 `GetPermission` / `GetPermissions` (`GetUserPermissions` for the base set). Two extension
 points reshape the model: `RegisterPermissionsResolver` (`dms/permissions-resolver`) rewrites
-a user's effective set, and `RegisterTenantAccessGate` (`dms/tenant-access`, checked via
+a user's effective set (the role preview also runs it, with `context.preview` set on the
+resolver's fourth argument and the viewer's user id: shape the set as for an ordinary
+member there, never from the viewer's standing), and `RegisterTenantAccessGate` (`dms/tenant-access`, checked via
 `CheckTenantAccess` / `AssertTenantAccess`) can block a whole tenant. The `dms/guards`
 decorators also run the tenant access gate; routes that must stay reachable for a denied
 tenant (billing, recovery) opt out with `@AuthTenantOwner({ bypassTenantAccessGate: true })`.
@@ -102,7 +104,7 @@ there too); `RoleModel`, `UserInviteModel`, `TenantModel`, `TenantMemberModel` u
 The DMS is **multi-tenant by default** (single-tenant apps live in the `default` tenant).
 Primitives, covered in `docs/03.auth-and-tenancy/03.multi-tenant.md`: `@TenantScopedModel`
 (`dms/tenant-scoped-model`) scopes a model to the request's tenant, `getRequestTenantId`
-(`dms/request-tenant`) reads it, `applyTenantOwnership`
+(`dms/request-tenant`) reads it (the verified credential's tenant, `default` without one), `applyTenantOwnership`
 (`dms/tenant-ownership`) upserts a user's tenant membership (roles + owner flag),
 `inviteUserToTenant` (`dms/invites`, expiry `INVITE_EXPIRY_DAYS`), and `CROSS_INSTANCE`
 (`@antelopejs/interface-database`) for cross-tenant queries. SaaS mode (Stripe billing,

package/skills/dms-best-practices/REFERENCE.md

@@ -13,11 +13,13 @@ Material for [SKILL.md](SKILL.md): mapping design elements to DMS blocks, the `P
 | Ranked list, leaderboard | `TopListCard` | Bar position, rank badge style |
 | Date range picker | `PeriodSelector` (`variant: "segmented"` for pills) | Preset labels |
 | Live / pause switch | `LiveToggle` | Pill vs segmented |
+| Context bar of a page with a period or live data | `pageToolbar()` (a `PageToolbar` holding the `LiveToggle` and `PeriodSelector`) | Leading blocks, `size` |
 | Table, list with actions | `TableView` over a DataController (`displays` for cards / kanban) | Column widths, row height (`density`) |
 | Detail facts of a record | `KeyValueList` | Value alignment |
 | Recent events, audit log | `ActivityFeed` | Day separators vs relative times |
 | Usage bar, quota | `Meter` | Bar thickness (`size`) |
 | Notice, alert strip | `Banner` | Wash vs flat background |
+| Strip under the dashboard header, across pages | `RegisterLayoutBanner` (backend): the app's pages by default, `scope: "everywhere"` for a workspace-wide state | Not inside `/modules` unless scoped `everywhere` |
 | Empty / first-run screen | `EmptyState` (or `Guard` around blocks) | Illustration vs icon well |
 | Links to sub-pages as cards | `NavCardGrid` | Card height |
 | Code snippet | `CodeBlock` | Theme of the highlighting |

package/skills/dms-best-practices/SKILL.md

@@ -73,5 +73,9 @@ The protocol is done when every visibly different component has an answer and ev
 
 - Every page field and child is a DMS block, except custom blocks the user chose through the path.
 - Every `CustomComponent` has `.meta({ name, description, icon })` with `$` keys present in every locale file.
+- Every automation node a module registers names itself, its description and each schema property's `title` and `description` with `$` keys present in every locale file (`docs/02.building/06.backend-services.md`, Texts in the builder).
+- An automation action with side effects (email, notification, write) declares `dryRun(input, ctx)`: it checks the input as `execute` would and acts on nothing, so a builder Test run sends nothing (`docs/02.building/06.backend-services.md`, Test runs).
+- Locale values escape vue-i18n's special characters as literals (`{'@'}`, `{'{'}`, `{'}'}`, `{'|'}`): a raw `@` or brace breaks the message's compilation (`docs/02.building/07.localization.md`, Special characters).
 - Data comes from routes (`fetchUrl`) rather than options computed at registration; a custom block reads its route with `useApiData` (server-rendered, refreshed with the page) and writes with `$authFetch`.
+- Publish tenant data with the tenant id: a `PublishMessage` about one workspace's data passes `{ tenantId }`, or it wakes the page of every workspace.
 - Verified live with **dms-project** (the build only typechecks `src/`).

package/skills/dms-module/SKILL.md

@@ -85,7 +85,7 @@ module's frontend; without it the module is backend-only.
 
 `renderer` names the framework (Vue 3), not a loader release. The `@antelopejs/dms-frontend`
 releases the frontend module runs on go in the frontend module's own `package.json`, as
-`"engines": { "@antelopejs/dms-frontend": ">=0.6.0 <0.7.0" }`: the loader refuses the module
+`"engines": { "@antelopejs/dms-frontend": ">=0.8.0 <0.9.0" }`: the loader refuses the module
 outside that range. Cap it below the next loader minor while the loader is 0.x.
 
 An absolute link (a public file, a snippet to copy, a mail) is built on `await GetApiBaseUrl()`
@@ -103,7 +103,8 @@ module root** (nest under what `RegisterModule` returned, or rely on `defaultCat
 module pages cannot use the Settings category, and the module must exist before a page names
 it. Pages resolve at `/modules/<moduleId>/<urlSlug>`; entering the module lands on
 `landingPage` if set, else the first page by `order` — `/modules/<id>` itself redirects there (server
-redirect, query and hash kept), so never register a hidden page to forward it. Access is **owner-only by design**: the
+redirect, query and hash kept), so never register a hidden page to forward it. `store` is not a
+module id to take: `/modules/store` is the DMS's module store. Access is **owner-only by design**: the
 Modules group is visible to the platform owner alone (the `*` holder), and the
 `modules.<moduleId>.…` permission ids are module-scoped — never grantable through Roles. On a
 SaaS deployment that means you, the maker, not your customers; a screen for end users belongs

package/skills/dms-pages/REFERENCE.md

@@ -10,7 +10,7 @@ lists them with their option schemas); `docs/04.components/` has one page per bl
 
 | Group | Blocks |
 | --- | --- |
-| Layout | `Grid` + `GridRow` (children must be rows; `{ colSpan }` child metadata), `HStack` / `VStack` / `Spacer`, `Card` (slots `actions`, `footer`), `Tab` (`{ slot }` per child), `Guard`, `Placeholder` |
+| Layout | `Grid` + `GridRow` (children must be rows; `{ colSpan }` child metadata; a `GridRow` inside a cell, e.g. in a `Section`, spreads its own children rather than the grid's columns), `HStack` / `VStack` / `Spacer`, `PageToolbar` (`pageToolbar()`), `Card` (slots `actions`, `footer`), `Tab` (`{ slot }` per child), `Guard`, `Placeholder` |
 | Charts & widgets | `KpiCard`, `ChartCard` (wraps one chart), `TopListCard`, `PeriodSelector`, `LiveToggle`; charts `ChartLine`, `ChartArea`, `ChartRangeArea`, `ChartBar`, `ChartColumn`, `ChartScatter`, `ChartMixed`, `ChartRadar`, `ChartCandlestick`, `ChartDonut`, `ChartPie`, `ChartRadialBar`, `ChartHeatmap` |
 | Display | `StatGroup`, `KeyValueList`, `NavCardGrid`, `EmptyState` (its `code` shows a snippet), `Banner`, `CodeBlock` (`code` + `language`, or `fetchUrl` answering `{ code, language? }`) |
 | Lists & settings | `ActivityFeed`, `Meter`, `Section` + `FieldRow` |
@@ -38,7 +38,8 @@ gets `navigation` (J / K, `index` / `total` in the order shown) —
 A page's `headerActions` follow its URL: a target URL takes `{{params.X}}` / `{{query.X}}`
 (`?workspace={{query.workspace}}`, a pair the page has no value for is dropped), a label's
 translation takes the page's route and query parameters (`"Download {locale}.json"`), and an
-`availability` reads `context.query`, asked again when the query changes — no need to build
+`availability` reads `context.query` and the route parameters in `context.params` (`:id`),
+asked again when either changes (a detail page hides "Edit" for a missing record) — no need to build
 the header in Vue with `usePageHeaderActions` to carry the scope —
 `packages/interface-dms/docs/3.base/6.layout.md#buttons-that-follow-the-page-url`. An `availability`
 answering `{ hidden: true }` leaves the button out for that query (`{ reason }` only
@@ -48,13 +49,42 @@ component's client-side ones (default `0`, served first on a tie: `order: -1` pu
 "Export" before a served "Add key") — `packages/interface-dms/docs/3.base/6.layout.md#ordering-the-header`.
 
 A button or row action (`customButtons`, `rowActions.custom`, a page's `headerActions`)
-points at an `ActionTarget`. A `drawer` target opens from the bottom; give it
-`direction: "right"` for a side sheet (an inspector, a detail panel) instead of hosting your
-own drawer in a `CustomComponent`.
-To read rows one after the other next to the table (a request log), use a `sidePanel`
-target instead: a non-modal panel docked on the right whose header the DMS draws (title,
-`rowTitle` naming the row from its fields, `positionLabel` "x of y", previous / next, J / K, close), `?record=` kept by default (`deepLink: false` opts out), a "not found" state on a 404 (`notFound: { title, description }`) and the table's
-`rowClick: "single"` (a `TableView.fromSource` table reads a deep-linked row beyond its first page through `fetchRowUrl: "/api/x/{{row.id}}"`) — never bridge the table's DOM to build one —
+points at an `ActionTarget`. A detail or record panel (an inspector, a request, a run) is a
+`drawer` target — never a `sidePanel`, and never your own drawer hosted in a
+`CustomComponent`. It opens from the bottom; `direction: "right"` makes it a side sheet,
+600px wide from `lg` (`size: "3xl"` opens it at a modal's width instead), which the user
+resizes by its inner edge and which opens again at that size. On a row it takes the side
+panel's row options: the DMS draws the row header once `rowTitle` (naming the row from its
+fields) or `positionLabel` ("Request 4 of 50") is set (`rowHeader: true` with the defaults),
+with previous / next next to close; J / K step in place, through every row the table lists
+(the position counts them all, a step past the page loaded turns the page, a step goes to
+the open row's neighbour by id so live rows never make it skip or revisit one, and a
+deep-linked row past the page loaded is located in the table's result, in the order
+the table shows, pinned rows leading their own page); `deepLink:
+true` on the target keeps
+`?record=`; `notFound: { title, description }` draws the 404 state — with the table's
+`rowClick: "single"` (a `TableView.fromSource` table reads a deep-linked row beyond its first
+page through `fetchRowUrl: "/api/x/{{row.id}}"`) — never bridge the table's DOM to build one —
+`docs/04.components/08.tables/8.row-drawers.md#detail-drawers`.
+A drawer a module opens itself through `useDrawer()` keeps the size the user gives it under
+its `sizeKey`, by default its `containerId`, else its component's name — pass `sizeKey` only
+when one component opens drawers that must not share a size, or when the component is
+anonymous — `docs/06.frontend-composables/05.ui-toolkit.md`. On a row of a list the module draws
+itself, `rowHeader: { title, positionLabel, navigation }` draws the DMS's row header (position,
+previous / next, J and K; `titleClass`, `titleBreakAfter`, `subtitle`, `subtitleClass` and
+`component` / `componentOptions` under the position line shape it — never a header component of
+the module's own); `patch({ componentOptions, componentKey, rowHeader })` steps it — never
+import the layer's `RowHeader` component —
+`docs/06.frontend-composables/05.ui-toolkit.md#a-drawer-on-a-row-of-your-own`.
+A drawer's body is a flex column: a body component with a growing root (`flex flex-1 flex-col`)
+fills it and ends with `<DmsContainerFooter>` for its buttons — never measure the drawer nor use
+`--dms-form-foot-*`; a code editor taking the height left (`DmsInputCode fill`, in a stacked
+`DmsFieldRow fill`) — never count its lines from the drawer's size —
+`docs/06.frontend-composables/05.ui-toolkit.md#a-body-that-fills-the-drawer-and-its-footer`.
+A `useDrawer()` body injects what the component calling `useDrawer()` (in its setup) provides —
+never pass a context as a prop to provide it again in the body.
+A `sidePanel` target (non-modal, docked on the right) still works, but is meant for global,
+page-independent panels such as an assistant dock —
 `docs/04.components/08.tables/8.row-drawers.md#side-panel`.
 A button downloading a file the user's session may read (`/api/...`) takes a `download`
 target, `{ url, filename? }`, with the same `{{row.field}}` / `{{query.X}}` tokens — never a Vue
@@ -76,9 +106,15 @@ row's ⋯ button — `docs/04.components/08.tables/0.index.md#pinned-rows`.
 - `.watch(FormEvents.SUBMIT_SUCCESS, BlockFunctions.REFRESH_PAGE)` makes the page's data blocks
   (table views included) re-fetch after a form saves.
 - `periodScope` binds a card, chart, list block, `Meter` or `TableView.fromSource` to a
-  `PeriodSelector`, which keeps its period in the page URL (`?<id>.period=`).
-- `realtimeTopic` re-fetches a chart, list block, `Meter`, `Tab` badges or `TableView` on each
-  `PublishMessage`.
+  `PeriodSelector`, which keeps its period in the page URL (`?<id>.period=`). Its selected
+  comparison drives the cards: `KpiCard` names it ("vs previous year", leave `compareLabel`
+  unset) and prints the route's `previousValue`; "No comparison" hides the change, the value
+  compared against and the label on `KpiCard`, `ChartCard` and `TopListCard`.
+- `realtimeTopic` re-fetches a chart, a `KpiCard`, list block, `Meter`, `Tab` badges or `TableView` on each
+  `PublishMessage`. Publish tenant data with the tenant id (`{ tenantId }`): without it the message
+  is global and refetches the page in every workspace. A `TableView` needs no option: the DMS
+  publishes to every tenant for a table of the shared schema, and a platform (module) page receives
+  every tenant's changes.
 
 ### Live pages
 
@@ -86,7 +122,24 @@ row's ⋯ button — `docs/04.components/08.tables/0.index.md#pinned-rows`.
   options (`slowRateAfter: { period: "7d", maxRate: 60 }` for long periods, `rememberKey: "<module>"`
   to share the choice; `maxRate` is also the polling interval while the stream is down) and places a
   `LiveToggle()` (Live / Pause, L key; `variant: "pill"`, `missedLabel` for "N new requests").
-- `liveHold: true` keeps a table's rows while paused; `liveHold: { whileRowOpen, whileScrolled,
+- A page with a period or live data starts with `pageToolbar({ leading, live, period })`
+  (`base/page-toolbar`): the same bar on every page — leading blocks, then "Updated N s ago",
+  Live / Pause, the window and the 1H / 24H / 7D / 30D presets, at one `size` and one height
+  (24 / 28 / 32 px, with live or not). `live: false` or `period: false` drops a control; without
+  `live` it shows the last read and a refresh button. A module's leading chip takes the toolbar's
+  height from `usePageToolbarSize().heightClass`. More than one comparison offered
+  (`comparisons: ["previous-period", "previous-year", "none"]`) draws a menu naming the compared window ("vs 16 – 17 Oct ▾", the range label then
+  without its "vs …"); a single one
+  stays on without a control. A `custom` preset shows as a calendar icon, named in full.
+  `live` / `period` also take `childId` (keep an id roles already grant, `live` / `period` by
+  default) and `meta` (roles-editor name), so a page never builds the toolbar by hand for that;
+  `transformOptions` changes a child's options at each registration (a setting read in
+  `construct()`) — never patch the toolbar's children afterwards;
+  an editor reads the default children from the block type's `initialChildren`.
+  A component may draw `<DmsPageToolbarBlock>` and `<DmsLiveToggleBlock>` itself, around controls
+  of its own: neither needs a `componentId` or `pageId` there.
+- `liveHold: true` keeps a table's rows while paused, and in Direct while they are on screen (new
+  rows wait behind a "N new · Show" pill over the rows, counting the rows the table's query matches now beyond those held, through its count route); `liveHold: { whileRowOpen, whileScrolled,
   whileSearching, whileSorted }` also holds the table alone; `liveHold.missedLabel` words its "N new".
   Paused, an event counts as its `payload.ids` rows or its `payload.count`, so a module may batch
   publishes with `{ count }`. A hidden tab and `?live=0` pause the page too.
@@ -94,7 +147,18 @@ row's ⋯ button — `docs/04.components/08.tables/0.index.md#pinned-rows`.
   `setMissedDetail()`); one that reads its own data on a topic calls
   `usePageLiveRefresh(refresh, { realtimeTopic, idleRefresh })` — never a throttle of its own.
   `refreshPageBlocks()` (user actions) always reads; `refreshLivePageBlocks()` (timers, feeds) is
-  held while paused.
+  held while paused. A table view's write (row/bulk action, its form saved) already
+  calls `refreshPageBlocks()`: KPIs and badges of the page need no wiring of their own.
+- Making a block live: a built-in data block names a `realtimeTopic` (its builder registers the
+  topic on the page) and the backend calls `PublishMessage`; a table view follows its controller's
+  row events by itself. A block without a topic reads only on `refreshLivePageBlocks()`, the
+  polling while the stream is down and `refreshPageBlocks()` — no timer while the stream is up. A
+  custom component's own topic needs `RegisterPageTopic(pageId, topic)` in the backend.
+- Pause (user, hold, hidden tab) freezes every block of the page at once: realtime events, row
+  events, page-topic events behind `useApiData`, `refreshLivePageBlocks()`, `idleRefresh`, the
+  stream-down polling and a component's `useApiData` `refreshInterval`. Each block that missed
+  something reads once on resume. User actions and inputs (period, filter, search, sort, page)
+  still read; notifications, presence and the menu are not the page and keep updating.
 
 ### Texts
 
@@ -103,6 +167,13 @@ row's ⋯ button — `docs/04.components/08.tables/0.index.md#pinned-rows`.
   KeyValueList / Banner / NavCardGrid / ActivityFeed / Meter / TopListCard item texts, ActivityFeed
   `params` (typed `count` for plurals), tab badges and layout banners (`RegisterLayoutBanner({ resolve })`
   → `{ text, actions }`) take it. Never format text server-side.
+- A layout banner (`RegisterLayoutBanner`) shows on the application's pages only by default, never
+  inside `/modules` (modules page, module store, module pages). Give `scope:
+  LayoutBannerScope.EVERYWHERE` to a workspace-wide state (billing past due, suspended workspace,
+  maintenance) that must follow the user into modules; leave the default for anything about the
+  application's own data.
+- A route that must word a text reads the request's `x-content-language` header (the language on
+  screen), never `users.language` (the profile's, for mails).
 - A status the backend computes (health, outage) is a `Banner({ fetchUrl })`: the route answers a
   `BannerContent` (its buttons may run `api` / modal / quick-action targets with `confirm`) or
   `null` for no banner.
@@ -110,13 +181,20 @@ row's ⋯ button — `docs/04.components/08.tables/0.index.md#pinned-rows`.
 ### Blocks
 
 - `StatGroup` details and `NavCardGrid` card titles take up to two lines before their ellipsis.
+- `StatGroup({ columnsFrom: "md" })` (`DmsStatGroup columns-from`) sets all `columns` side by side from
+  that group width — never a class forcing the group's grid (`[&>div]:grid-cols-*`).
 - `ActivityFeed`: `wrap: true` for entries read whole (leave `fillHeight` off), `visibleItems: N`
   for a "Show N more" fold.
 - `KeyValueList` rows take `copy: true` or `copyValue` (the text to copy instead).
+- A fetched list block draws `skeletonCount` placeholders until its first answer in a client
+  navigation (a server render waits for the data): set it to the usual number of items so the page
+  does not move when they land. A refresh keeps the items on screen until the new ones land.
 - `TopListCard({ actions })` puts link buttons in its head; `Tab({ fit: true })` keeps pill tabs to
   their labels' width; with `persistState` the URL names the open tab by its slot (`?tab=tester`).
 - A `ChartCard` plotting several series names them with `showSeriesLegend: true` (placed by the
   chart's `legendPosition`) — never a raw Apex `legend` in `rawOptions`.
+- A chart route sends series names, categories (`x`) and point labels as `$` keys, bare chart or
+  `ChartCard` alike: the browser translates them, so donut slices are `{ x: "$app.plan.pro", y }`.
 
 ### Tables
 
@@ -128,13 +206,42 @@ row's ⋯ button — `docs/04.components/08.tables/0.index.md#pinned-rows`.
   `{ label, tone?, variant: "soft" | "outline" }`.
 - A `TableView` over a shared controller hides a column on one page with
   `columns: { hidden: ["workspace"] }` — no view just to hide it.
+- Conditional fields on a `TableView`'s generated forms go in `forms: { new?, edit?, view? }`, each a
+  callback receiving the form's builder: `new: (form) => form.watch(FormEvents.FIELD_CHANGE, …)` —
+  they run in a drawer, a modal or a form page alike; no custom page just to add a watch.
+- A table of more than a few columns that phones will read offers the cards and opens them there:
+  `displays: [{ id: "table" }, { id: "cards" }], mobileDisplay: "cards"`. Only a display the user
+  saved or the open view's own `display` overrides it: a `views.defaultView` that sets no display
+  still opens phones on the cards.
 - A table ordered by hand (`reorder: { field }`) moves rows on the grid and cards on the `cards`
   display alike; a `card.component` receives a `reorder` prop and `v-bind`s `reorder.handle`.
+- A `cards` display whose cards need more room sets `card.minWidth` (a CSS length, `230px` by
+  default, the skeleton follows): cards stretch to fill the row, a short list's up to twice that.
+- A `cards` display whose `card.component` is taller than the built-in card sets
+  `card.skeletonHeight` to its height (a CSS length): the loading placeholder takes it, so the
+  pagination footer does not drop when the cards land.
+- A built-in card carries its row's actions top right (the grid row's buttons and … menu, same
+  rules and confirmations); a `card.component` opts in with `<component :is="rowActions" />`.
 
 ### Forms
 
-- A unit after a number field is `NumberType({ suffix: "$…days" })`; a character counter is
+- A unit after a number field is `NumberType({ suffix: "$…days" })` (written in its table cells,
+  cards and read-only fields too); a character counter is
   `StringType({ maxLength, showCount: true })` — no custom `inputComponent` for either.
+- A relation picker depending on another field of the form takes `filterBy: { field, from }`:
+  `RelationType({ dataApiController: SiteController, filterBy: { field: "customer", from: "customer" } })`
+  lists only the picked customer's sites, searches again when it changes and clears a pick made for
+  the previous one — no custom picker. `field` must be filterable on the related controller (it
+  throws at registration otherwise) — `docs/04.components/10.data-types.md`.
+- A field whose value follows another one (stage → probability) takes a watch running
+  `FormFunctions.SET_FIELD_VALUE` with `{ targetField, valueMap: { won: 100, lost: 0 } }` (or a fixed
+  `value`) on `FIELD_CHANGE` keyed on the source `fieldId` — never a custom component. It writes on a
+  change only, never over the values a record opens with; a rule that must hold stays in the write
+  route — `docs/04.components/07.forms/0.index.md#setting-a-value-from-another-field`.
+- A short number or text field (an estimate, a count, a code) takes `width: "compact"` on its
+  `NumberType` / `StringType` rather than filling the row; one bounded to 6 digits or a
+  `maxLength` of 16 or less is compact already, and `width: "full"` opts out. Phones keep the
+  full row.
 - A long sectioned `Form` groups its navigation with `FormSection.navGroup`, in the side list and
   the `sectionNav: "jump"` chips alike.
 - A module's own `inputComponent` submits its form, adds a validator and focuses a field with
@@ -145,7 +252,9 @@ row's ⋯ button — `docs/04.components/08.tables/0.index.md#pinned-rows`.
 ### Custom components
 
 - Name the record at the end of the breadcrumb with
-  `usePageRecordLabel().setLabel(useDmsRoute().path, label)`.
+  `usePageRecordLabel().setLabel(useDmsRoute().path, label)`. A hidden detail page next to its
+  list (`project/:id` beside `projects`) declares `parent: ProjectsPage` in its menu options so
+  the breadcrumb shows the list before the record — `docs/02.building/04.navigation.md`.
 - Format through `useRegionalFormat()`; `useRegionalFormat({ locale: "format" })` writes in the
   locale of the DMS's texts (`en` → `en-GB`).
 - Bring a block into view with `scrollToBlock("tabs.statistics")` — never a DOM query.

package/skills/dms-pages/SKILL.md

@@ -63,7 +63,7 @@ export class SubmitRecipePage extends PageController("submit-recipe", { displayN
     ],
     submitUrl: "/api/recipes",   // a route — often declared on this same class
     submitUrlMethod: HttpMethod.post,
-    kind: "action",              // sends something new each time; omit for a record form (save bar)
+    kind: "action",              // sends something new each time; "create" for a form making a row; omit for a record form (save bar)
   });
 }
 ```

package/skills/dms-project/DEV-SERVERS.md

@@ -46,11 +46,33 @@ not survive orb updates.
 Only the project in `DMS_BACK_DIR`. The script records the pids it starts in
 `DMS_BACK_DIR/.antelope/dms-dev.pid`; without that file it matches only dev processes whose working
 directory or command line lies under `DMS_BACK_DIR`. Each process gets SIGTERM, then SIGKILL after
-`DMS_DEV_STOP_GRACE` seconds (default 10). Other projects' dev servers on the machine keep running,
+`DMS_DEV_STOP_GRACE` seconds (default 10); on Windows, `taskkill /T /F` ([below](#windows)). Other projects' dev servers on the machine keep running,
 which is why the script replaces `pkill` by name (`pkill -9 node`, `pkill -f antelope-runner`).
 
+`restart-back` and `restart-front` touch one server only: the pid the pid file records for it
+(`backend` or `frontend`) and its process tree, or, when that pid is gone (the server crashed),
+the processes of that server alone that the scan below finds. The other server keeps running.
+
 Run one `start` or `restart` at a time: a second concurrent call hits a port or lock conflict.
 
+## Windows
+
+The script runs in Git Bash, MSYS2 or Cygwin. Their `ps` lists only their own processes and takes
+no `-o`, and they have no `setsid`, while the dev servers run as native `node.exe` processes. So on
+Windows the script:
+
+- reads the Windows process table through PowerShell (`Get-CimInstance Win32_Process`: pid, parent
+  pid, creation time, command line), and maps the pids it recorded to Windows pids through
+  `/proc/<pid>/winpid`;
+- follows parent pids for the tree (Windows has no process groups), counting only children created
+  after their parent, so that a process holding a dead parent's reused pid is left alone;
+- stops each tree at once with `taskkill /T /F`: a console node process handles no SIGTERM, so
+  there is no grace period (`DMS_DEV_STOP_GRACE` is unused);
+- without a pid file, matches only processes whose command line names `DMS_BACK_DIR`: a native
+  process exposes no working directory. Servers started through `pnpm` rarely do (only binaries
+  installed in the project's `node_modules` show its path), so start them with the script, which
+  records their pids.
+
 ## Pitfalls
 
 - **Zombie frontend processes.** The frontend CLI spawns children. `stop` signals the whole

package/skills/dms-project/REFERENCE.md

@@ -20,5 +20,5 @@ Put secrets/per-deploy values in `envOverrides` (a framework feature); per-envir
 | --- | --- |
 | Pages, TableViews, the component builders | **dms-pages** (`docs/02.building/03.pages-and-components.md`, `docs/04.components/`) |
 | Auth on pages/routes, permissions, tenants | **dms-auth** (`docs/03.auth-and-tenancy/`) |
-| Hooks, notifications, realtime, replayable jobs, HTML render, export jobs | `docs/02.building/06.backend-services.md` |
+| Hooks, notifications, realtime, replayable jobs, automation nodes, HTML render, export jobs | `docs/02.building/06.backend-services.md` |
 | Custom Vue in your `frontend-vue/` module | `docs/02.building/08.frontend-layer.md`, `docs/05.extending-the-dashboard/`, `docs/06.frontend-composables/` |

package/skills/dms-project/SKILL.md

@@ -193,6 +193,8 @@ DMS_BACK_DIR=<resolved-path> bash "<skill-base-dir>/scripts/dms-dev.sh" restart
 | Command | Use when |
 | --- | --- |
 | `restart` | Hot reload cannot apply a change, or the state is unknown. |
+| `restart-front` | The frontend crashed or hangs while the backend runs: only the frontend is stopped (if it runs) and started again. |
+| `restart-back` | The backend crashed alone: only the backend is restarted, and the frontend keeps running. Run `restart-front` too if the frontend then serves stale layers. |
 | `start` | Nothing is running (fresh shell, after `stop`). |
 | `stop` | Before walking away, before destructive operations, on session cleanup. |
 | `status` | The user asks whether the DMS is running. |
@@ -202,7 +204,8 @@ The call returns once both servers print their ready line and reports the URLs t
 fails fast when a server exits early, otherwise after 180 s per server (`DMS_DEV_TIMEOUT`). The
 servers keep running detached. By default the script runs the project's `pnpm dev` and
 `pnpm frontend:dev` scripts (a project convention that expands to the two commands above);
-override them with `DMS_BACK_CMD` / `DMS_FRONT_CMD`.
+override them with `DMS_BACK_CMD` / `DMS_FRONT_CMD`. It runs in bash on Linux and macOS, and in
+Git Bash, MSYS2 or Cygwin on Windows ([DEV-SERVERS.md](DEV-SERVERS.md#windows)).
 
 When you hand off for manual testing, run `restart` yourself, wait for both ready lines, then tell
 the user what to click. Boot failures, stale frontends, a refused credential (401), stop scope and