@cxtms/cx-schema 1.7.14 → 1.7.16

package/.claude/skills/cx-core/SKILL.md

@@ -10,7 +10,7 @@ Shared domain reference for CargoXplorer entities. Used by `cx-workflow` and `cx
 
 ## CX Server Authentication & Management
 
-For CLI authentication, PAT tokens, org management, and publishing: see [ref-cli-auth.md](ref-cli-auth.md)
+For CLI authentication, PAT tokens, org management, and releasing: see [ref-cli-auth.md](ref-cli-auth.md)
 
 ## GraphQL Querying & Audit History
 

package/.claude/skills/cx-core/ref-cli-auth.md

@@ -61,7 +61,7 @@ npx cxtms orgs use <orgId>
 npx cxtms orgs use
 ```
 
-The active org is cached in the session file and used by all server commands. **Always pass `--org <id>` on deploy/undeploy/publish/execute/logs commands** to avoid the interactive org picker blocking automation.
+The active org is cached in the session file and used by all server commands. **Always pass `--org <id>` on deploy/undeploy/release/execute/logs commands** to avoid the interactive org picker blocking automation.
 
 ## Session Resolution
 
@@ -88,7 +88,7 @@ Validates all YAML files first, then pushes modules and workflows to the server.
 
 ## App Manifest Management
 
-Server-side app manifest operations — install from git, publish changes to git, and list installed apps.
+Server-side app manifest operations — install from git, release changes to git, and list installed apps.
 
 ```bash
 # Install/refresh app from its git repository into the CX server
@@ -103,11 +103,11 @@ npx cxtms app install --branch develop
 # Install but skip modules that have unpublished local changes
 npx cxtms app install --skip-changed
 
-# Publish server changes to git (creates a PR) — message is required
-npx cxtms app publish -m "Add new shipping module"
+# Release server changes to git (creates a PR) — message is required
+npx cxtms app release -m "Add new shipping module"
 
-# Force publish all modules and workflows (not just changed ones)
-npx cxtms app publish -m "Full republish" --force
+# Force release all modules and workflows (not just changed ones)
+npx cxtms app release -m "Full republish" --force
 
 # List installed app manifests on the server
 npx cxtms app list
@@ -115,6 +115,6 @@ npx cxtms app list
 
 **`app install`** reads `repository` and `branch` from `app.yaml`, downloads the repo on the server side, and installs/updates all modules and workflows. Use `--force` to reinstall even if the version hasn't changed. Use `--skip-changed` to preserve modules with unpublished changes.
 
-**`app publish`** takes the current server state and publishes it to git by creating a PR. Requires a `-m` message describing the changes (like a git commit message). The server increments the version, creates a publish branch, commits all module/workflow YAML files, and opens a pull request to the target branch.
+**`app release`** takes the current server state and releases it to git by creating a PR. Requires a `-m` message describing the changes (like a git commit message). The server increments the version, creates a release branch, commits all module/workflow YAML files, and opens a pull request to the target branch.
 
 **`app list`** shows all installed app manifests with their version, status flags (disabled, unpublished changes, update available), and repository info.

package/.claude/skills/cx-core/ref-entity-organization.md

@@ -0,0 +1,41 @@
+# Organization Entity Reference
+
+Core tenant entity. Each organization represents a company/tenant in the system.
+
+## Fields
+
+| Field | Type | Notes |
+|-------|------|-------|
+| `organizationId` | `int` | PK |
+| `companyName` | `string` | Required |
+| `addressLine` | `string?` | |
+| `addressLine2` | `string?` | |
+| `cityName` | `string?` | |
+| `countryCode` | `string?` | |
+| `stateCode` | `string?` | |
+| `postalCode` | `string?` | |
+| `phoneNumber` | `string?` | |
+| `faxNumber` | `string?` | |
+| `uniqueId` | `Guid` | Immutable external identifier |
+| `slug` | `string?` | URL-friendly identifier for Public API routes (lowercase, hyphenated) |
+| `isDeleted` | `bool` | Soft delete |
+| `customValues` | `Dictionary?` | jsonb, merged on update |
+| `created` / `lastModified` | `DateTime` | Audit fields (from `AuditableEntity`) |
+| `createdBy` / `lastModifiedBy` | `string` | Audit fields |
+
+## Slug
+
+Generated by `SlugGenerator`: lowercased, non-alphanumeric stripped, spaces→hyphens, truncated to max length. Numeric suffix appended for uniqueness.
+
+Used by `PublicApiOrganizationResolver` to resolve org by slug or GUID in Public API URLs. Cached 1h sliding.
+
+## Relationships
+
+- `AspNetUserEmployees` — users belonging to this organization
+
+## Domain Methods
+
+- `ChangeSlug(string?)` — trims and lowercases
+- `ChangeCompanyName(string)`, `ChangeAddressLine(string?)`, etc.
+- `ChangeCustomValues(Dictionary?)` — merges into existing values
+- `DeleteOrganization()` — sets `IsDeleted = true`

package/.claude/skills/cx-module/SKILL.md

@@ -20,7 +20,7 @@ You are a CargoXplorer module YAML builder. You generate schema-valid YAML for C
 - **Feature folder**: `npx cxtms create module <name> --template <template> --feature <feature-name>`
 - **Deploy to server**: `npx cxtms appmodule deploy <file.yaml> --org <id>` — creates or updates module on the CX server
 - **Undeploy from server**: `npx cxtms appmodule undeploy <appModuleId> --org <id>` — removes a module by UUID
-- **Publish all**: `npx cxtms publish [--feature <name>] --org <id>` — push all modules and workflows to the server
+- **Publish all**: `npx cxtms publish [--feature <name>] --org <id>` — deploy all modules and workflows to the server
 
 ## Generation Workflow
 
@@ -409,28 +409,28 @@ Reusable select components (e.g., `Countries/Select`, `Ports/Select`) follow thi
 
 ## Server Module Commands
 
-Deploy, undeploy, and publish commands are listed in the CLI section at the top of this file. For authentication setup (login, PAT tokens, org management): see [cx-core/ref-cli-auth.md](.claude/skills/cx-core/ref-cli-auth.md)
+Deploy, undeploy, and release commands are listed in the CLI section at the top of this file. For authentication setup (login, PAT tokens, org management): see [cx-core/ref-cli-auth.md](.claude/skills/cx-core/ref-cli-auth.md)
 
-### Publishing App to GitHub
+### Releasing App to GitHub
 
-Use `app publish` to push modified modules and workflows from the CX server to a GitHub repository. This creates a branch and pull request — it does NOT push directly to the target branch.
+Use `app release` to release modified modules and workflows from the CX server to a GitHub repository. This creates a branch and pull request — it does NOT push directly to the target branch.
 
 ```bash
-# Publish all unpublished changes to GitHub (creates a PR) — message is required
-npx cxtms app publish -m "Add warehouse locations module"
+# Release all unpublished changes to GitHub (creates a PR) — message is required
+npx cxtms app release -m "Add warehouse locations module"
 
-# Publish specific modules and/or workflows by YAML file
-npx cxtms app publish -m "Fix country module" modules/my-module.yaml
-npx cxtms app publish -m "Update billing" modules/a.yaml workflows/b.yaml
+# Release specific modules and/or workflows by YAML file
+npx cxtms app release -m "Fix country module" modules/my-module.yaml
+npx cxtms app release -m "Update billing" modules/a.yaml workflows/b.yaml
 
-# Force publish all modules and workflows (not just unpublished ones)
-npx cxtms app publish -m "Full republish" --force
+# Force release all modules and workflows (not just unpublished ones)
+npx cxtms app release -m "Full republish" --force
 
-# Publish with explicit org
-npx cxtms app publish -m "Add warehouse locations module" --org 42
+# Release with explicit org
+npx cxtms app release -m "Add warehouse locations module" --org 42
 ```
 
-**What `app publish` does:**
+**What `app release` does:**
 1. Reads `app.yaml` for the `id` (appManifestId), repository, and branch
 2. Increments the app version (patch bump)
 3. Creates a `publish/{app-name}-v{version}-{timestamp}` branch on GitHub
@@ -438,11 +438,11 @@ npx cxtms app publish -m "Add warehouse locations module" --org 42
 5. Creates a pull request from the publish branch to the target branch
 6. Marks published modules and workflows as `hasUnpublishedChanges: false`
 
-**This is a commit-and-push operation** — it commits the current server-side YAML directly to GitHub via the API. No local git repo is involved. The modules and workflows being published are taken from the CX server database, not from local files. The YAML file arguments only identify *which* items to include by their IDs.
+**This is a release-to-git operation** — it commits the current server-side YAML directly to GitHub via the API. No local git repo is involved. The modules and workflows being released are taken from the CX server database, not from local files. The YAML file arguments only identify *which* items to include by their IDs.
 
-**Important:** Modules and workflows must be deployed to the TMS server before they can be published. Use `cxtms appmodule deploy` or `cxtms workflow deploy` first, then `cxtms app publish` to commit them to GitHub.
+**Important:** Modules and workflows must be deployed to the TMS server before they can be released. Use `cxtms appmodule deploy` or `cxtms workflow deploy` first, then `cxtms app release` to commit them to GitHub.
 
-**Do NOT run `app publish` automatically.** Only publish when the user explicitly requests it. Publishing creates a branch and PR on GitHub, so it should be done once when all changes are ready — not after every deploy.
+**Do NOT run `app release` automatically.** Only release when the user explicitly requests it. Releasing creates a branch and PR on GitHub, so it should be done once when all changes are ready — not after every deploy.
 
 **Prerequisites:**
 - `app.yaml` must exist with a valid `id` field

package/.claude/skills/cx-module/ref-components-layout.md

@@ -288,6 +288,47 @@ children:
 
 ---
 
+## slot
+
+Extension point that renders dynamically registered components targeting a named slot. Enables cross-module UI extensions without modifying the original layout.
+
+**Props:**
+| Prop | Type | Default | Description |
+|------|------|---------|-------------|
+| `name` | `string` | — | Slot name to match. Supports templates: `TMS/{{entityType}}/Actions` |
+| `itemTag` | `string` | `React.Fragment` | HTML element to wrap each extension (`div`, `li`, etc.) |
+
+**Children:** No — extensions are loaded from the database at runtime.
+
+Extension components must define `props.targetSlot` matching the slot name, `props.order` for sort order, and a `layout` object.
+
+```yaml
+# Define a slot extension point
+component: slot
+props:
+  name: "TMS/ShipmentDashboard/Tabs"
+```
+
+```yaml
+# Extension component (registered via another module's appComponents)
+name: "TMS/ShipmentDashboard/TrackingTab"
+props:
+  targetSlot: "TMS/ShipmentDashboard/Tabs"
+  order: 10
+layout:
+  component: tab
+  props:
+    label: { en-US: "Tracking" }
+  children:
+    - component: layout
+      props:
+        component: "TMS/Tracking/Panel"
+```
+
+**Naming convention:** `{Module}/{Entity}/{Location}` (e.g., `TMS/OrderDetail/Actions`)
+
+---
+
 ## line
 
 Simple `<hr>` horizontal divider.

package/.claude/skills/cx-module/ref-components-specialized.md

@@ -341,7 +341,9 @@ CSS Grid-based timeline with swim lanes, drill-down, and virtual scrolling.
 | `view` | `day \| week \| month \| year` | `week` | Time view |
 | `startDate` / `endDate` | `string` | — | Date range |
 | `eventSources` | `EventSource[]` | — | Event data sources |
+| `eventSources[].query.name` | `string` | `query1`, `query2`... | Source name, used as key in `summaryComponent` `dataSources` |
 | `eventTemplate` | `ComponentProps` | — | Custom event template |
+| `summaryComponent` | `ComponentProps` | — | Custom component rendered per column in the summary row. Replaces numeric totals when set. |
 | `options.height` | `string \| number` | `600` | Container height |
 | `options.cellHeight` | `number` | `60/100` | Cell height (px) |
 | `options.groupBy` | `string` | — | Field for swim lane grouping |
@@ -352,6 +354,14 @@ CSS Grid-based timeline with swim lanes, drill-down, and virtual scrolling.
 | `options.showWeekends` | `boolean` | `true` | Show weekends |
 | `options.showTotalCount` | `boolean` | `false` | Show event totals |
 
+**Summary component variables** (available when `summaryComponent` is set):
+| Variable | Type | Description |
+|----------|------|-------------|
+| `dataSources` | `Record<string, TimelineEvent[]>` | Per-source events filtered to the column, keyed by `query.name` |
+| `column` | `ColumnDefinition` | Column metadata (`id`, `label`, `date`, `startDate`, `endDate`) |
+| `columnIndex` | `number` | Zero-based column index |
+| `totalCount` | `number` | Total event count for the column across all sources |
+
 **Events:**
 | Event | Data | Description |
 |-------|------|-------------|
@@ -397,6 +407,36 @@ props:
           props: { date: "{{ date }}", assignee: "{{ row }}" }
 ```
 
+**Summary component example** (per-source breakdown per column):
+```yaml
+component: timeline-grid
+props:
+  view: week
+  options: { height: 600, enableNavigation: true }
+  eventSources:
+    - query:
+        name: ups
+        command: "query($s:String!,$e:String!){ upsShipments(start:$s,end:$e){ id date title } }"
+        variables: { s: "{{ startDate }}", e: "{{ endDate }}" }
+        path: upsShipments
+    - query:
+        name: fedex
+        command: "query($s:String!,$e:String!){ fedexShipments(start:$s,end:$e){ id date title } }"
+        variables: { s: "{{ startDate }}", e: "{{ endDate }}" }
+        path: fedexShipments
+  summaryComponent:
+    component: layout
+    props:
+      direction: column
+    children:
+      - component: text
+        props: { value: "UPS: {{ dataSources.ups.length }}" }
+      - component: text
+        props: { value: "FedEx: {{ dataSources.fedex.length }}" }
+      - component: text
+        props: { value: "Total: {{ totalCount }}" }
+```
+
 ---
 
 ## oauth2

package/.claude/skills/cx-workflow/SKILL.md

@@ -21,7 +21,7 @@ You are a CargoXplorer workflow YAML builder. You generate schema-valid YAML for
 - **Execute**: `npx cxtms workflow execute <workflowId|file.yaml> --org <id> [--vars '<json>'] [--file varName=path]` — trigger a workflow execution (--file uploads a local file and passes the URL as a variable)
 - **List logs**: `npx cxtms workflow logs <workflowId|file.yaml> --org <id> [--from YYYY-MM-DD] [--to YYYY-MM-DD]` — list executions with log availability
 - **Download log**: `npx cxtms workflow log <executionId> --org <id> [--json] [--console] [--output <file>]` — download execution log
-- **Publish all**: `npx cxtms publish [--feature <name>] --org <id>` — push all modules and workflows to the server
+- **Publish all**: `npx cxtms publish [--feature <name>] --org <id>` — deploy all modules and workflows to the server
 
 ## Generation Workflow
 
@@ -320,28 +320,28 @@ Implicit variable: `iteration` (zero-based).
 
 ## Server Workflow Commands
 
-Deploy, undeploy, and publish commands are listed in the CLI section at the top of this file. For authentication setup (login, PAT tokens, org management): see [cx-core/ref-cli-auth.md](.claude/skills/cx-core/ref-cli-auth.md)
+Deploy, undeploy, and release commands are listed in the CLI section at the top of this file. For authentication setup (login, PAT tokens, org management): see [cx-core/ref-cli-auth.md](.claude/skills/cx-core/ref-cli-auth.md)
 
-### Publishing App to GitHub
+### Releasing App to GitHub
 
-Use `app publish` to push modified workflows and modules from the CX server to a GitHub repository. This creates a branch and pull request — it does NOT push directly to the target branch.
+Use `app release` to release modified workflows and modules from the CX server to a GitHub repository. This creates a branch and pull request — it does NOT push directly to the target branch.
 
 ```bash
-# Publish all unpublished changes to GitHub (creates a PR) — message is required
-npx cxtms app publish -m "Add order notification workflow"
+# Release all unpublished changes to GitHub (creates a PR) — message is required
+npx cxtms app release -m "Add order notification workflow"
 
-# Publish specific workflows and/or modules by YAML file
-npx cxtms app publish -m "Fix tracking workflow" workflows/my-workflow.yaml
-npx cxtms app publish -m "Update shipping" workflows/a.yaml modules/b.yaml
+# Release specific workflows and/or modules by YAML file
+npx cxtms app release -m "Fix tracking workflow" workflows/my-workflow.yaml
+npx cxtms app release -m "Update shipping" workflows/a.yaml modules/b.yaml
 
-# Force publish all workflows and modules (not just unpublished ones)
-npx cxtms app publish -m "Full republish" --force
+# Force release all workflows and modules (not just unpublished ones)
+npx cxtms app release -m "Full republish" --force
 
-# Publish with explicit org
-npx cxtms app publish -m "Add order notification workflow" --org 42
+# Release with explicit org
+npx cxtms app release -m "Add order notification workflow" --org 42
 ```
 
-**What `app publish` does:**
+**What `app release` does:**
 1. Reads `app.yaml` for the `id` (appManifestId), repository, and branch
 2. Increments the app version (patch bump)
 3. Creates a `publish/{app-name}-v{version}-{timestamp}` branch on GitHub
@@ -349,11 +349,11 @@ npx cxtms app publish -m "Add order notification workflow" --org 42
 5. Creates a pull request from the publish branch to the target branch
 6. Marks published workflows and modules as `hasUnpublishedChanges: false`
 
-**This is a commit-and-push operation** — it commits the current server-side YAML directly to GitHub via the API. No local git repo is involved. The workflows and modules being published are taken from the CX server database, not from local files. The YAML file arguments only identify *which* items to include by their IDs.
+**This is a release-to-git operation** — it commits the current server-side YAML directly to GitHub via the API. No local git repo is involved. The workflows and modules being released are taken from the CX server database, not from local files. The YAML file arguments only identify *which* items to include by their IDs.
 
-**Important:** Workflows and modules must be deployed to the TMS server before they can be published. Use `cxtms workflow deploy` or `cxtms appmodule deploy` first, then `cxtms app publish` to commit them to GitHub.
+**Important:** Workflows and modules must be deployed to the TMS server before they can be released. Use `cxtms workflow deploy` or `cxtms appmodule deploy` first, then `cxtms app release` to commit them to GitHub.
 
-**Do NOT run `app publish` automatically.** Only publish when the user explicitly requests it. Publishing creates a branch and PR on GitHub, so it should be done once when all changes are ready — not after every deploy.
+**Do NOT run `app release` automatically.** Only release when the user explicitly requests it. Releasing creates a branch and PR on GitHub, so it should be done once when all changes are ready — not after every deploy.
 
 **Prerequisites:**
 - `app.yaml` must exist with a valid `id` field

package/dist/cli.js

@@ -117,7 +117,7 @@ ${chalk_1.default.bold.yellow('COMMANDS:')}
   ${chalk_1.default.green('appmodule')}       Manage app modules on a CX server (deploy, undeploy)
   ${chalk_1.default.green('workflow')}        Manage workflows on a CX server (deploy, undeploy, execute, logs, log)
   ${chalk_1.default.green('publish')}         Publish all modules and workflows to a CX server
-  ${chalk_1.default.green('app')}             Manage app manifests (install/upgrade from git, publish to git, list)
+  ${chalk_1.default.green('app')}             Manage app manifests (install/upgrade from git, release to git, list)
   ${chalk_1.default.green('query')}           Run a GraphQL query against the CX server
   ${chalk_1.default.green('gql')}             Explore GraphQL schema (types, queries, mutations)
   ${chalk_1.default.green('schema')}          Show JSON schema for a component or task
@@ -149,7 +149,7 @@ ${chalk_1.default.bold.yellow('OPTIONS:')}
   ${chalk_1.default.green('--output <file>')}        Save workflow log to file (or -o)
   ${chalk_1.default.green('--console')}              Print workflow log to stdout
   ${chalk_1.default.green('--json')}                 Download JSON log instead of text
-  ${chalk_1.default.green('-m, --message <msg>')}     Commit message for app publish (required)
+  ${chalk_1.default.green('-m, --message <msg>')}     Release message for app release (required)
   ${chalk_1.default.green('-b, --branch <branch>')}   Branch override for app install/publish
   ${chalk_1.default.green('--force')}                Force install (even if same version) or publish all
   ${chalk_1.default.green('--skip-changed')}         Skip modules with unpublished changes during install
@@ -311,15 +311,15 @@ ${chalk_1.default.bold.yellow('APP COMMANDS:')}
   ${chalk_1.default.cyan(`${PROGRAM_NAME} app upgrade`)}
   ${chalk_1.default.cyan(`${PROGRAM_NAME} app upgrade --force`)}
 
-  ${chalk_1.default.gray('# Publish server changes to git (creates a PR) — message is required')}
-  ${chalk_1.default.cyan(`${PROGRAM_NAME} app publish -m "Add new shipping module"`)}
+  ${chalk_1.default.gray('# Release server changes to git (creates a PR) — message is required')}
+  ${chalk_1.default.cyan(`${PROGRAM_NAME} app release -m "Add new shipping module"`)}
 
-  ${chalk_1.default.gray('# Publish specific workflows and/or modules by YAML file')}
-  ${chalk_1.default.cyan(`${PROGRAM_NAME} app publish -m "Fix order workflow" workflows/my-workflow.yaml`)}
-  ${chalk_1.default.cyan(`${PROGRAM_NAME} app publish -m "Update billing" workflows/a.yaml modules/b.yaml`)}
+  ${chalk_1.default.gray('# Release specific workflows and/or modules by YAML file')}
+  ${chalk_1.default.cyan(`${PROGRAM_NAME} app release -m "Fix order workflow" workflows/my-workflow.yaml`)}
+  ${chalk_1.default.cyan(`${PROGRAM_NAME} app release -m "Update billing" workflows/a.yaml modules/b.yaml`)}
 
-  ${chalk_1.default.gray('# Force publish all modules and workflows')}
-  ${chalk_1.default.cyan(`${PROGRAM_NAME} app publish -m "Full republish" --force`)}
+  ${chalk_1.default.gray('# Force release all modules and workflows')}
+  ${chalk_1.default.cyan(`${PROGRAM_NAME} app release -m "Full republish" --force`)}
 
   ${chalk_1.default.gray('# List installed app manifests on the server')}
   ${chalk_1.default.cyan(`${PROGRAM_NAME} app list`)}
@@ -3030,9 +3030,9 @@ async function runAppPublish(orgOverride, message, branch, force, targetFiles) {
     const token = session.access_token;
     const orgId = await resolveOrgId(domain, token, orgOverride);
     if (!message) {
-        console.error(chalk_1.default.red('Error: --message (-m) is required for app publish'));
+        console.error(chalk_1.default.red('Error: --message (-m) is required for app release'));
         console.error(chalk_1.default.gray('Describe what changed, similar to a git commit message.'));
-        console.error(chalk_1.default.gray(`Example: ${PROGRAM_NAME} app publish -m "Add new shipping module"`));
+        console.error(chalk_1.default.gray(`Example: ${PROGRAM_NAME} app release -m "Add new shipping module"`));
         process.exit(2);
     }
     const appYaml = readAppYaml();
@@ -3041,7 +3041,7 @@ async function runAppPublish(orgOverride, message, branch, force, targetFiles) {
         console.error(chalk_1.default.red('Error: app.yaml must have an `id` field'));
         process.exit(2);
     }
-    console.log(chalk_1.default.bold.cyan('\n  App Publish\n'));
+    console.log(chalk_1.default.bold.cyan('\n  App Release\n'));
     console.log(chalk_1.default.gray(`  Server:  ${new URL(domain).hostname}`));
     console.log(chalk_1.default.gray(`  Org:     ${orgId}`));
     console.log(chalk_1.default.gray(`  App:     ${appYaml.name || appManifestId}`));
@@ -4606,7 +4606,7 @@ async function main() {
         if (sub === 'install' || sub === 'upgrade') {
             await runAppInstall(options.orgId, options.branch, options.force, options.skipChanged);
         }
-        else if (sub === 'publish') {
+        else if (sub === 'release' || sub === 'publish') {
             await runAppPublish(options.orgId, options.message, options.branch, options.force, files.slice(1));
         }
         else if (sub === 'list' || !sub) {
@@ -4614,7 +4614,7 @@ async function main() {
         }
         else {
             console.error(chalk_1.default.red(`Unknown app subcommand: ${sub}`));
-            console.error(chalk_1.default.gray(`Usage: ${PROGRAM_NAME} app <install|upgrade|publish|list>`));
+            console.error(chalk_1.default.gray(`Usage: ${PROGRAM_NAME} app <install|upgrade|release|list>`));
             process.exit(2);
         }
         process.exit(0);