@@ -0,0 +1,33 @@
+---
+'@objectstack/spec': patch
+---
+
+fix(spec): the `filter-text-operator-declared-type-refused` migration entry's control no longer counts JSON-stored fields, and it names the separate door that refuses text operators there
+
+Clause-②: no
+
+**`filter-text-operator-declared-type-refused` (protocol 18).** The entry's acceptance criteria
+named every text-valued field, `multiselect` / `checkboxes` / `tags` and lookup and `user` ids
+included, as the control that "must keep answering exactly as before". The declared-type door this
+entry registers still leaves every text-valued type alone. A second door, though, judges a field by
+how it is STORED: on a column stored as JSON it now refuses `$startsWith`, `$endsWith`,
+`$icontains`, `$like` and `$ilike` with `INVALID_FILTER` / `400`, as it already refused the scalar
+comparisons there. So a stored filter that uses one of those operators on a multi-valued field
+answers that `400` after the upgrade, and the old sentence called it a control.
+
+The criteria now say four things:
+
+- The control is a text-valued field that is NOT stored as a JSON column.
+- The JSON-stored population is `multiselect` / `checkboxes` / `tags`, any field declared
+  `multiple: true` (a multi-valued lookup or `user` among them), and, on a SQL deployment still
+  inside the ADR-0104 dual-encoding window, a single-value file-class field.
+- That door refuses every text operator except the membership pair `$contains` / `$notContains`,
+  and its refusal names no declared type, so it is outside this entry's repair list.
+- The repair on a multi-valued field is membership: `$contains` for one member, an `$or` of
+  `$contains` for any-of. A single-value file-class field answers text operators again once the
+  deployment finishes the media-column move (the column step of
+  `objectstack migrate files-to-references --apply`).
+
+Text only: no entry id, `surface`, `replacement`, `reason`, conversion or refusal changes, and
+neither door moves. `objectstack migrate meta` prints the corrected `verify:` line, and the
+generated migration registry carries the same text.
@@ -50,12 +50,29 @@ export const entry: SemanticMigration = {
     + 'refusals — each message names the filter key, the field\'s declared type and the '
     + 'operator, which is the whole repair list. A filter re-authored onto a typed '
     + 'operator returns the rows its author meant; one left as written keeps answering '
-    + '400, and NOTHING silently rewrites it. Filters over text-valued fields — '
-    + 'including `select` / `radio` codes, `multiselect` / `checkboxes` / `tags`, lookup '
-    + 'and `user` ids, `autonumber` and the file classes — are unaffected and must keep '
-    + 'answering exactly as before; that is the control which proves a repair pass did '
-    + 'not over-reach. A DIRECT driver call bypasses this door entirely and keeps '
+    + '400, and NOTHING silently rewrites it. This door judges a field by its declared '
+    + 'type alone, so it never refuses a text operator over a text-valued field — '
+    + '`select` / `radio` codes, `multiselect` / `checkboxes` / `tags`, lookup and `user` '
+    + 'ids, `autonumber` and the file classes. Over every such field that is not stored '
+    + 'as a JSON column (below), filters must keep answering exactly as before; that is '
+    + 'the control which proves a repair pass did not over-reach. A DIRECT driver call '
+    + 'bypasses this door entirely and keeps '
     + 'answering the `FILTER_TEXT_CASES` stored-value row (a stored value that is not a string '
     + 'never satisfies a positive text operator and satisfies `$notContains`), so a '
-    + 'driver-level test is not evidence about this migration in either direction.',
+    + 'driver-level test is not evidence about this migration in either direction. A '
+    + 'field stored as a JSON column is NOT that control, because a separate door judges '
+    + 'it by its storage rather than its declared type: `multiselect` / `checkboxes` / '
+    + '`tags`, any field declared `multiple: true` (a multi-valued lookup or `user` among '
+    + 'them) and, on a SQL deployment still inside the ADR-0104 dual-encoding window (its '
+    + 'media columns not yet moved), a single-value file-class field. That door refuses '
+    + 'every text operator there except the membership pair `$contains` / `$notContains` '
+    + '— `$startsWith`, `$endsWith`, `$icontains`, `$like` and `$ilike`, beside the '
+    + 'scalar comparisons it already refused — with an `INVALID_FILTER` 400 that names no '
+    + 'declared type, so a stored filter left on one of those operators there answers '
+    + 'that 400 after the upgrade and is outside this entry\'s repair list. On a multi-valued field its '
+    + 'repair is membership, which no rewrite chooses either: `$contains` for one member, '
+    + 'an `$or` of `$contains` for any-of. A single-value file-class field is not a '
+    + 'membership question: it answers text operators again once its deployment finishes '
+    + 'the media-column move (the column step of `objectstack migrate files-to-references '
+    + '--apply`).',
 };
@@ -11814,14 +11814,31 @@ const step18: MigrationStep = {
         + 'refusals — each message names the filter key, the field\'s declared type and the '
         + 'operator, which is the whole repair list. A filter re-authored onto a typed '
         + 'operator returns the rows its author meant; one left as written keeps answering '
-        + '400, and NOTHING silently rewrites it. Filters over text-valued fields — '
-        + 'including `select` / `radio` codes, `multiselect` / `checkboxes` / `tags`, lookup '
-        + 'and `user` ids, `autonumber` and the file classes — are unaffected and must keep '
-        + 'answering exactly as before; that is the control which proves a repair pass did '
-        + 'not over-reach. A DIRECT driver call bypasses this door entirely and keeps '
+        + '400, and NOTHING silently rewrites it. This door judges a field by its declared '
+        + 'type alone, so it never refuses a text operator over a text-valued field — '
+        + '`select` / `radio` codes, `multiselect` / `checkboxes` / `tags`, lookup and `user` '
+        + 'ids, `autonumber` and the file classes. Over every such field that is not stored '
+        + 'as a JSON column (below), filters must keep answering exactly as before; that is '
+        + 'the control which proves a repair pass did not over-reach. A DIRECT driver call '
+        + 'bypasses this door entirely and keeps '
         + 'answering the `FILTER_TEXT_CASES` stored-value row (a stored value that is not a string '
         + 'never satisfies a positive text operator and satisfies `$notContains`), so a '
-        + 'driver-level test is not evidence about this migration in either direction.',
+        + 'driver-level test is not evidence about this migration in either direction. A '
+        + 'field stored as a JSON column is NOT that control, because a separate door judges '
+        + 'it by its storage rather than its declared type: `multiselect` / `checkboxes` / '
+        + '`tags`, any field declared `multiple: true` (a multi-valued lookup or `user` among '
+        + 'them) and, on a SQL deployment still inside the ADR-0104 dual-encoding window (its '
+        + 'media columns not yet moved), a single-value file-class field. That door refuses '
+        + 'every text operator there except the membership pair `$contains` / `$notContains` '
+        + '— `$startsWith`, `$endsWith`, `$icontains`, `$like` and `$ilike`, beside the '
+        + 'scalar comparisons it already refused — with an `INVALID_FILTER` 400 that names no '
+        + 'declared type, so a stored filter left on one of those operators there answers '
+        + 'that 400 after the upgrade and is outside this entry\'s repair list. On a multi-valued field its '
+        + 'repair is membership, which no rewrite chooses either: `$contains` for one member, '
+        + 'an `$or` of `$contains` for any-of. A single-value file-class field is not a '
+        + 'membership question: it answers text operators again once its deployment finishes '
+        + 'the media-column move (the column step of `objectstack migrate files-to-references '
+        + '--apply`).',
     },
     // The absent half of the decision-branch predicate rule. A SEPARATE entry from
     // `flow-predicate-slot-blank-string-refused` on purpose: that one keeps the