docs(spec): dated addendum — MySQL joined the unresolvable-column refusal AND the #3821 recoveries (#9060)

The ADR-0087 entry driver-sql-unresolvable-where-column-refused stated MySQL
was outside the refusal's reach. True at registration (#8790); false since
#8926 landed via PR #9061. The historical paragraph is kept verbatim as the
state at registration and a dated addendum states both halves of the parity:
the INVALID_FILTER / 400 envelope, and the #3821 projection / ORDER-BY
recoveries MySQL never had. registry.ts regenerated via gen:migration-registry.

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

Author: claude

.changeset/spec-unresolvable-column-mysql-reach-addendum.md

@@ -0,0 +1,34 @@
+---
+"@objectstack/spec": patch
+---
+
+docs(spec): the `driver-sql-unresolvable-where-column-refused` ledger entry states MySQL's reach as it is after #8926, not as it was at registration (#9060)
+
+Text amendment to an already-registered ADR-0087 entry — the entry id, `surface`
+and `replacement` prescription are unchanged, and no accept/reject behaviour
+moves. What changes is the `reason`, which is upgrader-facing documentation: it
+is the data source for `objectstack migrate meta`, `spec-changes.json` and the
+generated upgrade guide.
+
+The entry's "Reach, stated rather than assumed" paragraph said MySQL was outside
+the refusal — true when #8790 registered it, false the moment #8926 merged (PR
+#9061). A MySQL user reading "on MySQL this condition still travels out as the
+raw dialect error" would have concluded the migration did not apply to them,
+which is exactly wrong after parity.
+
+The historical paragraph is kept verbatim as the state at registration, and a
+dated addendum states both halves of what the one shared predicate did on MySQL:
+
+- **The envelope** — an unresolvable WHERE column refuses with the same
+  `INVALID_FILTER` / 400 naming the column, instead of the raw
+  `ER_BAD_FIELD_ERROR` with the statement's bound literals inlined.
+- **The recoveries** — MySQL also gained the #3821 projection and ORDER-BY
+  recoveries it never had, so those positions now return recovered rows where
+  they used to throw.
+
+Both arrive together because `ER_BAD_FIELD_ERROR` spells every clause position
+with one sentence, so all three ride one arm of the predicate — pinned as the
+ruled direction by the widened sweep in
+`sql-driver-unresolvable-where-column-refusal.test.ts`. Unchanged by that
+ruling, and said so in the addendum: a dotted filter key is still classified per
+dialect, the axis #8371 owns.

packages/spec/src/migrations/entries/semantic/18.driver-sql-unresolvable-where-column-refused.ts

@@ -51,6 +51,30 @@ export const entry: SemanticMigration = {
     + 'matches, so on MySQL this condition still travels out as the raw dialect error; '
     + 'widening that predicate would also hand MySQL the #3821 recoveries it has never had, '
     + 'which is an accept-set change in the opposite direction and is filed separately.\n\n'
+    + 'Addendum 2026-08-16 (#8926, landed by PR #9061). The paragraph above is kept as the '
+    + 'state at registration; this amends it. MySQL joined the one shared predicate, so the '
+    + 'reach is now all three dialects this driver speaks, and a MySQL reader must NOT '
+    + 'conclude the migration does not apply — it applies exactly as it does on SQLite and '
+    + 'Postgres. Because that predicate serves both consumers at once, the accept set moved '
+    + "in BOTH directions on MySQL in one line, and both halves were ruled together (option "
+    + 'A, maintainer, 2026-08-16; a split predicate — the envelope while withholding the '
+    + 'recoveries — was considered and refused). (1) THE ENVELOPE: an unresolvable WHERE '
+    + 'column now refuses with the same `INVALID_FILTER` / 400 naming the column, instead of '
+    + "travelling out as the raw `ER_BAD_FIELD_ERROR` with the statement's bound literals "
+    + 'inlined — the #7929 disclosure shape closed on the last dialect that still had it. '
+    + '(2) THE RECOVERIES: MySQL also gained the #3821 projection and ORDER-BY recoveries it '
+    + 'had never had, so an unresolvable column in a projection or an ORDER BY now returns '
+    + 'recovered rows where it used to throw. The two halves arrive together because '
+    + '`ER_BAD_FIELD_ERROR` spells every clause position with one sentence — '
+    + "`Unknown column 'x' in 'where clause'` / `'field list'` / `'order clause'` — so all "
+    + 'three ride one arm of the predicate; that is pinned as the ruled direction by the '
+    + 'widened predicate sweep in `sql-driver-unresolvable-where-column-refusal.test.ts`. '
+    + 'The widening can never drop a predicate: every ladder rung is rebuilt from '
+    + '`buildBase()`, which unconditionally re-applies `query.where`. Unchanged by the '
+    + 'ruling: a DOTTED filter key is still classified per dialect (Postgres raises '
+    + 'undefined_table, which neither arm matches), the axis #8371 owns. The entry id, '
+    + 'surface and prescription are unchanged — this is a text amendment, not a new '
+    + 'migration.\n\n'
     + 'This is a CODE-path API, not stored metadata, so — like '
     + '`engine-dotted-projection-refused` and `engine-find-formula-filter-refused` — there '
     + 'is no `sys_metadata` row for the D2 chain to rewrite and this entry is the '

packages/spec/src/migrations/registry.ts

@@ -5118,6 +5118,30 @@ const step18: MigrationStep = {
         + 'matches, so on MySQL this condition still travels out as the raw dialect error; '
         + 'widening that predicate would also hand MySQL the #3821 recoveries it has never had, '
         + 'which is an accept-set change in the opposite direction and is filed separately.\n\n'
+        + 'Addendum 2026-08-16 (#8926, landed by PR #9061). The paragraph above is kept as the '
+        + 'state at registration; this amends it. MySQL joined the one shared predicate, so the '
+        + 'reach is now all three dialects this driver speaks, and a MySQL reader must NOT '
+        + 'conclude the migration does not apply — it applies exactly as it does on SQLite and '
+        + 'Postgres. Because that predicate serves both consumers at once, the accept set moved '
+        + "in BOTH directions on MySQL in one line, and both halves were ruled together (option "
+        + 'A, maintainer, 2026-08-16; a split predicate — the envelope while withholding the '
+        + 'recoveries — was considered and refused). (1) THE ENVELOPE: an unresolvable WHERE '
+        + 'column now refuses with the same `INVALID_FILTER` / 400 naming the column, instead of '
+        + "travelling out as the raw `ER_BAD_FIELD_ERROR` with the statement's bound literals "
+        + 'inlined — the #7929 disclosure shape closed on the last dialect that still had it. '
+        + '(2) THE RECOVERIES: MySQL also gained the #3821 projection and ORDER-BY recoveries it '
+        + 'had never had, so an unresolvable column in a projection or an ORDER BY now returns '
+        + 'recovered rows where it used to throw. The two halves arrive together because '
+        + '`ER_BAD_FIELD_ERROR` spells every clause position with one sentence — '
+        + "`Unknown column 'x' in 'where clause'` / `'field list'` / `'order clause'` — so all "
+        + 'three ride one arm of the predicate; that is pinned as the ruled direction by the '
+        + 'widened predicate sweep in `sql-driver-unresolvable-where-column-refusal.test.ts`. '
+        + 'The widening can never drop a predicate: every ladder rung is rebuilt from '
+        + '`buildBase()`, which unconditionally re-applies `query.where`. Unchanged by the '
+        + 'ruling: a DOTTED filter key is still classified per dialect (Postgres raises '
+        + 'undefined_table, which neither arm matches), the axis #8371 owns. The entry id, '
+        + 'surface and prescription are unchanged — this is a text amendment, not a new '
+        + 'migration.\n\n'
         + 'This is a CODE-path API, not stored metadata, so — like '
         + '`engine-dotted-projection-refused` and `engine-find-formula-filter-refused` — there '
         + 'is no `sys_metadata` row for the D2 chain to rewrite and this entry is the '