no-mistakes(document): Docs updated for the Postgres CHECK/index probe. CHANGELOG and migrations-and-drift.md now say "anywhere" for ;, document @using refusal, and per-table 42501 fallback. Overlong lines reflowed. No unresolved gaps.

Author: dmealing

CHANGELOG.md

@@ -207,12 +207,13 @@ here.**
   The string normaliser stays, and decides, on SQLite and D1, in the offline `meta migrate`
   (which has no database), on a read-only connection or hot standby, for a role without the `TEMP`
   privilege, and for an expression that does not compile against the live columns. A probe that
-  cannot answer never reports drift or fails the command. An expression holding a `;` anywhere, or an
-  index `@using` that is not a plain access-method name, is never sent to the database; a refusal
-  for one table (such as no `SELECT` on it) does not stop the other tables being probed. `meta migrate baseline --from-db` now records the
-  generated text, not Postgres's spelling, for a CHECK or an index expression the live database
-  proves equal to the metadata's, so the offline plan after a baseline compares like with like; it
-  is best effort and writes the introspected snapshot as before if the metadata does not load.
+  cannot answer never reports drift or fails the command. An expression holding a `;` anywhere, or
+  an index `@using` that is not a plain access-method name, is never sent to the database. A refusal
+  for one table (such as no `SELECT` on it) gives that table no answer and does not stop the other
+  tables being probed. `meta migrate baseline --from-db` now records the generated text, not
+  Postgres's spelling, for a CHECK or an index expression the live database proves equal to the
+  metadata's, so the offline plan after a baseline compares like with like; it is best effort and
+  writes the introspected snapshot as before if the metadata does not load.
   `meta verify --db` also uses the probe for its committed-snapshot check. New exports from
   `@metaobjectsdev/migrate-ts`: `postgresExprCanonProbe`, `adoptGeneratedSpelling` and the
   `ExprCanonProbe` types, with a `DiffArgs.exprCanonProbe` option. Schema comparison is

docs/features/migrations-and-drift.md

@@ -392,9 +392,12 @@ Where the question cannot be asked, the comparison falls back to a **string norm
 - SQLite and D1, which store the text as written;
 - the default **offline** `meta migrate`, which diffs the committed snapshot and has no database;
 - a read-only connection or a hot standby, and a role without the `TEMP` privilege;
+- a table the role cannot read (no `SELECT` on it, or no `USAGE` on its schema): that table only,
+  the other tables are still asked;
 - an expected expression that does not compile against the live columns (the column diff reports
   that case);
-- an expression containing a `;` anywhere, quoted or not, or an index `@using` that is not a plain access-method name, which is never sent to the database.
+- an expression containing a `;` anywhere, quoted or not, or an index `@using` that is not a plain
+  access-method name: neither is ever sent to the database.
 
 The normaliser cannot tell a precedence change from a bracket-only change (it deletes every
 bracket), so on the fallback path `(a OR b) AND c` and `a OR (b AND c)` compare as equal. A fallback