@@ -0,0 +1,25 @@
+---
+'@objectstack/spec': patch
+---
+
+fix(spec): `os migrate meta` guidance for the `datasource-*`, `filter-*`, `action-*`, `data-*` and `element-*` migration entries states each lesson in words instead of citing tracker numbers
+
+Clause-②: no
+
+The ADR-0087 semantic entries of the `datasource-*` family (the publish-time credential,
+placeholder and URL refusals, and the bound-secret pairs a mongo datasource cannot use),
+the `filter-*` family (the retired `$regex`, the `$between` endpoint refusals and the
+comparand shapes the save door now refuses), the `action-*` family (the retired
+descriptor key, the `resumeAuthority` default flip, the action-session rename, the bulk
+dispatch contract and the engine facade's query envelope), the `data-*` family (the
+retired driver and engine contract members, the retired field-changed event and two
+duration keys renamed with their unit) and the `element-*` family (the filter rule array
+at the page binding and the element and block doors) are printed by `os migrate meta` as
+the header, `why:` and `verify:` lines of a manual change. Their text sent the reader to
+issue-tracker, decision-batch and ruling-record numbers — some of which no longer
+resolve, and some in other repositories — for what a ruling, measurement or fix had
+decided; it now says what was decided, in the sentence being read. ADR ids are kept.
+
+Text only: no entry id, `surface`, `from` / `to`, conversion or matching logic changes,
+and the chain rewrites exactly what it rewrote before. The generated migration registry,
+`spec-changes.json` and the protocol upgrade guide carry the same text.
@@ -3,8 +3,8 @@
 /**
  * `os migrate meta` — the guidance it prints for the ADR-0087 semantic entries
  * of the COVERED families (`engine-*`, `ui-*`, `plugin-*`, `driver-*`,
- * `kernel-*`, `system-*`) states each lesson in words and carries no tracker
- * number.
+ * `kernel-*`, `system-*`, `datasource-*`, `filter-*`, `action-*`, `data-*`,
+ * `element-*`) states each lesson in words and carries no tracker number.
  *
  * ## What this pins
  *
@@ -73,26 +73,62 @@ const TSX = resolve(HERE, '../../../node_modules/.bin/tsx');
 const TRACKER_ID = /#\d{4,5}\b/;
 
 /** The families this pin holds, selected by entry-id prefix. */
-const COVERED_PREFIXES = ['engine-', 'ui-', 'plugin-', 'driver-', 'kernel-', 'system-'];
+const COVERED_PREFIXES = [
+  'engine-', 'ui-', 'plugin-', 'driver-', 'kernel-', 'system-',
+  'datasource-', 'filter-', 'action-', 'data-', 'element-',
+];
 
 /**
  * The entries rewritten when each family was brought to this line — the
  * anti-vacuity floor. A covered entry that carried no tracker id to begin with
  * is held by its prefix and needs no row here.
  */
 const REWRITTEN = [
+  'action-bulk-dispatch-contract-undeclared',
+  'action-descriptor-is-async-retired',
+  'action-descriptor-resume-authority-default-flip',
+  'action-engine-facade-find-query-envelope',
+  'action-session-roles-to-positions',
+  'data-driver-find-stream-retired',
+  'data-driver-query-omit-object',
+  'data-engine-batch-retired',
+  'data-field-changed-event-retired',
+  'data-file-value-duration-unit-in-key',
+  'data-nosql-query-options-timeout-unit-in-key',
+  'datasource-config-inline-credential-refused',
+  'datasource-config-mongo-options-credential-refused',
+  'datasource-config-placeholder-refused',
+  'datasource-config-postgres-url-unparseable-refused',
+  'datasource-config-url-query-credential-refused',
+  'datasource-config-url-userinfo-refused',
+  'datasource-credentialsref-mongo-composed-no-username-refused',
+  'datasource-credentialsref-mongo-url-no-user-refused',
   'driver-aggregate-undeclared-key-aliases-removed',
   'driver-capabilities-inert-bits-removed',
   'driver-options-timeout-to-timeout-ms',
   'driver-sql-distinct-bare-filter-typed',
   'driver-sql-unresolvable-where-column-refused',
   'driver-sql-upsert-cross-row-identity-merge-refused',
   'driver-turso-config-local-path-wasm-retired',
+  'element-data-source-and-object-block-filter-rule-array',
+  'element-number-filter-rule-array',
+  'element-record-picker-filter-rule-array',
   'engine-dotted-filter-refused',
   'engine-dotted-projection-refused',
   'engine-find-formula-filter-refused',
   'engine-find-formula-order-by-refused',
   'engine-update-upsert-retired',
+  'filter-between-blank-endpoint-refused',
+  'filter-between-field-reference-endpoint-refused',
+  'filter-comparand-types-and-widget-nested-slots-refused-at-save',
+  'filter-equality-array-comparand-refused',
+  'filter-equality-array-comparand-refused-at-save',
+  'filter-icontains-comparand-refused-at-parse',
+  'filter-ne-array-comparand-refused',
+  'filter-preset-ordering-comparand-refused',
+  'filter-query-face-comparands-refused-at-save',
+  'filter-regex-options-retired',
+  'filter-text-operator-declared-type-refused',
   'kernel-compatibility-matrix-estimated-migration-time-unit-in-key',
   'kernel-context-preview-mode-retired',
   'kernel-event-bus-retention-unit-in-key',
 
@@ -23,30 +23,32 @@ export const entry: SemanticMigration = {
     + 'also took — becomes `[{ field: \'owner_id\', operator: \'equals\', value: '
     + '\'{current_user_id}\' }]`; the value placeholders and date macros are unchanged. Legacy '
     + 'operator shorthands (`eq`, `ne`, `gt`, `notIn`, …) are accepted and normalized on parse. '
-    + 'The dashboard widget `filter` (`dashboard.zod.ts`) is a different family and is not moved '
-    + 'by this entry (#15829); `object-grid.defaultFilters` is a different key and is not named '
+    + 'The dashboard widget `filter` (`dashboard.zod.ts`) is a different family, judged on its '
+    + 'own, and is not moved by this entry; `object-grid.defaultFilters` is a different key and is not named '
     + 'by the ruling this entry records.',
   reason:
-    'One filter orthography platform-wide (objectui#6206, maintainer batch adjudication '
-    + '2026-08-25, verbatim 「同意」, Option B) reached two more locations the ComponentPropsMap '
-    + 'census could not see (#15442 anchor, #15449 member; decision batch #55, 2026-09-06, '
-    + 'verbatim 「同意」, option A: converge family-wide, one entry). The binding-level '
+    'One filter orthography platform-wide (the maintainer\'s 2026-08-25 ruling, option B: a '
+    + 'filter door takes the `ViewFilterRule` array rather than keeping a record-shaped '
+    + 'exception every author and AI would have to remember) reached two more locations the '
+    + 'ComponentPropsMap census could not see (ruled 2026-09-06, option A: converge the binding '
+    + 'and the four block doors family-wide, under one entry, rather than record an exception). The binding-level '
     + '`dataSource.filter` alone still said `FilterConditionSchema`: it refused the array the '
     + 'consumer\'s own pins author at that key, and `element:record_picker` carried two '
     + 'orthographies at two keys (`properties.filter` the rule array, `dataSource.filter` the '
     + 'record) resolved through one `??` in the renderer — the shape in which a dropped or '
     + 'misread filter returns the wrong rows without an error. The four `object-*` doors said '
-    + '`z.unknown()`: a read-point record derived from the renderers on 2026-08-13 (#7751), '
+    + '`z.unknown()`: a read-point record derived from the renderers on 2026-08-13, when the '
+    + '`object-*` blocks first got props schemas in the map, '
     + 'twelve days before the ruling, not an exception to it — so an author following the '
     + 'showcase wrote the record and an author following the manifest wrote an array, and each '
     + 'got a silent success receipt while the html tier already declared `array` for the grid '
     + 'and the metric. The record\'s `$and` / `$or` / `$not` keys were misread by every gate '
-    + 'block anyway (objectui#6948), so the exception would have preserved a capability the '
+    + 'block anyway (the console\'s filter converter had no branch for them), so the exception would have preserved a capability the '
     + 'consumer does not honour. Sequenced measurement-first, as the family had to be: at the '
     + 'objectui pin `a472b07` the `object-metric` aggregate path posted an array `where` that '
-    + '`POST /analytics/query` refused with 400 on every array form (#15828), so the converge '
-    + 'was parked behind the pin bump #16626; at the pin this repo builds against (`53ded82b`, '
-    + 'objectui#7754) the adapter lowers an authored array through `translateFilterArray` and '
+    + '`POST /analytics/query` refused with 400 on every array form, so the converge '
+    + 'was parked behind a bump of that pin; at the pin this repo builds against (`53ded82b`) '
+    + 'the adapter lowers an authored array through `translateFilterArray` and '
     + 'the spec\'s own `parseFilterAST` sink before the wire, `ObjectGrid.tsx` lowers a rule '
     + 'array through `toFilterNode`, `ObjectKanban.tsx` / `ObjectCalendar.tsx` hand it verbatim '
     + 'to `$filter` where `convertQueryParams` lowers it, and the binding\'s composition seam '
@@ -58,7 +60,9 @@ export const entry: SemanticMigration = {
     + 'in the same change, and zero outside those files; this entry carries the prescription '
     + 'for authors outside the repo. '
     + '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 '
+    + '`page-component-filter-record-to-rule-array` (ruled 2026-09-12, option B: convert what '
+    + 'maps losslessly and name what does not, rather than leave every stored row to its next '
+    + 'save or flatten combinators), 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 '
@@ -95,7 +99,8 @@ export const entry: SemanticMigration = {
     + 'a record-form `filter: { status: \'active\' }` is refused at the `filter` path of all '
     + 'five doors (`invalid_type`, expected array), and an AST tuple array is refused at '
     + '`filter.0` (expected object). No `filter` door in `ComponentPropsMap` accepts the '
-    + 'record any more (the twin of the #14406 census pin). At runtime each block and the '
+    + 'record any more (the twin of the census pin that asks whether any `filter` door still '
+    + 'refuses the array). At runtime each block and the '
     + 'binding select exactly the rows the array selects — the same filter a list view '
     + 'renders — including the `object-metric` aggregate tile, whose analytics `where` is the '
     + 'lowered condition. Downstream (objectui, after a released spec version reaches the '
 
@@ -17,27 +17,32 @@ export const entry: SemanticMigration = {
     + 'several rules (they AND). Legacy operator shorthands (`eq`, `gt`, `notIn`, …) are '
     + 'accepted and normalized on parse',
   reason:
-    'One filter orthography platform-wide (objectui#6206, maintainer batch adjudication '
-    + "2026-08-25, verbatim 「同意」, Option B). `ComponentPropsMap['element:number'].filter` "
+    'One filter orthography platform-wide (the maintainer\'s 2026-08-25 ruling, option B: '
+    + 'align the element to the `ViewFilterRule` array rather than keep it the record-shaped '
+    + "exception). `ComponentPropsMap['element:number'].filter` "
     + 'was the one `filter` input in the map declared as the MongoDB-style record '
     + '(`FilterConditionSchema`) while its siblings declared the `ViewFilterRule` array, so '
     + 'the filter a list view stores and renders was refused by the KPI element beside it, '
     + 'and the objectui parity gate had to carry a reasoned exemption to look away. The '
     + 'convergence was sequenced consumer-first (ruling recorded 2026-08-25, Option A): '
-    + 'objectui#6828 made `ObjectStackAdapter.aggregate()` run the same `translateFilterArray` '
+    + 'the console adapter was changed so `ObjectStackAdapter.aggregate()` runs the same '
+    + '`translateFilterArray` '
     + 'its `find()` path runs, and the objectui pin carrying it was re-measured before this '
-    + 'entry moved — but that measurement named the wrong hop, and #15828 corrects it here. '
+    + 'entry moved — but that measurement named the wrong hop, and the runtime route\'s refusal '
+    + 'of the array corrects it here. '
     + '`translateFilterArray` yields AST tuples, which are still a `FilterArray` — input-only '
     + 'sugar — so the real path is: authored array → `translateFilterArray` → lowered by '
     + '`parseFilterAST` (`@objectstack/spec/data`, the single sink the `FilterArray` docblock '
-    + 'names, #5158 ruling C) in the adapter, BEFORE the wire → a `FilterCondition` on the '
+    + 'names, since the maintainer\'s 2026-08-04 ruling C declared the array input-only sugar '
+    + 'with one lowering seam) in the adapter, BEFORE the wire → a `FilterCondition` on the '
     + 'body. The hop that decides it is the runtime route `POST /analytics/query`, which '
     + 'parses `where` with `AnalyticsQueryRequestSchema` — a `FilterCondition` and nothing '
     + 'else — so an un-lowered array is refused there before any service code runs. '
     + '`lowerAnalyticsWhere` (`service-analytics`), where that earlier measurement stopped, '
-    + 'is the IN-PROCESS door (#5334) for callers reaching `analyticsService.query` '
+    + 'is the IN-PROCESS door (added when an array `where` was found silently dropped on the '
+    + 'analytics path) for callers reaching `analyticsService.query` '
     + "directly, not the wire's; it too still refuses a RAW rule-object array by design. "
-    + 'objectui#7752 lands the adapter-side lowering. '
+    + 'The adapter-side lowering lands in the console\'s own repository. '
     + 'The ruled migration check ran with the change: the '
     + 'sweep of first-party corpora (examples/, skills/, create-objectstack, content/docs/, '
     + 'packages/apps/, spec fixtures) found ONE `element:number` author writing a record-form '
@@ -53,5 +58,5 @@ export const entry: SemanticMigration = {
     + 'filter a list view renders. Downstream (objectui, after a released spec version reaches '
     + "the pin): the `element:number.filter:array` entry in `OFF_SPEC_ARM_EXEMPTIONS` "
     + '(`registry-inputs-spec-parity.test.ts`) becomes deletable, which is what closes '
-    + 'objectui#6206.',
+    + 'the console-side half of this convergence.',
 };
@@ -11,24 +11,26 @@ export const entry: SemanticMigration = {
     '`z.array(ViewFilterRuleSchema)` — the rule array `[{ field, operator, value }, ...]` '
     + "the map's array-declared `filter` doors already carry (`record:related_list`, its nested "
     + 'Add-affordance picker, `element:number`; the four `object-*` blocks declare `filter` as '
-    + '`z.unknown()`, #15449). A record-form filter '
+    + '`z.unknown()`, a gap measured on its own). A record-form filter '
     + "`{ status: 'active' }` becomes `[{ field: 'status', operator: 'equals', value: 'active' }]`; "
     + "an operator object `{ amount: { $gt: 100 } }` becomes "
     + "`[{ field: 'amount', operator: 'greater_than', value: 100 }]`; several keys become "
     + 'several rules (they AND). Legacy operator shorthands (`eq`, `gt`, `notIn`, …) are '
     + 'accepted and normalized on parse. The binding-level `dataSource.filter` on the same node '
     + 'is a different key (`ElementDataSourceSchema`) and is not moved by this entry',
   reason:
-    'One filter orthography platform-wide (objectui#6206, maintainer batch adjudication '
-    + "2026-08-25, verbatim 「同意」, Option B). `ComponentPropsMap['element:record_picker'].filter` "
+    'One filter orthography platform-wide (the maintainer\'s 2026-08-25 ruling, option B: '
+    + 'every `filter` door takes the `ViewFilterRule` array rather than keeping record-shaped '
+    + "exceptions). `ComponentPropsMap['element:record_picker'].filter` "
     + 'was the LAST `filter` input in the map still declared as the MongoDB-style record '
-    + '(`FilterConditionSchema`) after `element:number` converged (#12039 Key 2): the three '
+    + '(`FilterConditionSchema`) after `element:number` converged: the three '
     + 'array-declared doors (`record:related_list`, its nested Add-affordance picker, '
     + '`element:number`) carried the `ViewFilterRule` array and the four `object-*` doors '
-    + 'declare `z.unknown()` (#15449), so the filter a list view stores and renders was refused '
+    + 'declare `z.unknown()`, so the filter a list view stores and renders was refused '
     + 'by the picker beside them, and a lone holdout is the state where the next author copies '
     + 'the wrong form. Sequenced measurement-first, as that convergence had to be (the 2026-08-25 '
-    + 'Option-A ordering ruling, #14406): at the objectui pin `00d3f09c` the renderer hands '
+    + 'Option-A ordering ruling: measure the consumer\'s read path before the contract moves): '
+    + 'at the objectui pin `00d3f09c` the renderer hands '
     + '`filter` to `query.$filter` and calls `adapter.find()` '
     + '(`components/src/renderers/basic/record-picker.tsx`); `ObjectStackAdapter.convertQueryParams` '
     + 'lowers an ARRAY `$filter` through `translateFilterArray` into filter AST tuples '
@@ -50,5 +52,5 @@ export const entry: SemanticMigration = {
     + "a released spec version reaches the pin): the registry's `inputs.filter` entry for "
     + "`element:record_picker` (`type: 'object'`, `record-picker.tsx`) flips to the array arm and "
     + 'the `record-picker-inputs-spec-parity.test.ts` pins that assert the record form follow — '
-    + 'objectui#7663, filed from #14406 with a Blocked-by line.',
+    + 'a console-side change filed in the objectui repository, blocked on that release.',
 };