Merge branch 'main' into fix/durable-package-install

Author: os-zhuang

.github/workflows/release.yml

@@ -74,7 +74,7 @@ jobs:
           # ADR-0085 (hotcrm#423) — the intended break, explicitly digested
           # downstream. Bump this ref whenever a deliberate spec surface
           # removal ships a matching hotcrm release.
-          HOTCRM_REF: v1.2.1
+          HOTCRM_REF: v1.2.2
         run: bash scripts/downstream-smoke.sh
 
       - name: Create Release Pull Request or Publish to npm

.objectui-sha

@@ -1 +1 @@
-9aec6817d8f682e42eab6b7539391e8d9dc04d21
+09e1b261563284fbeddc7c5c1bde753330ccab87

AGENTS.md

@@ -261,6 +261,7 @@ export default {
    never `gh pr merge --auto`). A finished task = a merged PR, not a dirty
    working tree.
 3. **Add a changeset for feature work.** When the change is a feature or functional improvement, run `pnpm changeset` (or add a `.changeset/*.md` entry) describing it before committing. Pure bug fixes do **not** require a changeset.
+   **Breaking changesets must carry their migration.** If the change removes or renames anything an author can write (a spec key, an export, a config field), the changeset body must state the FROM → TO mapping and the one-line fix — this text ships to consumers as `CHANGELOG.md` inside the npm package and is what an upgrading agent greps after the tombstone error. Removing an authorable spec key also requires a tombstone entry in the relevant `UNKNOWN_KEY_GUIDANCE` map (see `object.zod.ts`) so the rejection itself carries the prescription.
 4. Update `CHANGELOG.md` / `ROADMAP.md` if user-facing or architectural.
 5. **Delete temporary artifacts** — screenshots, traces, scratch logs, `.playwright-mcp/`, throwaway `tmp*.ts`, ad-hoc scripts. Repo must look identical to before, minus intended changes.
 

content/docs/guides/data-modeling.mdx

@@ -67,7 +67,7 @@ export const MyObject = ObjectSchema.create({
 | `icon` | string | Icon identifier | `'building'` |
 | `description` | string | Help text | `'Companies...'` |
 | `titleFormat` | string | Record title template (`{{record.field}}` interpolation) | `'{{record.name}} - {{record.id}}'` |
-| `highlightFields` | string[] | Most-important fields, in priority order (default columns, cards, previews, detail highlight strip; ADR-0085 — formerly `compactLayout`, still accepted as an alias) | `['name', 'status']` |
+| `highlightFields` | string[] | Most-important fields, in priority order (default columns, cards, previews, detail highlight strip; ADR-0085 — formerly `compactLayout`; the old spelling was retired and is now rejected) | `['name', 'status']` |
 
 ### Enable Features
 

content/docs/guides/metadata/object.mdx

@@ -68,7 +68,7 @@ export const Account = ObjectSchema.create({
 | :--- | :--- | :--- | :--- |
 | `displayNameField` | `string` | optional | Field used as record display name (defaults to `'name'`) |
 | `titleFormat` | `string` | optional | Title expression (e.g. `'{name} - {code}'`) |
-| `highlightFields` | `string[]` | optional | Most-important fields in priority order — default list columns, cards, previews, detail highlight strip (ADR-0085; formerly `compactLayout`, accepted as an alias) |
+| `highlightFields` | `string[]` | optional | Most-important fields in priority order — default list columns, cards, previews, detail highlight strip (ADR-0085; formerly `compactLayout` — the old spelling was retired and is now rejected) |
 | `stageField` | `string \| false` | optional | Linear lifecycle field; `false` declares the status field non-linear and suppresses stage heuristics (ADR-0085) |
 | `recordName` | `object` | optional | Record name auto-generation config |
 

examples/app-crm/CHANGELOG.md

@@ -1,5 +1,14 @@
 # @objectstack/example-crm
 
+## 4.0.69
+
+### Patch Changes
+
+- Updated dependencies [6a9397e]
+- Updated dependencies [c0efe5d]
+  - @objectstack/spec@11.10.0
+  - @objectstack/runtime@11.10.0
+
 ## 4.0.68
 
 ### Patch Changes

examples/app-crm/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@objectstack/example-crm",
-  "version": "4.0.68",
+  "version": "4.0.69",
   "description": "Minimal CRM example — a smoke-test workspace that exercises the metadata loading pipeline (objects → views → app → dashboard → hook → flow → seed). For a full-featured enterprise CRM see https://github.com/objectstack-ai/hotcrm.",
   "license": "Apache-2.0",
   "private": true,

examples/app-showcase/CHANGELOG.md

@@ -1,5 +1,18 @@
 # @objectstack/example-showcase
 
+## 0.2.15
+
+### Patch Changes
+
+- Updated dependencies [6a9397e]
+- Updated dependencies [c0efe5d]
+  - @objectstack/spec@11.10.0
+  - @objectstack/cloud-connection@11.10.0
+  - @objectstack/connector-rest@11.10.0
+  - @objectstack/connector-slack@11.10.0
+  - @objectstack/driver-sql@11.10.0
+  - @objectstack/runtime@11.10.0
+
 ## 0.2.14
 
 ### Patch Changes

examples/app-showcase/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@objectstack/example-showcase",
-  "version": "0.2.14",
+  "version": "0.2.15",
   "description": "Kitchen-sink showcase workspace — exercises every metadata type, every view type, every chart type, and the major end-to-end capability chains (security, automation, AI). Built for demonstration, debugging, and coverage-driven verification.",
   "license": "Apache-2.0",
   "private": true,

examples/app-showcase/src/objects/project.object.ts

@@ -56,6 +56,24 @@ export const Project = ObjectSchema.create({
     start_date: Field.date({ label: 'Start Date' }),
     end_date: Field.date({ label: 'Target End Date' }),
     owner: Field.text({ label: 'Owner', maxLength: 200 }),
+    // Multi-value fields — the payload for the grid's *bulk-edit* showcase. A
+    // multiselect (fixed options) and a multi-user field are exactly the two
+    // shapes that, before #2185, the bulk dialog could not set: its people /
+    // select picker collapsed to a single value and overwrote the array. The
+    // list view's `bulkActionDefs` below now sets both with real multi-select
+    // controls, writing an array patch.
+    labels: {
+      type: 'multiselect',
+      label: 'Labels',
+      options: [
+        { label: 'Frontend', value: 'frontend', color: '#3B82F6' },
+        { label: 'Backend', value: 'backend', color: '#8B5CF6' },
+        { label: 'Design', value: 'design', color: '#EC4899' },
+        { label: 'QA', value: 'qa', color: '#F59E0B' },
+        { label: 'DevOps', value: 'devops', color: '#10B981' },
+      ],
+    },
+    team_members: Field.user({ label: 'Team Members', multiple: true }),
     // Roll-up summaries — recomputed server-side whenever a child task is
     // inserted / updated / deleted (FK auto-detected: showcase_task.project).
     task_count: Field.summary({