changeset: state the SDK narrowing in the disposition its three siblings use

#8140 / #11925 / #12034 are the same class — a published `@objectstack/client`
return-type narrowing with no metadata surface behind it — and all three record
the no-ADR-0087-entry disposition as prose rather than as a `**BREAKING**`
declaration, which in this repo is the token that routes a change at the
metadata migration ledger. The consumer impact is stated in full (FROM/TO per
method, and the exact reads that stop compiling); what is dropped is a token
that would have claimed a ledger relevance this change does not have.

Recorded on the PR: the ADR-0087 gate has no honest disposition for a published
TYPE-surface narrowing that carries a consumer source-edit prescription and no
metadata migration — filed separately.

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

Author: claude

.changeset/client-json-erasure-in-repo-families.md

@@ -4,10 +4,10 @@
 
 fix(client): bind the five in-repo `return res.json()` methods, whose published type was `Promise< any >` (part of #12104)
 
-**BREAKING** return-type narrowing on five already-published SDK methods,
-shipped as `minor` under the repo's launch-window convention for breaking
-changes. No runtime behaviour changes — the values these methods resolve to are
-byte-identical before and after; only their DECLARED types move off `any`.
+**Return-type narrowing on a published SDK (clause-②).** No runtime change: the
+value each method resolves to is byte-identical before and after. Only the
+DECLARED type moved, off `any` — which is exactly why a runtime test cannot
+observe it and the pins for it are type-level.
 
 > ⓘ Angle brackets are spaced throughout (`Promise< any >`) on purpose —
 > GitHub's body sanitizer strips tag-shaped spans, backticks and fenced code
@@ -19,34 +19,54 @@ its published type was `Promise< any >`, inherited from `lib.dom`'s
 `Promise` nor `unwrapResponse`, which is why the class was invisible to the
 greps two earlier censuses used.
 
-FROM (all five): `Promise< any >`
-
-TO:
-
-| method | now returns | why |
-|---|---|---|
-| `analytics.query` | `BaseResponse & { data: AnalyticsResult }` | dispatcher-served; `deps.success(v)` wraps, `res.json()` strips nothing |
-| `analytics.meta` | `AnalyticsMetadataResponse` | same envelope; `data` is the bare `CubeMeta[]` projection |
-| `analytics.explain` | `AnalyticsSqlResponse` | same envelope; `data` is `{ sql, params }` |
-| `automation.trigger` | `BaseResponse & { data: AutomationResult }` | same envelope; the payload its sibling `automation.execute` unwraps |
-| `analytics.queryDataset` | `AnalyticsResult` | served by `@objectstack/rest`, which answers `res.json(result)` — no envelope |
-
-**What breaks.** Nothing that was already reading these correctly. `any`
-accepted every read, so code that treated `analytics.query(...)` as if it were
-the payload — `(await client.analytics.query(q)).rows` — compiled and was
-`undefined` at runtime; it is now a compile error naming the envelope. The
-remedy is the read the wire always required: `.data.rows`. The one method that
-moves the other way is `queryDataset`, which is served BARE — a caller reading
-`.data` off it was likewise reading `undefined`, and that read is now refused
-too.
-
-Every shape above was measured by driving the real producers (a real
-`AnalyticsService`, a real `AutomationEngine`, the real `HttpDispatcher` and the
-real `RestServer`, with only the socket stood in for), not by reading source or
-asserting against a mock.
-
-Scope: the five families whose producers live in this repo. The 38
-better-auth-backed `auth.*` / `organizations.*` / `oauth.*` methods of the same
-class are untouched and remain ledgered.
-
-<!-- adr-0087: not-required (no-migration-prescription) A TypeScript return-type narrowing on five runtime SDK methods. No authorable key, schema property or metadata shape is removed, renamed or re-shaped anywhere — `packages/spec` is untouched — so there is no tombstone and nothing mechanical for `objectstack migrate meta` to rewrite; a ledger entry would have no artifact to project into. The channel that reaches an affected caller is the compile error at their own call site, which names the envelope and is why the change is worth shipping: the remedy (`.data.rows` instead of `.rows`) is a source edit in consumer code, which no migration entry can perform on an upgrader's behalf. -->
+## What each method declares now
+
+| method | declared before | declares now | why |
+|---|---|---|---|
+| `client.analytics.query` | `any` | `BaseResponse & { data: AnalyticsResult }` | dispatcher-served; `deps.success(v)` wraps and `res.json()` strips nothing |
+| `client.analytics.meta` | `any` | `AnalyticsMetadataResponse` | same envelope; `data` is the bare `CubeMeta[]` projection |
+| `client.analytics.explain` | `any` | `AnalyticsSqlResponse` | same envelope; `data` is `{ sql, params }` |
+| `client.automation.trigger` | `any` | `BaseResponse & { data: AutomationResult }` | same envelope, over the payload its sibling `automation.execute` unwraps |
+| `client.analytics.queryDataset` | `any` | `AnalyticsResult` | served by `@objectstack/rest`, which ends `res.json(result)` — no envelope |
+
+`any` is assignable to everything and admits every property read, so a
+consumer's code can stop compiling where it previously did not. Concretely:
+
+- **Reading a payload key off one of the four ENVELOPED results.**
+  `(await client.analytics.query(q)).rows` compiled and was `undefined` at
+  runtime; the read the wire always required is `.data.rows`. Same for
+  `.data` on `meta` / `explain`, and `.data.runId` / `.data.screen` on
+  `automation.trigger`.
+- **Reading `.data` off `queryDataset`**, which is served bare — likewise
+  `undefined` today, likewise refused now.
+- Assigning any of the five results to an unrelated annotation, or forwarding
+  one to a differently-typed parameter.
+
+That break is the point: those call sites are already wrong at runtime and the
+`any` is what hid it. The compiler is the channel that reaches every affected
+consumer, and it is strictly more precise than a release note.
+
+## How the shapes were established
+
+By DRIVING the real producers — a real `AnalyticsService`, a real
+`AutomationEngine`, the real `HttpDispatcher` and the real `RestServer`, with
+only the socket stood in for — not by reading source and not by asserting
+against a mock. Two spec response types that look like the right binding are
+NARROWER than the contract their route relays
+(`AnalyticsResultResponseSchema.data.fields` and
+`TriggerFlowResponseSchema.data`), so those two annotations bind the producer's
+contract instead; the near-miss is pinned so a later sweep cannot retarget them.
+
+## Scope
+
+The five families whose producers live in this repo. The 38 better-auth-backed
+`auth.*` / `organizations.*` / `oauth.*` methods of the same class are untouched
+and keep their erased `any` — they are exactly as permissive as before, and no
+consumer loses anything by that.
+
+No ADR-0087 ledger entry: nothing here is a metadata surface. No Zod schema, no
+`packages/spec` declaration and no stored representation changed — the erasure
+lived only in a TypeScript return annotation — so `objectstack migrate meta` has
+nothing to rewrite and an entry would have no artifact to project into. This is
+the disposition #8140, #11925 and #12034 recorded for the same class of SDK
+return-type narrowing.