docs(build/data): align data-modeling pages with framework 16.0

- enable.softDelete → enable.trash in the capability example (softDelete
  is a 16.0 tombstone; object.zod.ts throws with guidance); added a
  'Changed in 16.0' callout covering the removed object props
  (versioning, search→searchableFields, recordName→autonumber
  nameField, keyPrefix, tags, active, abstract).
- referenceFilters warning upgraded from 'accepted but unread' to
  removed-in-16.0 (stripped at parse; lookupFilters + dependsOn is the
  only form).
- summaryOperations example gains the new 16.0 filter (filtered
  roll-ups, #1868) with re-aggregation semantics.
- Validation rules: 'delete' event removed (guard deletions with
  beforeDelete — the evaluator never ran on delete); state_machine
  gains initialStates (#3165) with the events:['insert','update']
  requirement called out (events gates dispatch, so insert must be
  listed or initialStates is dead); noted 16.0 evaluates rules on
  multi-row updates (#3106).
- Formulas: 'New in 16.0' — date-vs-number arithmetic is a build-time
  error pointing at daysBetween/daysFromNow/addDays/addMonths (#3306);
  null-guard ternary compiles; floor/ceil registered; date equality
  now matches via temporal coercion (#3183).
- zh-Hans twins updated faithfully; other locale twins' code blocks
  fixed mechanically.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Kj2MJEPXoUXC4LiC3XYJc

Author: claude

content/docs/build/data/formulas.mdx

@@ -99,6 +99,22 @@ Field.formula({
 > `coalesce(record.x, '')` when concatenating — or use `joinNonEmpty`
 > and skip the ceremony.
 
+### New in 16.0
+
+- **Date arithmetic against numbers is a build-time error.** Expressions
+  like `record.end_date - record.start_date + 1` or `today() + 30`
+  always faulted at runtime (silently evaluating to null); the build now
+  rejects them with an error pointing at `daysBetween(a, b)` for spans
+  and `daysFromNow(n)` / `addDays(d, n)` / `addMonths(d, n)` for shifts.
+- **The null-guard ternary compiles.** `cond ? value : null` — e.g.
+  `record.end_date != null ? daysBetween(record.start_date, record.end_date) + 1 : null`
+  — is the blessed way to keep a formula blank until its inputs exist.
+- **`floor(x)` / `ceil(x)` are registered.** They round toward −∞ / +∞
+  (so `floor(-1.2) == -2`) — not toward zero like integer division.
+- **Date equality against `today()` now matches.** Temporal values are
+  coerced before comparison, so `record.due_date == today()` and
+  `daysBetween(today(), record.due_date) == 0` both work as expected.
+
 ### Formula as record title
 
 Since ADR-0079, a record's title is a designated field via `nameField`

content/docs/build/data/formulas.zh-Hans.mdx

@@ -87,6 +87,13 @@ Field.formula({
 
 > **提示：**CEL 遇到 `null + string` 会抛错，所以拼接时把可能为空的操作数包进 `coalesce(record.x, '')` —— 或者直接用 `joinNonEmpty`，省掉这套仪式。
 
+### 16.0 新增
+
+- **日期与数字做算术现在是构建期错误。**像 `record.end_date - record.start_date + 1` 或 `today() + 30` 这样的表达式过去总在运行时出错（静默求值为 null）；现在构建会直接拒绝，并在报错中指向 `daysBetween(a, b)`（求跨度）以及 `daysFromNow(n)` / `addDays(d, n)` / `addMonths(d, n)`（移动日期）。
+- **空值守卫三元表达式可以编译了。**`cond ? value : null` —— 例如 `record.end_date != null ? daysBetween(record.start_date, record.end_date) + 1 : null` —— 是让公式在输入就绪前保持空白的推荐写法。
+- **注册了 `floor(x)` / `ceil(x)`。**它们分别向 −∞ / +∞ 取整（所以 `floor(-1.2) == -2`）—— 不像整数除法那样向零取整。
+- **日期与 `today()` 的相等比较现在能匹配了。**时间值会在比较前先做类型归一，因此 `record.due_date == today()` 和 `daysBetween(today(), record.due_date) == 0` 都能按预期工作。
+
 ### 公式作为记录标题
 
 自 ADR-0079 起，记录的标题由 `nameField` 指定的字段决定 —— 组合式标题可以用文本公式：

content/docs/build/data/index.de.mdx

@@ -216,7 +216,7 @@ ObjectSchema.create({
     apiEnabled: true,         // generated REST endpoints
     trackHistory: true,       // audit log of field changes
     feeds: true,              // sys_comment / sys_activity / @mentions
-    softDelete: true,         // tombstone instead of hard delete
+    trash: true,              // soft-delete with restore (default true)
   },
 });
 ```

content/docs/build/data/index.es.mdx

@@ -215,7 +215,7 @@ ObjectSchema.create({
     apiEnabled: true,         // generated REST endpoints
     trackHistory: true,       // audit log of field changes
     feeds: true,              // sys_comment / sys_activity / @mentions
-    softDelete: true,         // tombstone instead of hard delete
+    trash: true,              // soft-delete with restore (default true)
   },
 });
 ```

content/docs/build/data/index.fr.mdx

@@ -217,7 +217,7 @@ ObjectSchema.create({
     apiEnabled: true,         // generated REST endpoints
     trackHistory: true,       // audit log of field changes
     feeds: true,              // sys_comment / sys_activity / @mentions
-    softDelete: true,         // tombstone instead of hard delete
+    trash: true,              // soft-delete with restore (default true)
   },
 });
 ```

content/docs/build/data/index.ja.mdx

@@ -216,7 +216,7 @@ ObjectSchema.create({
     apiEnabled: true,         // generated REST endpoints
     trackHistory: true,       // audit log of field changes
     feeds: true,              // sys_comment / sys_activity / @mentions
-    softDelete: true,         // tombstone instead of hard delete
+    trash: true,              // soft-delete with restore (default true)
   },
 });
 ```

content/docs/build/data/index.ko.mdx

@@ -214,7 +214,7 @@ ObjectSchema.create({
     apiEnabled: true,         // generated REST endpoints
     trackHistory: true,       // audit log of field changes
     feeds: true,              // sys_comment / sys_activity / @mentions
-    softDelete: true,         // tombstone instead of hard delete
+    trash: true,              // soft-delete with restore (default true)
   },
 });
 ```

content/docs/build/data/index.mdx

@@ -217,11 +217,19 @@ ObjectSchema.create({
     feeds: true,              // sys_comment / @mentions (default true)
     activities: true,         // mirror CRUD to sys_activity timeline (default true)
     files: true,              // Attachments panel (opt-in, default false)
-    softDelete: true,         // tombstone instead of hard delete
+    trash: true,              // soft-delete with restore (default true)
   },
 });
 ```
 
+> **Changed in 16.0:** the object-level `softDelete` prop is removed —
+> `ObjectSchema.create` now throws a located error if you pass it. The
+> shipped equivalent is `enable: { trash: true }` (soft-delete with
+> restore), on by default. The same cleanup removed `versioning`,
+> `search` (use top-level `searchableFields`), `recordName` (use an
+> autonumber field as `nameField`), `keyPrefix`, `tags`, `active`, and
+> `abstract`.
+
 Since ObjectStack 14 the `enable.*` flags are **enforced**, not
 advisory: `feeds: false` rejects comment creation with 403
 `FEEDS_DISABLED`, `files` must be opted in before `sys_attachment` rows

content/docs/build/data/index.zh-Hans.mdx

@@ -208,11 +208,18 @@ ObjectSchema.create({
     feeds: true,              // sys_comment / @提及（默认 true）
     activities: true,         // CRUD 镜像到 sys_activity 时间线（默认 true）
     files: true,              // 附件面板（需显式开启，默认 false）
-    softDelete: true,         // 软删除而非硬删除
+    trash: true,              // 软删除并可恢复（默认 true）
   },
 });
 ```
 
+> **16.0 变更：**对象级 `softDelete` 属性已被移除 —— 再传入它，
+> `ObjectSchema.create` 会抛出带定位信息的错误。对应的现行能力是
+> `enable: { trash: true }`（软删除并可恢复），默认开启。同一轮清理还
+> 移除了 `versioning`、`search`（改用顶层 `searchableFields`）、
+> `recordName`（改用作为 `nameField` 的自动编号字段）、`keyPrefix`、
+> `tags`、`active` 和 `abstract`。
+
 自 ObjectStack 14 起，`enable.*` 开关是**强制执行**的，而不再只是声明：
 `feeds: false` 会以 403 `FEEDS_DISABLED` 拒绝评论创建；`files` 必须显式开启
 后才能创建 `sys_attachment` 行（否则返回 403 `FILES_DISABLED`）；

content/docs/build/data/relationships.mdx

@@ -68,9 +68,10 @@ contact: Field.lookup('contact', {
 ```
 
 > **Warning:** The legacy `referenceFilters: string[]` property (e.g.
-> `['is_active = true']`) is accepted by the schema but **not read by
-> the record-picker UI** — it filters nothing. Always use the
-> structured `lookupFilters` + `dependsOn` shown above.
+> `['is_active = true']`) is **removed in 16.0** — it is stripped at
+> parse time, and even before removal the record-picker UI never read
+> it, so it filtered nothing. The structured `lookupFilters` +
+> `dependsOn` shown above is the only supported form.
 
 ## Master-detail (owned children)
 
@@ -167,13 +168,20 @@ total_lines: {
     object: 'order_line',    // child object to aggregate
     field: 'quantity',       // field to aggregate
     function: 'sum',         // count | sum | min | max | avg
+    filter: { status: 'active' },  // new in 16.0: aggregate only matching children
   },
 }
 ```
 
 Summary fields are read-only and computed from the children — you never
 write them directly.
 
+**New in 16.0:** the optional `filter` is a query-style `where`
+predicate — only child rows matching it are aggregated (e.g. count only
+`status == 'active'` children), and the roll-up re-aggregates when a
+child moves in or out of the predicate. It also lets several summaries
+roll up the *same* child object into different totals.
+
 ## Querying across relationships
 
 Load related records in one call with `expand` — the query API follows