@@ -0,0 +1,52 @@
+---
+"@objectstack/spec": minor
+---
+
+feat(spec): a stored record-form `filter` at the converged rule-array doors is converted to the rule array wherever the mapping is lossless — the ADR-0087 D2 conversion `page-component-filter-record-to-rule-array` (#17321, ruling B)
+
+The one-filter-orthography convergence moved every page-component `filter` door onto the
+`ViewFilterRule` array and refused the MongoDB-style record it used to take — but converted
+nothing at rest. A page saved with the old form kept rendering, and the next person to open it
+in the builder and press Save was refused. This release adds the mechanical half.
+
+**What converts** — at `dataSource.filter` on any page component, at `properties.filter` on the
+`object-grid`, `object-metric`, `object-kanban`, `object-calendar`, `object-map`, `object-gantt`,
+`object-tree`, `object-timeline`, `element:number` and `element:record_picker` blocks, and at
+`properties.defaultFilters` on `object-grid`:
+
+| Stored | Becomes |
+| --- | --- |
+| `{ status: 'active' }` | `[{ field: 'status', operator: 'equals', value: 'active' }]` |
+| `{ amount: { $gt: 100 } }` | `[{ field: 'amount', operator: 'greater_than', value: 100 }]` |
+| `{ amount: { $gte: 1, $lte: 9 }, owner_id: 'u1' }` | three rules — they AND |
+| `[['owner_id', '=', '{current_user_id}']]` | `[{ field: 'owner_id', operator: 'equals', value: '{current_user_id}' }]` |
+| `{}` | `[]` |
+
+Values are carried verbatim, value placeholders and date macros included. The operator comes
+from the two tables the doors already use — a declared FilterCondition operator (`$gt`, `$nin`,
+`$notContains`, …) folded through `normalizeFilterOperator`, and an AST infix spelling (`=`,
+`!=`, `>=`, …) lowered through `parseFilterAST` — and every produced rule must parse at the
+door, so a converted page re-saves cleanly.
+
+**Where it runs.** On every stored-row read (`applyConversionsToStoredItem` replays it), so
+the metadata API already serves such a page in the rule-array form; `os migrate meta --stored --apply`
+persists it; `os migrate meta --from 17` lists the edits for author sources. It is retired from
+the authoring load path, so `defineStack` / `os validate` still refuse an author who writes the
+record form and teach the rule array — no accept-set change.
+
+**What is left exactly as stored.** A filter carrying `$and` / `$or` / `$not` is never
+flattened: the rule array only ANDs, and flattening `$or` or `$not` changes which rows the page
+selects. So is any filter with a part that has no lossless rule spelling — a `null` value (the
+renderer skips that key today, where a rule would test IS NULL), `$null` / `$exists`, an AST
+`like` / `ilike`, an array or object comparand in equality position, an AST `and` / `or` group.
+Conversion is all-or-nothing per filter: converting the mappable keys and dropping the rest
+would widen the filter. And every filter — the binding's included — of a component whose rows
+are **inline** (`data: { provider: 'value', … }`, a `data` array, or `staticData`) is left as
+stored: the `object-map`, `object-tree`, `object-calendar` and `object-gantt` renderers match
+that filter against their own rows in an in-memory data source that reads the record form but
+excludes every row for a rule array, so a rewrite there would empty the block. The same filter
+on a block that queries an object converts. Such a page keeps loading and rendering unchanged and is refused at its
+`filter` door on its next save — and for a combinator record that refusal no longer renders the
+combinator as a field (`{ field: '$or', … }`); it names the combinator and says why no rule
+spells it. `os migrate meta --stored` does not list these rows yet: a row the conversion leaves
+as stored reports there as already on protocol.
@@ -57,15 +57,29 @@ export const entry: SemanticMigration = {
     + 'array on `object-grid`) and three lint fixtures — every one rewritten to the rule array '
     + 'in the same change, and zero outside those files; this entry carries the prescription '
     + 'for authors outside the repo. '
-    + '⚠️ Metadata AT REST is deliberately NOT rewritten, and this disposition adds no D2 '
-    + 'conversion — a SemanticMigration converts nothing by its own type, and '
-    + '`os migrate meta --stored` (the pass over a deployment\'s `sys_metadata` rows) replays '
-    + 'D2 conversions only, so it has nothing to rewrite for this shape. The read path '
-    + 'does not re-validate stored rows '
-    + '(`applyConversionsToStoredItem` replays the full chain without validating, by its own '
-    + 'contract), so a stored page or block carrying the record form keeps loading unchanged '
-    + 'and is still rendered by objectui at the pinned `.objectui-sha`; what changes is that '
-    + 'RE-SAVING it is refused at the `filter` door, on its next save and not before.',
+    + 'Metadata AT REST: the mappable part of the table above is a D2 conversion, '
+    + '`page-component-filter-record-to-rule-array` (#17321, ruling B), so '
+    + '`os migrate meta --stored` (the pass over a deployment\'s `sys_metadata` rows) rewrites '
+    + 'a stored page whose `filter` is a flat record, an operator object whose operators the '
+    + 'rule vocabulary spells, several such keys, or a single-level AST tuple array, and every '
+    + 'stored-row read replays the same rewrite until it does. It is retired from the load '
+    + 'path: an author writing the record form is still refused at the `filter` door. ⚠️ A '
+    + 'filter carrying `$and` / `$or` / `$not` is left exactly as stored — the rule array '
+    + 'only ANDs, and flattening a combinator changes which rows the page selects — and so is '
+    + 'any filter with a part that has no lossless rule spelling: a `null` value (the renderer '
+    + 'skips that key, so it constrains nothing today, where a rule would test IS NULL), an '
+    + 'operator such as `$null` / `$exists` or an AST `like`, an array or object comparand in '
+    + 'equality position, or an AST `and` / `or` group. So is every filter — the binding\'s '
+    + 'included — of a component whose rows are INLINE (`data: { provider: \'value\' }`, a '
+    + '`data` array, or `staticData`): at the pinned `.objectui-sha` the `object-map`, '
+    + '`object-tree`, `object-calendar` and `object-gantt` blocks match that filter against '
+    + 'their own rows in an in-memory data source that reads the record form and excludes '
+    + 'EVERY row for a rule array, so a rewrite there would empty the block. Such a row keeps loading unchanged '
+    + '(`applyConversionsToStoredItem` replays the chain without validating, by its own '
+    + 'contract) and is refused at the `filter` door on its next save — for a combinator '
+    + 'record, a refusal that names the combinator and says why no rule spells it. '
+    + '`os migrate meta --stored` does not list these rows yet: a row the conversion leaves '
+    + 'as stored reports there as already on protocol.',
   acceptanceCriteria:
     '`ElementDataSourceSchema.safeParse({ object, filter: [{ field: \'status\', operator: '
     + '\'equals\', value: \'active\' }] })` succeeds and the parsed `filter` is the same rule '
 
@@ -48,13 +48,17 @@ export const entry: SemanticMigration = {
     + 'outright — the other arm the finding offered — removes an accepted shape and needs its '
     + 'own ruling; the deprecation already stated in the description is unchanged and still '
     + 'says to prefer filter. '
-    + 'Metadata AT REST is deliberately NOT rewritten and this entry adds no D2 conversion, '
-    + 'for the reason its sibling gives at length: a SemanticMigration converts nothing by '
-    + 'its own type, the stored-row pass replays D2 conversions only, and the read path does '
-    + 'not re-validate stored rows — so a stored page carrying the record form keeps loading '
-    + 'and keeps rendering as it does today. What changes is that RE-SAVING it is refused at '
-    + 'the defaultFilters path, with the same conversion table the filter door gives, '
-    + 'computed from the author\'s own keys. ADR-0049 / ADR-0087.',
+    + 'Metadata AT REST: the record form and the AST tuple array at this key are rewritten to '
+    + 'the rule array by the same D2 conversion as its sibling filter, '
+    + 'page-component-filter-record-to-rule-array, wherever the mapping is lossless — by '
+    + 'os migrate meta --stored, and on every stored-row read until it runs. What it cannot '
+    + 'map losslessly is left exactly as stored and keeps rendering as it does today — a '
+    + 'combinator, a null value, an operator the rule vocabulary does not spell, the bare '
+    + 'string or number this key also took, and any filter on a grid whose rows are inline '
+    + '(data with provider value, or staticData), for the reason its sibling gives — and '
+    + 'RE-SAVING such a node is refused at the '
+    + 'defaultFilters path, with the same conversion table the filter door gives, computed '
+    + 'from the author\'s own keys. ADR-0049 / ADR-0087.',
   acceptanceCriteria:
     'Every object-grid node in your pages either omits defaultFilters or carries a '
     + 'ViewFilterRule array on it. The parse of an object-grid node whose defaultFilters is '
 
@@ -5279,7 +5279,18 @@ const step18: MigrationStep = {
     + 'door persists the authored value and the stored-row rehydration seam is live for '
     + 'this type, both measured); and the withdrawn `ConnectorProviderContext` member, '
     + 'which is code and has no authored source to rewrite, leaves via the paired semantic '
-    + 'entry instead.',
+    + 'entry instead. '
+    + 'Finally it gives the one-filter-orthography convergence (objectui#6206) its '
+    + 'mechanical half at rest (#17321, ruling B): the D2 conversion '
+    + '`page-component-filter-record-to-rule-array` rewrites a record-form or single-level '
+    + 'AST `filter` at the converged rule-array doors — `dataSource.filter`, the '
+    + '`object-*` / `element:number` / `element:record_picker` `filter` props and '
+    + '`object-grid.defaultFilters` — to the rule array wherever the mapping is lossless, '
+    + 'and leaves a filter carrying `$and` / `$or` / `$not` (or any part with no lossless '
+    + 'rule spelling) exactly as stored, because flattening a combinator changes which rows '
+    + 'a page selects — as it does every filter of a component whose rows are inline, which '
+    + 'the renderer matches in the record dialect and would empty for a rule array. It is retired from the load path, so authors are still refused at '
+    + 'the door and taught the array; the stored-row seams and this chain replay it.',
   conversionIds: [
     'field-malformed-scale-precision-removed',
     'record-chatter-position-vocabulary',
@@ -5315,6 +5326,7 @@ const step18: MigrationStep = {
     'dashboard-widget-chart-config-structure-removed',
     'translation-per-app-settings-removed',
     'object-tenancy-organization-field-removed',
+    'page-component-filter-record-to-rule-array',
   ],
   semantic: [
     // One file per entry under `entries/semantic/`, concatenated here sorted by
@@ -7863,15 +7875,29 @@ const step18: MigrationStep = {
         + 'array on `object-grid`) and three lint fixtures — every one rewritten to the rule array '
         + 'in the same change, and zero outside those files; this entry carries the prescription '
         + 'for authors outside the repo. '
-        + '⚠️ Metadata AT REST is deliberately NOT rewritten, and this disposition adds no D2 '
-        + 'conversion — a SemanticMigration converts nothing by its own type, and '
-        + '`os migrate meta --stored` (the pass over a deployment\'s `sys_metadata` rows) replays '
-        + 'D2 conversions only, so it has nothing to rewrite for this shape. The read path '
-        + 'does not re-validate stored rows '
-        + '(`applyConversionsToStoredItem` replays the full chain without validating, by its own '
-        + 'contract), so a stored page or block carrying the record form keeps loading unchanged '
-        + 'and is still rendered by objectui at the pinned `.objectui-sha`; what changes is that '
-        + 'RE-SAVING it is refused at the `filter` door, on its next save and not before.',
+        + 'Metadata AT REST: the mappable part of the table above is a D2 conversion, '
+        + '`page-component-filter-record-to-rule-array` (#17321, ruling B), so '
+        + '`os migrate meta --stored` (the pass over a deployment\'s `sys_metadata` rows) rewrites '
+        + 'a stored page whose `filter` is a flat record, an operator object whose operators the '
+        + 'rule vocabulary spells, several such keys, or a single-level AST tuple array, and every '
+        + 'stored-row read replays the same rewrite until it does. It is retired from the load '
+        + 'path: an author writing the record form is still refused at the `filter` door. ⚠️ A '
+        + 'filter carrying `$and` / `$or` / `$not` is left exactly as stored — the rule array '
+        + 'only ANDs, and flattening a combinator changes which rows the page selects — and so is '
+        + 'any filter with a part that has no lossless rule spelling: a `null` value (the renderer '
+        + 'skips that key, so it constrains nothing today, where a rule would test IS NULL), an '
+        + 'operator such as `$null` / `$exists` or an AST `like`, an array or object comparand in '
+        + 'equality position, or an AST `and` / `or` group. So is every filter — the binding\'s '
+        + 'included — of a component whose rows are INLINE (`data: { provider: \'value\' }`, a '
+        + '`data` array, or `staticData`): at the pinned `.objectui-sha` the `object-map`, '
+        + '`object-tree`, `object-calendar` and `object-gantt` blocks match that filter against '
+        + 'their own rows in an in-memory data source that reads the record form and excludes '
+        + 'EVERY row for a rule array, so a rewrite there would empty the block. Such a row keeps loading unchanged '
+        + '(`applyConversionsToStoredItem` replays the chain without validating, by its own '
+        + 'contract) and is refused at the `filter` door on its next save — for a combinator '
+        + 'record, a refusal that names the combinator and says why no rule spells it. '
+        + '`os migrate meta --stored` does not list these rows yet: a row the conversion leaves '
+        + 'as stored reports there as already on protocol.',
       acceptanceCriteria:
         '`ElementDataSourceSchema.safeParse({ object, filter: [{ field: \'status\', operator: '
         + '\'equals\', value: \'active\' }] })` succeeds and the parsed `filter` is the same rule '
@@ -10900,13 +10926,17 @@ const step18: MigrationStep = {
         + 'outright — the other arm the finding offered — removes an accepted shape and needs its '
         + 'own ruling; the deprecation already stated in the description is unchanged and still '
         + 'says to prefer filter. '
-        + 'Metadata AT REST is deliberately NOT rewritten and this entry adds no D2 conversion, '
-        + 'for the reason its sibling gives at length: a SemanticMigration converts nothing by '
-        + 'its own type, the stored-row pass replays D2 conversions only, and the read path does '
-        + 'not re-validate stored rows — so a stored page carrying the record form keeps loading '
-        + 'and keeps rendering as it does today. What changes is that RE-SAVING it is refused at '
-        + 'the defaultFilters path, with the same conversion table the filter door gives, '
-        + 'computed from the author\'s own keys. ADR-0049 / ADR-0087.',
+        + 'Metadata AT REST: the record form and the AST tuple array at this key are rewritten to '
+        + 'the rule array by the same D2 conversion as its sibling filter, '
+        + 'page-component-filter-record-to-rule-array, wherever the mapping is lossless — by '
+        + 'os migrate meta --stored, and on every stored-row read until it runs. What it cannot '
+        + 'map losslessly is left exactly as stored and keeps rendering as it does today — a '
+        + 'combinator, a null value, an operator the rule vocabulary does not spell, the bare '
+        + 'string or number this key also took, and any filter on a grid whose rows are inline '
+        + '(data with provider value, or staticData), for the reason its sibling gives — and '
+        + 'RE-SAVING such a node is refused at the '
+        + 'defaultFilters path, with the same conversion table the filter door gives, computed '
+        + 'from the author\'s own keys. ADR-0049 / ADR-0087.',
       acceptanceCriteria:
         'Every object-grid node in your pages either omits defaultFilters or carries a '
         + 'ViewFilterRule array on it. The parse of an object-grid node whose defaultFilters is '
 
@@ -160,6 +160,46 @@ describe('§1 the record form is refused WITH the new spelling', () => {
     );
   });
 
+  // A combinator-carrying record is exactly what the D2 conversion
+  // `page-component-filter-record-to-rule-array` leaves at rest, so it is what
+  // still meets this door on its next save. The worked rewrite used to render
+  // the combinator as a field — `{ field: '$or', operator: …, value: … }` — a
+  // "fix" that is no fix.
+  it('a lone combinator is not rendered as a field, and the refusal says why no rule spells it', () => {
+    const issue = filterIssue(
+      ElementDataSourceSchema.safeParse({
+        object: 'task',
+        filter: { $or: [{ status: 'open' }, { status: 'blocked' }] },
+      }),
+    );
+    expect(issue.code).toBe('invalid_type');
+    expect(issue.message).not.toContain("field: '$or'");
+    expect(issue.message).toContain('`$or` is a combinator, not a field, and the rule array has no spelling for it');
+    expect(issue.message).toContain('flattening one changes which rows the filter selects');
+    expect(issue.message).toContain('decide which rows this filter should select');
+    expect(issue.message).toContain('migration `element-data-source-and-object-block-filter-rule-array`');
+    // No worked rewrite at all: "this filter becomes `[]`" would read as "no filter".
+    expect(issue.message).not.toContain('becomes `[]`');
+    expect(issue.message).not.toContain('Write one rule per record key');
+  });
+
+  it('beside field keys, the rewrite covers only the field keys and every combinator is named', () => {
+    const issue = filterIssue(
+      ElementDataSourceSchema.safeParse({
+        object: 'task',
+        filter: { owner: 'me', $and: [{ a: 1 }], $not: { b: 2 } },
+      }),
+    );
+    expect(issue.code).toBe('invalid_type');
+    expect(issue.message).toContain(
+      "Write one rule per field key — they AND — so its field keys become "
+      + "`[{ field: 'owner', operator: 'equals', value: 'me' }]`.",
+    );
+    expect(issue.message).toContain('`$and` and `$not` are combinators, not fields');
+    expect(issue.message).not.toContain("field: '$and'");
+    expect(issue.message).not.toContain("field: '$not'");
+  });
+
   it('an operator-object value is not mis-prescribed as an `equals` scalar', () => {
     const issue = filterIssue(
       ElementDataSourceSchema.safeParse({ object: 'task', filter: { amount: { $gt: 100 } } }),