@@ -0,0 +1,10 @@
+---
+'@objectstack/skills': patch
+---
+
+docs(skills): objectstack-ui carries the view and action judgment the hosted build agent learned — a view added beside the list, the empty board over a just-added group field, an operation is an action whose body writes, the view kind the request names
+
+Clause-②: no
+Metadata-protocol: none
+
+Card 1 of the cloud#3659 ruling A split, the `objectstack-ui` port (the last of three) — the judgment the schema cannot express and the published skill did not yet state. `rules/list-views.md`: "add a kanban / calendar / gallery / gantt view" is a NEW `listViews` entry whose key encodes its kind, the default `list` untouched; a view's kind changes in place only on an explicit ask; a board grouped by a field added in the same change opens with every existing record in the trailing `Uncategorized` lane, and the hand-over says so — with the correction that on a SQL datasource a literal `defaultValue` is emitted as the added column's DEFAULT, so there existing rows read it. `SKILL.md`: an operation on a record is `defineAction` metadata, never a view; a write button's body must call `ctx.api.object(OBJ).update` with `language: 'js'` and `api.write` — a body that only returns the new values writes nothing; a named view kind (gallery, gantt, kanban) is kept, never downgraded to `grid`. The two Chinese fragments left in `rules/navigation.md` and `rules/record-page.md` are English now: the shipped skill text is English-only. Three eval cases pin the teachings (views-apps-actions-pages 13–15).
@@ -704,7 +704,22 @@ export const CEILINGS = new Map([
   // `rules/record-page.md`; one Detailed Rules link and the CRM blueprint row reworded.
   // The file is 14194 bytes less its stamp line -> 3544 tokens; the ceiling follows it
   // down to the measurement, the ratchet's ordinary direction.
-  ['skills/objectstack-ui/SKILL.md', 3544],
+  // 3544 -> 3814 (#31155, the objectstack-ui port of the cloud#3659 ruling-A split): two
+  // teachings the hosted build agent carried privately — an operation on a record is `action`
+  // metadata, never a view, and a write button's body must CALL `ctx.api…update` with
+  // `language: 'js'` and `api.write` (the return value is applied to nothing); and the view
+  // kind the request names is kept, never downgraded to `grid`. PAID DOWN FIRST by genuine
+  // deletion in this file: the intro paragraph restating the frontmatter description, the
+  // "load objectstack-formula" sentence restating the frontmatter, Common Pitfalls 1–2
+  // restating `rules/list-views.md` § Column Features (one pointer line now), the blueprint
+  // row's `slotted` / `full` clause restating Detailed Rules' Record Page line, the
+  // "canonical reference" sentence said twice, the App-navigation row's gloss. `main` base
+  // 14151 bytes (14131 priced) -> 15276 (15256 priced) -> 3814 tokens, pinned AT the
+  // measurement, zero headroom. Authority: the ruling of record that orders this text into
+  // the published skills, objectstack-ai/cloud#3659 letter A (ruling comment 6682024726), via
+  // the standing 2026-10-27 ruling (record 6513306068), quoted verbatim in the PR body.
+  //   ceil(($(wc -c < skills/objectstack-ui/SKILL.md) - 20) / 4) == ceil(15256 / 4)
+  ['skills/objectstack-ui/SKILL.md', 3814],
   // 8333 -> 6193: RE-LOCK at the landed count after the #19715 split (decision
   // batch #213 item 1, maintainer 「1 2 4 同意」): the worked R1, the report
   // template and the v17-canonical shapes block moved VERBATIM into
@@ -982,12 +997,34 @@ export const CEILINGS = new Map([
   // the paragraph restating the allowed-set table above it, and the related-record search
   // prescription that objectstack-data → Search Fields carries whole — so the file nets -4
   // and the ceiling follows it down to the new measurement.
-  ['skills/objectstack-ui/rules/list-views.md', 3129],
+  // 3129 -> 3451 (#31155, the objectstack-ui port of the cloud#3659 ruling-A split): one new
+  // section beside the kanban config — "add a kanban / calendar / gallery / gantt view" is a
+  // NEW `listViews` entry whose key encodes its kind, the default `list` untouched, a kind
+  // changed in place only on an explicit ask; and the board grouped by a field added in the
+  // same change opens with every existing record in the trailing `Uncategorized` lane, with
+  // the three-part hand-over (and the SQL-datasource literal-`defaultValue` exception the
+  // driver's ADD COLUMN DEFAULT makes true). PAID DOWN FIRST by genuine deletion in this
+  // file: the kanban example's `// required on every list view` comment (the sentence above
+  // it), the `userFilters` bullet's "Need named presets? Add a listViews entry" restating the
+  // bullet before it, "the saved-views switcher already covers presets" (same bullet), the
+  // search example's `searchableFields: []` comment restating the table row above it, the
+  // narrowing sentence's "refuses the request" clause restating the ⛔ section below it, the
+  // two Data Source code comments restating the blockquote under them, the `summary`
+  // comment's "footer aggregation" restating the Column Features row. `main` base 12503
+  // bytes -> 13802 -> 3451 tokens, pinned AT the measurement, zero headroom. Authority as the
+  // SKILL.md row above: cloud#3659 letter A (6682024726) via record 6513306068, quoted
+  // verbatim in the PR body.
+  //   ceil($(wc -c < skills/objectstack-ui/rules/list-views.md) / 4) == ceil(13802 / 4)
+  ['skills/objectstack-ui/rules/list-views.md', 3451],
   // 2273 -> 2196 (#27059): LOWERED. The Surface bullet points at `rules/record-page.md`,
   // says create / edit is a modal or the `editMode: 'page'` route, and the Overlay-width
   // bullet moved there whole (the `size` bucket, the deprecated pixel keys); the ceiling
   // follows the file down to the measurement (8784 bytes).
-  ['skills/objectstack-ui/rules/navigation.md', 2196],
+  // 2196 -> 2184 (#31155): LOWERED. The two Chinese fragments in the interface-page signal
+  // list are English (the shipped skill text is English-only), and the bullet's repeated
+  // objectui ADR-0055 citation (the section heading carries it) is gone; the ceiling follows
+  // the file down to the measurement (8734 bytes).
+  ['skills/objectstack-ui/rules/navigation.md', 2184],
   // 5501 -> 5692 (#19715, card item 4): a 5-line table of contents at the top,
   // anchors to the file's existing headings, nothing else changed. +191 tokens,
   // zero headroom to absorb any of it, ceiling +191. Maintainer ruling
@@ -1012,7 +1049,11 @@ export const CEILINGS = new Map([
   // landed at +39 (1876 -> 1915), so the package nets +592 tokens, every one of them
   // teaching the surface `main` ships today and none of it restating a sibling file.
   //   ceil($(wc -c < skills/objectstack-ui/rules/record-page.md) / 4) == ceil(3981 / 4)
-  ['skills/objectstack-ui/rules/record-page.md', 996],
+  // 996 -> 991 (#31155): LOWERED. The record page's second tab is named as the console
+  // labels it (Activity) in place of the Chinese word, and step 5's "(one page at two
+  // widths)" aside — step 1 already says layout follows the surface's width — is gone; the
+  // ceiling follows the file down to the measurement (3961 bytes).
+  ['skills/objectstack-ui/rules/record-page.md', 991],
 
   // ── 2026-09-22 the #19715 split — decision batch #213 item 1 ─────────────
   // The maintainer ruled the four over-500-line published SKILL.md files split
 
@@ -25,10 +25,6 @@ metadata:
 
 # UI Design — ObjectStack UI Protocol
 
-Expert instructions for designing user interfaces using the ObjectStack
-specification. This skill covers Views (list, form, kanban, calendar, …),
-App navigation, Dashboards, Reports, and Actions.
-
 ---
 
 ## View Types
@@ -47,6 +43,14 @@ App navigation, Dashboards, Reports, and Actions.
 | `chart` | Aggregate visualisation over the object (mini chart view) |
 | `tree` | Self-referencing hierarchy (tree-grid) |
 
+**Keep the kind the request names.** A photo wall, card wall or catalogue of
+covers is `gallery` (an image, avatar or file field as `gallery.coverField`),
+a schedule or timeline over a start/end date pair is `gantt`, a board is
+`kanban`; never downgrade a named kind to `grid`: the file parses and the user
+opens a table where they asked for a board. Adding one beside the list, and
+the empty board over a field added in the same change:
+[List Views](./rules/list-views.md#adding-a-board-calendar-gallery-or-gantt-beside-the-list).
+
 ### Form Views
 
 | Type | When to Use |
@@ -114,8 +118,7 @@ ObjectUI forms consume them. Their semantics and server behaviour:
 
 UI-side: inline master-detail grids evaluate these rules **row-by-row** against
 each child row. Use `requiredWhen` — the `conditionalRequired` alias was REMOVED
-in protocol 17 and is now a parse error. Load **objectstack-formula** when
-authoring non-trivial CEL.
+in protocol 17 and is now a parse error.
 
 ---
 
@@ -183,15 +186,13 @@ Use this CRM-style structure as the canonical UI assembly reference:
 |:--|:--|:--|
 | Multi-view object UI | `src/views/*.view.ts` | Define default `list` + `form`, then named `listViews` / `formViews` for scenarios |
 | **Public form** | `src/views/*.view.ts` (formView with `sharing: { enabled: true, allowAnonymous: true, publicLink: 'slug' }`) | Web-to-Lead at `GET/POST /api/v1/forms/:slug` |
-| App navigation | `src/apps/*.app.ts` | Use grouped nav trees, `viewName` shortcuts, and `requiresObject` for capability-aware visibility |
+| App navigation | `src/apps/*.app.ts` | Grouped nav trees, `viewName` shortcuts, `requiresObject` |
 | **Analytics dataset** | `src/datasets/*.dataset.ts` | One per object you want reportable — dashboards and reports bind a **declared** dataset by name, so an object without one has no analytics face |
 | Dashboards | `src/dashboards/*.dashboard.ts` | Combine KPI + chart + table widgets with shared `dateRange` and `globalFilters` |
 | Reports | `src/reports/*.report.ts` | Select `rows` (dimensions) + `values` (measures) from that dataset; tabular/summary/matrix/joined |
-| Record pages | — (synthesized) | The object's declarations produce the page ([Record Page](./rules/record-page.md)); `src/pages/*.page.ts` only to override a `slotted` slot or for a `kind: 'full'` layout |
+| Record pages | — (synthesized) | The object's declarations produce the page ([Record Page](./rules/record-page.md)) |
 | User actions | `src/actions/*.actions.ts` | Use `flow` for orchestration and `script` for parameterized bulk mutations |
 
-This blueprint is the default for “build a complete metadata app UI” tasks.
-
 ---
 
 ## Date Macros — Filter Placeholders
@@ -233,19 +234,31 @@ Register them under `defineStack({ actions: [...] })`.
 | `api`    | Call a registered API endpoint                                     | `target`       |
 | `form`   | Open a FormView by name (routed to `/_console/forms/:name`)        | `target`       |
 
+**An operation is an `action`, never a view.** "Mark as done", "approve",
+"submit", "set status to X" — anything that DOES something to a record — is
+`defineAction` metadata; a view only displays. A record button carries
+`objectName` (what folds it into that object's record surfaces) and
+`locations`; with neither `locations` nor a view naming it in `rowActions` /
+`bulkActions` it renders nowhere (`action-no-placement`). **A write button must
+write:** `ctx.record` is a read-only snapshot and the body's return value is
+applied to nothing, so a body that only returns the new values or assigns to
+`ctx.record` changes nothing and still reports success
+(`action-record-write-discarded`). Write with `type: 'script'` and
+`body: { language: 'js', source: "await ctx.api.object('task').update({ id: ctx.recordId, status: 'done' });", capabilities: ['api.write'] }`:
+`js`, because an `expression` body is a pure formula with no I/O; `api.write`,
+because the sandbox throws on `ctx.api…update` / `insert` / `delete` without
+it; the option `value`, never its label. A multi-step operation is
+`type: 'flow'` with `target` naming a flow you also author.
+
 ---
 
 ## Common Pitfalls
 
-1. **Putting too many columns in a grid view.**
-   Users rarely need more than 6–8 columns visible by default. Use `hidden`
-   for secondary columns.
-
-2. **Forgetting `link: true` on the primary column.**
-   The first meaningful column (usually the name/subject) should be the
-   navigation link to the record detail.
+1. **Too many default columns, or no `link: true` on the primary one.** 6–8
+   visible columns is plenty (`hidden` the rest); the name/subject column is
+   the record link ([Columns](./rules/list-views.md#column-features)).
 
-3. **Putting widget grid placement in `position`.**
+2. **Putting widget grid placement in `position`.**
    The grid-placement field is `layout: { x, y, w, h }` — `position` is not a
    widget key and the closed schema REJECTS it by name (it was silently
    dropped before protocol 17). `layout` is optional: omit it and the widget
 
@@ -19,7 +19,9 @@ view / page / dashboard / report metadata.
   base object's `allowExport` permission).
 - `views-apps-actions-pages.json` — `defineView` containers, `App.create`
   navigation, `defineAction` surfaces, record / interface pages, package
-  docs, wizard forms.
+  docs, wizard forms, a view added beside the list (and the empty board over
+  a field added with it), a write button whose body writes, the view kind
+  the request names.
 
 ## Format
 
 
@@ -120,6 +120,36 @@
         "must_contain": ["listViews", "or: [", "{current_user_id}"],
         "must_not_contain": ["$or:", "logic:", "conditions:", "anyOf:"]
       }
+    },
+    {
+      "id": 13,
+      "prompt": "`task` already ships `defineView({ list, form })`. Reps want a board: add a `priority` select (A / B / C) to the object and a kanban grouped by it — the list must stay — and tell them what they will see when they first open the board.",
+      "expected_output": "A new `listViews.priority_kanban` entry (`type: 'kanban'`, the required top-level `columns`, `kanban: { groupByField: 'priority' }`) beside the untouched default `list`, never the list retyped into a board. The hand-over discloses the empty board: every existing task has no `priority` yet, so all of them sit in the trailing `Uncategorized` lane (scroll right on a narrow screen) under one empty lane per option; dragging a card onto a real lane writes the field, or they edit from the list; a runtime-token or CEL `defaultValue` on the new field fills no existing row, and a literal one does only on a SQL datasource, where it becomes the column DEFAULT.",
+      "files": [],
+      "assertions": {
+        "must_contain": ["listViews", "groupByField: 'priority'", "Uncategorized"],
+        "must_not_contain": ["list: { type: 'kanban'", "ready to use"]
+      }
+    },
+    {
+      "id": 14,
+      "prompt": "Add a 'Mark as done' button on `task` records that sets `status` to Done (the option is labelled Done, its value is `done`).",
+      "expected_output": "A `defineAction`, not a view: `name`, `label: 'Mark as done'`, `objectName: 'task'`, `locations: ['record_header']`, `type: 'script'`, `body: { language: 'js', source: \"await ctx.api.object('task').update({ id: ctx.recordId, status: 'done' });\", capabilities: ['api.write'] }`, `refreshAfter: true`. The body CALLS the update with the option value: a body that returns `{ status: 'done' }` or assigns to `ctx.record` writes nothing, an `expression` body cannot write, and without `api.write` the sandbox refuses the call.",
+      "files": [],
+      "assertions": {
+        "must_contain": ["defineAction", "objectName: 'task'", "ctx.api.object('task').update", "ctx.recordId", "api.write", "status: 'done'"],
+        "must_not_contain": ["defineView(", "language: 'expression'", "status: 'Done'"]
+      }
+    },
+    {
+      "id": 15,
+      "prompt": "Products need a photo wall: every product as a card with its `main_image` as the cover. Write the `listViews` entry.",
+      "expected_output": "`catalog_gallery: { label: 'Catalogue', type: 'gallery', data, columns: ['name', 'price'], gallery: { coverField: 'main_image' } }` — the kind the request names, added beside the existing views; not a table with an image column, and not the default `list` retyped.",
+      "files": [],
+      "assertions": {
+        "must_contain": ["type: 'gallery'", "coverField: 'main_image'"],
+        "must_not_contain": ["type: 'grid'"]
+      }
     }
   ]
 }