chore(client): drop the stale packages.update exported-any ledger entry

[os-zhuang]

Unblocks the repo-wide red on Type Check · consumer gates.

#12062 bound ObjectStackClient.packages.update to InstalledPackage, but the corresponding row in packages/client/exported-any-returns.json survived the merge. The ledger is exact-judged and shrink-only, so check:exported-any-returns now fails on every PR's merge commit with:

❌ 1 stale exported-any-returns.json entr(y/ies) — the gap is closed, delete the entry: • ObjectStackClient.packages.update

First observed on #12093's CI (job 97795807249); any PR running consumer gates against current main reproduces it.

One-line fix, exactly what the gate's own failure text prescribes. Gate re-run locally on this branch after pnpm --filter '@objectstack/client...' build:

✅ self-test: flags awaited-`any` returns through nested namespaces, …
✅ no NEW exported callable of @objectstack/client resolves to `any`: 317 callables reached
(51 caller-supplied generics, not counted as erasure), 64 ledgered site(s) still open.

No changeset: a repo-internal gate ledger, nothing published.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

⚠️1 changed file(s) yielded no anchor (packages/client/exported-any-returns.json), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files. Nothing else in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 1 changed package(s)).

What this run could not see

• 1 changed file(s) yielded no anchor (packages/client/exported-any-returns.json) — pages documenting those are invisible to this run
• a page that states a rule by its inputs shares no identifier with the emitter that implements the rule, so an emitter-only diff cannot list it — not on this run and not on any run. Measured on fix(driver-sql): emit varchar(maxLength) for a text field a declared index keys on #11430: content/docs/protocol/objectql/types.mdx documents the text-family column mapping by the ObjectQL type names it maps FROM (text / textarea / html) while the diff changed createColumn; it went unlisted, and it was the page that diff falsified, in four places. No shared token exists to detect this on, so a rule your change carries has to be re-read by hand in the pages that restate it.

Coarse fallback — 15 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json 22c42c9b21a479b502583ae74ac588232564a6a8 → packageMentionDocs.