fix(security): close out the stored-metadata-body family — project or refuse every further read/copy/evaluate exit

[objectstack-fleet]

Fixes #21120

Clause-②: no (narrowing)

Security boundary — human floor. This PR stays in DRAFT. It narrows a
credential-disclosure surface; landing is the maintainer's. No AI seat flips
it ready, queues it or arms auto-merge.

What this does

Stored metadata bodies (sys_metadata / sys_metadata_history's metadata
column — stored datasource credential material included) are declared
write-only and are already redacted on the /meta and datasource doors and, as
of #21086, on the generic data door's reads. This PR closes out the remaining
surfaces that can serve, copy or evaluate such a body, so each either goes
through the one shared redaction seam or refuses — and adds an enumeration pin
so a future surface fails the pin instead of joining the family silently.

• One seam, no second dialect. The family-wide primitives — the object set,
  the body predicate, the column names and the per-type body redactor — now live
  once in @objectstack/spec/kernel, beside the redactor registry they build
  on. The data door's wrappers (projection, dropType, the groupBy and the new
  filter/sort refusals) consume that one definition, as do the audit, analytics
  and realtime exits — none of which depends on @objectstack/metadata-protocol.

• Audit / activity copy (@objectstack/plugin-audit). The audit writer
  copies a stored-metadata row into sys_audit_log.new_value / old_value and
  sys_activity.metadata at write time — a second, admin-readable, at-rest
  store. The copy now projects the body through the shared redactor, so the
  credential is withheld there too, and a one-off migration
  (os migrate audit-metadata-bodies, dry-run by default, --apply, idempotent)
  rewrites the copies already at rest. Fail-closed: a body the redactor cannot
  judge is dropped from the recorded copy.

• Analytics (@objectstack/service-analytics). A query naming the stored
  body column of these objects as a dimension, measure, filter or sort is
  refused (400 INVALID_FIELD) at the service door, ahead of every strategy —
  the posture analytics already takes for a member it will not evaluate.

• Realtime (@objectstack/objectql). A data.record.* event projects its
  after / changes body through the same redactor, so a subscriber to these
  objects' events receives no stored credential. (Predicate/bulk events carry
  only a count, so they were already safe.)

• Data door filter / sort (@objectstack/metadata-protocol, maintainer
  ruling A). A filter or sort on the body column is refused (400 INVALID_FIELD),
  the same family and shape as the merged groupBy refusal. This lands on [security] Stored datasource credentials are served unredacted to an admin through a read path outside the two datasource read doors — detail withheld pending maintainer #21086's
  seam, now on main (merged in; no stacked branch).

What stays answerable on both tables: every scalar column — type, name,
scope, state, timestamps — is still grouped, filtered, sorted, counted and
served. Only the body column is affected, and only on these two objects.

Enumeration pin

packages/metadata-protocol/src/stored-metadata-body-family.pin.test.ts pins
the family: the object set is the boundary, every declared apiMethods verb on
the two objects is a covered read verb (a new verb or a write verb fails the
pin), and each family surface is enumerated with its disposition and owning
per-package pin.

Tests

• spec: the shared seam (register/lookup, fail-closed, by-reference) — metadata-type-redaction.test.ts.
• metadata-protocol: the family enumeration pin; the merged [security] Stored datasource credentials are served unredacted to an admin through a read path outside the two datasource read doors — detail withheld pending maintainer #21086 data-door suite still green on the reconciled seam.
• plugin-audit: the writer redaction (create / update rotation / clean body) in audit-writers.test.ts; the migration planners and driven runner (dry-run, apply, idempotent) in stored-metadata-body-migration.test.ts.
• service-analytics: the member refusal — stored-metadata-body-refusal.test.ts.
• objectql: the realtime event redaction — engine-realtime-stored-metadata-body.test.ts.

Changed lines well under the 5,000 human-merge threshold.

🤖 Generated with Claude Code

https://claude.ai/code/session_01MRdbfpy4sQT8bUjmMhxsN7

[github-actions]

📓 Docs Drift Check

This PR changes 6 package(s): @objectstack/cli, @objectstack/metadata-protocol, @objectstack/objectql, @objectstack/plugin-audit, @objectstack/service-analytics, @objectstack/spec, touching 52 documentable anchor(s). ⚠️ 4 changed file(s) yielded no anchor (packages/cli/vitest.config.ts, packages/plugins/plugin-audit/src/index.ts, packages/spec/api-surface/kernel.json, …), so the pages documenting them are NOT COVERED by this run — this is not a clean bill of health for those files.

56 hand-written doc(s) name something this change touched — list omitted above 15 rows. Re-derive on the tree named below: node scripts/docs-audit/affected-docs.mjs --json f0cc16e8d55b02269c7db708254e2917ba7e84e2.

⛔ 13 release-owned page(s) also affected — read-only, see AGENTS.md Documentation Guardrails.

What this run could not see

• 4 changed file(s) yielded no anchor (packages/cli/vitest.config.ts, packages/plugins/plugin-audit/src/index.ts, packages/spec/api-surface/kernel.json, …) — pages documenting those are invisible to this run
• 9 name(s) were too generic to anchor anything (single lowercase words)
• the SDK route bridge reached 54 of 206 client-bound route-ledger rows — the other 152 have no registrar path: tail to select them, so pages documenting THEIR client methods cannot appear above, on this or any run. Of those 152: 0 are remediable by widening that discovery convention (an in-repo file declares the path; the convention did not scan it); 55 are structural — on a ledger where NOT ONE row is declared in-repo, so no discovery change reaches them at any price; 97 are undecided (no in-repo declaration, on a ledger that has other in-repo registrars — absence and an unreadable spelling are not distinguishable here). The rows themselves: node scripts/docs-audit/affected-docs.mjs --bridge-coverage
• 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.
• a key NAME is not a key, so the hand re-read the line above prescribes can land on the wrong schema. The same spelling is authorable on one governed type and a [REMOVED] tombstone on another for each of active, aria, joins, objects, template, tools and version (censused on [finding] tools is a key on BOTH AgentSchema (tombstoned, dead) and SkillSchema (live, cloud-attested), so a name-based search attributes skill examples to the agent key — it produced a false stop-the-line alarm on PR #19059 #19093 over the liveness ledger's governed types, top-level keys); nothing in a search result distinguishes the two, so a grep hit on a LIVE example reads as evidence about the DEAD key. Measured on fix(spec): the agent.tools liveness row says dead — it claimed live on a key the schema tombstoned #19059: content/docs/ai/agents.mdx was reported as contradicting the agent.tools tombstone over its tools: example at :161, which is inside the defineSkill({ block opened at :155 — the page was already correct. Settle ownership by PARSING the value against both schemas, never by the name: that literal PASSES SkillSchema, and as an AgentSchema it FAILS at tools with the tombstone prescription. ⛔ These names are not the whole class — a key retired through a .strict() guidance map leaves no tombstone in the walked shape and none of them here (tool.category, live as AIToolDefinition.category).

Coarse fallback — 146 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 f0cc16e8d55b02269c7db708254e2917ba7e84e2 → packageMentionDocs.

Which tree this was computed on

This run read content/docs from 05a6397133583889cc6ed84e2813896912e0cc7c — the merge of head 5397aa8ba8d301d6e0261f611af1c83f2ed5e6b3 into base f0cc16e8d55b02269c7db708254e2917ba7e84e2, which is what actions/checkout gives a pull_request run. Not the PR head.

A worktree cut from an older main holds a different content/docs, so re-deriving there can legitimately return a different list — that is a different tree, not a wrong row. To answer on the same tree:

# while this PR is open — GitHub drops the merge commit once it closes
git fetch origin 05a6397133583889cc6ed84e2813896912e0cc7c && git checkout 05a6397133583889cc6ed84e2813896912e0cc7c
# afterwards, rebuild it from the two parents, which stay fetchable
git fetch origin f0cc16e8d55b02269c7db708254e2917ba7e84e2 5397aa8ba8d301d6e0261f611af1c83f2ed5e6b3 && git checkout -B drift-repro f0cc16e8d55b02269c7db708254e2917ba7e84e2 && git merge --no-ff 5397aa8ba8d301d6e0261f611af1c83f2ed5e6b3

node scripts/docs-audit/affected-docs.mjs --json f0cc16e8d55b02269c7db708254e2917ba7e84e2

⚠️ That checkout carried uncommitted changes, so the commit above does not fully identify what was read.

Advisory only, and a precision-first one (#9192): a page is listed because it names a
symbol, wire route or SDK method this diff touched — not because it mentions a changed
package. Each row says which anchor put it there, so a wrong row is reportable rather than
merely annoying. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs f0cc16e8d55b02269c7db708254e2917ba7e84e2 → pass the list as
args.docs, on the commit named under Which tree this was computed on.

[objectstack-fleet]

Landing note: this is a security-boundary change (human floor), so the PR stayed draft until the maintainer decided. The maintainer pre-authorized landing once CI was green, selecting verbatim 「绿了就转 ready + 进队列（推荐）」 in Claude Code session session_01MRdbfpy4sQT8bUjmMhxsN7 on 2026-10-01; the PM review is recorded on #21120. CI on head 5397aa8ba8 is 33 success / 2 skipped / 0 failed, mergeable clean. The PR is now ready with auto-merge armed, and the merge queue re-validates on the merged generation.

---

Generated by Claude Code