docs(driver-sql,service-analytics): repoint three comments at the moved driver-error classifier (#13555)

`schema-sync-errors.ts` moved from `@objectstack/metadata` to
`@objectstack/types` as `driver-error-classification.ts`, leaving three prose
pointers naming a path that no longer resolves. Each is a reader's trail to the
reasoning behind a driver-error verdict, so a dangling one costs the next author
the thing the comment exists to give them.

Repointed at the real current home, verified on `origin/main` rather than copied
from the move's prose, and each keeps the historical note of where it was — the
same idiom the pointers updated in the move itself already use.

Comment text only: no behaviour, no published surface, no test changed.


Claude-Session: https://claude.ai/code/session_01F3jdziLbAPGeceVNmSox5L

Co-authored-by: Claude <noreply@anthropic.com>

Author: claude[bot]

packages/drivers/driver-sql/src/sql-driver-backend-fault-envelope.test.ts

@@ -74,12 +74,14 @@
  * the platform ACCEPTS and is expressly outside this ruling.
  *
  * The predicate already follows `error.cause` four levels deep, with its own
- * pins (`schema-sync-errors.test.ts`, "follows an error wrapped as `cause`"),
- * because "drivers commonly re-throw with the original attached as `cause`" is
- * a case it was built for. So the wrap keeps the original there — and this
- * suite pins the driver's half of that contract: the cause is present, it is
- * the untouched dialect error, and it is NON-ENUMERABLE so it cannot ride back
- * onto a wire through `JSON.stringify` or a spread.
+ * pins (`packages/types/src/driver-error-classification.test.ts` — #13279
+ * moved it there from `metadata/src/utils/schema-sync-errors.test.ts` —
+ * "follows an error wrapped as `cause`"), because "drivers commonly re-throw
+ * with the original attached as `cause`" is a case it was built for. So the
+ * wrap keeps the original there — and this suite pins the driver's half of
+ * that contract: the cause is present, it is the untouched dialect error, and
+ * it is NON-ENUMERABLE so it cannot ride back onto a wire through
+ * `JSON.stringify` or a spread.
  */
 
 import { describe, it, expect, beforeAll, afterAll } from 'vitest';

packages/drivers/driver-sql/src/sql-driver.ts

@@ -813,10 +813,12 @@ function unresolvableFilterColumnError(object: string, column: string | null): E
  * platform accepts — expressly outside this ruling.
  *
  * That predicate already follows `error.cause` up to four levels, with its own
- * pins (`schema-sync-errors.test.ts`, "follows an error wrapped as `cause`"),
- * because "drivers commonly re-throw with the original attached as `cause`" is
- * a case it was built for. So the wrap is transparent to it and to every other
- * cause-following consumer, and ⛔ the predicate itself is untouched.
+ * pins (`packages/types/src/driver-error-classification.test.ts` — #13279
+ * moved it there from `metadata/src/utils/schema-sync-errors.test.ts` —
+ * "follows an error wrapped as `cause`"), because "drivers commonly re-throw
+ * with the original attached as `cause`" is a case it was built for. So the
+ * wrap is transparent to it and to every other cause-following consumer, and
+ * ⛔ the predicate itself is untouched.
  *
  * The property is defined NON-ENUMERABLE, the same shape `new Error(msg, {
  * cause })` produces. An enumerable `cause` would ride out through

packages/services/service-analytics/src/analytics-service.ts

@@ -191,8 +191,10 @@ function isMissingColumnOfRelation(message: string): boolean {
  * object "O"`, where the "relation" is inside "relationship" and the missing
  * thing is a RELATIONSHIP, not a table. The anchor is the same pattern the
  * sibling {@link missingSourceRelation} already uses for postgres (and the same
- * shape as `metadata/src/utils/schema-sync-errors.ts`), so "is something
- * missing" and "what is missing" can no longer disagree on this limb.
+ * shape as `packages/types/src/driver-error-classification.ts` — #13279
+ * moved it there from `metadata/src/utils/schema-sync-errors.ts`), so "is
+ * something missing" and "what is missing" can no longer disagree on this
+ * limb.
  *
  * MEASURED over the wordings this repo actually carries — 13 strings: the three
  * driver families' phrasings (including sql-prefixed and schema-qualified