fix(security): guard the write-response internal-field property, not one class (#8497) (#8587)

* fix(security): guard the write-response internal-field property, not one class (#8497)

Widen the #7823 write-response `internal: true` guard from "every `*Data` face
on the protocol class" to the property it exists to hold: no response body an
external caller receives from a write carries an `internal: true` value.

Widening it found a live leak. `@objectstack/mcp`'s stdio bridge is engine-only
by construction and its `create` arm echoed `engine.insert`'s result — whole
since #7823 relocated the strip off the engine — straight back to the MCP
caller. Measured, fixed, and pinned.

- mcp: strip on `create` (the leak) and on `update` (so a caller cannot use
  their own patch as an oracle on an internal column).
- core: the shared strip helper moves here from metadata-protocol, which
  re-exports it unchanged. `rest` and `mcp` both write through the engine
  directly and neither depends on metadata-protocol, so the old home forced
  every new mouth to duck-type or restate the rule.
- rest + mcp: two new tripwires, same mechanism as the shipped one (runtime
  enumeration, total disposition map, negative control). The shipped protocol
  tripwire is untouched.

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

* test(rest): keep the new tripwire out of the TEST_DEBT ratchet (#8497)

`packages/rest` hides its test files from its own `typecheck` script, so the
package typecheck passed while `check:type-check-debt` measured +2 raw tsc
errors against the frozen TEST_DEBT entry — both of them in the new tripwire:
a relative import missing its `.js` extension under NodeNext, and
`registry.registerObject` called without its required `packageId`.

Fixed rather than ledgered: TEST_DEBT is a shrink-only ratchet and raising it
is maintainer-only. Re-measured at 155, exactly the recorded value.

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

---------

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

Author: os-zhuang

.changeset/write-response-internal-fields-property-guard.md

@@ -0,0 +1,74 @@
+---
+"@objectstack/core": patch
+"@objectstack/metadata-protocol": patch
+"@objectstack/mcp": patch
+---
+
+fix(security): the MCP stdio bridge stops echoing `internal: true` columns from a write, and the write-response guarantee is guarded as a PROPERTY rather than per-class (#8497)
+
+**A live leak, found by widening a guard.** #7823 relocated the `internal: true`
+write-response strip to the generic-data-path ingress and gated the relocation on
+a tripwire that enumerates every `*Data` face on the protocol class. The card that
+produced this change observed that the guard's coverage — *"every `*Data` face on
+one class"* — is narrower than the property that needs holding — *"no response body
+an external caller receives from a write carries an `internal: true` value"* — and
+that `@objectstack/rest`'s cross-object batch (a direct `ql.update`) was the
+standing proof the two are not the same set.
+
+Widening the guard to the property immediately found a second direct mouth that
+was **not** covered, and it was leaking. `@objectstack/mcp`'s stdio bridge
+(`stdio-data-bridge.ts`) is engine-only by construction — the long-lived stdio
+host cannot reuse the runtime's request-shaped `callData` builder — and its
+`create` arm handed `engine.insert`'s result straight back to the MCP caller.
+Since #7823 the engine deliberately keeps its write results whole, so the flagged
+column rode the tool response verbatim. Measured before the fix:
+
+```
+{"object":"vault","id":"r1","record":{"name":"row","id":"r1","vault_secret":"<the stored secret>"}}
+```
+
+The file's own header had listed its protocol-layer divergences as *"deliberate,
+filed, not security"*. One limb of that list **was** security, and the header now
+says so.
+
+**What changed**
+
+- `@objectstack/mcp` — the stdio bridge's `create` runs its response record
+  through the shared strip. `update` does too: that arm discards the engine's
+  write result and echoes the read-path row plus the caller's own patch, so no
+  *stored* value could reach it, but a caller who puts an `internal: true` key in
+  `data` would otherwise get it echoed back — their own bytes used as an oracle
+  for a column the flag says is never returned. Read verbs are untouched (the
+  engine's read-path strip is unchanged).
+- `@objectstack/core` — the strip helper
+  (`omitInternalFieldsFromWriteResponse` / `collectInternalWriteResponseFields`)
+  moved here from `@objectstack/metadata-protocol`. It shipped beside the protocol
+  class when that class was its only caller, but the generic write mouths are not
+  all on it: `rest` and `mcp` both reach the engine directly and **neither depends
+  on `@objectstack/metadata-protocol`**, so the old home forced each new mouth to
+  choose between a duck-typed reach through a protocol instance and a private
+  restatement of a security-relevant rule. `core` is the floor all three already
+  depend on, and already hosts this class of shared write-path helper
+  (`bulk-write.ts`). No behaviour change and no API change:
+  `@objectstack/metadata-protocol` re-exports both names unchanged.
+
+**What guards it now.** Two new tripwires join the shipped one — which is **not**
+replaced: its runtime prototype walk and its `leakyData` negative control are
+untouched. Each is a runtime enumeration no author can dodge by adding code
+without touching it, and each fails on a surface it has no disposition for:
+
+- `metadata-protocol` — walks the protocol class for `*Data` faces (unchanged);
+- `rest` — walks `RestServer.getRoutes()` for HTTP write routes, drives the ten
+  data-plane ones (including `POST /batch`, the direct-`ql.update` mouth) against
+  a fixture whose stored rows carry a flagged sentinel, and deep-scans each
+  response body;
+- `mcp` — walks the `McpDataBridge` faces the factory actually returns.
+
+Every driven case also asserts a control value is present, so a refusal or an
+empty body cannot satisfy "no sentinel" by returning nothing.
+
+Reverse-verified in both directions, the discipline #7823's own fix used: deleting
+the strip from the REST batch arm turned the REST tripwire red on exactly that
+route; adding a *second* unstripped direct engine mouth turned it red again;
+removing the new MCP strip turned the MCP tripwire red; every restore was proven
+byte-identical with `git hash-object`.

packages/core/src/index.ts

@@ -36,6 +36,14 @@ export * from './utils/datetime.js';
 // Export the shared batched-write helper (framework#2678)
 export * from './utils/bulk-write.js';
 
+// Export the shared write-response `internal: true` strip (#7823, #8497) — the
+// ONE helper every write mouth that answers an external caller runs its
+// records through. It lives here, on the floor all three transports share,
+// because the mouths are not all on the protocol class: `rest` and `mcp` both
+// reach the engine directly and neither depends on `@objectstack/metadata-
+// protocol` (which re-exports these two names unchanged).
+export * from './utils/internal-write-response.js';
+
 // Export the migration-journal runner (ADR-0119 D2, #4617) — chunk-atomic
 // migrations with durable recovery, plus the shared `engineCanRollBack` gate
 // that `@objectstack/metadata-protocol`'s atomic `batchData` also uses.

packages/core/src/utils/internal-write-response.ts

@@ -0,0 +1,143 @@
+// Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.
+
+/**
+ * [#7823 / #8497] The write-response half of the `internal: true` guarantee —
+ * THE single helper every write mouth that returns a body to an external
+ * caller passes its record(s) through.
+ *
+ * ## The contract
+ *
+ * A field declared `internal: true` is *never returned on the generic data
+ * path* (#7728). The READ half lives in the engine (`omitInternalFields` runs
+ * on every find/findOne result). The WRITE-RESPONSE half lives HERE.
+ *
+ * ## Why the ingress and not the engine (the measured history, #7823)
+ *
+ * The first shape stripped `internal` fields inside the engine's insert and
+ * by-id-update paths. That conflated two different guarantees:
+ *
+ *  - "never returned on the generic data path" — the flag's sentence, about
+ *    what an EXTERNAL caller receives; and
+ *  - "never returned to the engine-level caller that performed the write" —
+ *    which no ruling ever asked for, and which is FALSE for credential mint:
+ *    better-auth's `createWithHooks` reads the minted `sys_session` row back
+ *    off the insert result, so the engine-side strip broke `signIn`/`signUp`
+ *    outright (measured: `verify signIn: no token in response`).
+ *
+ * Plain removal of the engine limbs was ALSO measured wrong: the by-id-update
+ * strip was the sole closure of #7728's fourth surface — with it neutralised,
+ * `PATCH /data/sys_api_key/{id}` answered 200 with the stored 64-hex `key`
+ * hash in the body. Both measurements are satisfiable at exactly one boundary:
+ * the mouth that builds the external 201/200 body. Engine write results keep
+ * the stored row whole (mint works); every external write response is stripped
+ * through this helper (the hash never leaves); the read path is untouched.
+ *
+ * ## Why this module sits in `@objectstack/core` (#8497)
+ *
+ * It shipped inside `@objectstack/metadata-protocol`, next to the protocol
+ * class that was then its only caller. That placement encoded an assumption
+ * the surface does not honour: **the generic write mouths are not all on the
+ * protocol class.** Two transports reach the engine directly —
+ *
+ *  - `@objectstack/rest` (`rest-server.ts`, the cross-object `POST /batch`
+ *    update arm's direct `ql.update`), and
+ *  - `@objectstack/mcp` (`stdio-data-bridge.ts`, whose `create` handed the
+ *    engine's insert result straight back to the MCP client — a MEASURED leak
+ *    of the flagged column, found by widening this guard's scope in #8497),
+ *
+ * — and neither package depends on `@objectstack/metadata-protocol`. The old
+ * home therefore forced each new mouth to choose between a duck-typed reach
+ * through a protocol instance (what `rest` does) and a private restatement of
+ * the rule (a third copy of a security-relevant predicate). `@objectstack/core`
+ * is the floor all three already depend on, and it already hosts exactly this
+ * class of shared write-path helper (`bulk-write.ts`, used by both
+ * `metadata-protocol` and `rest` so neither reimplements batching). One helper,
+ * reachable from every mouth, is the whole point of the flag being structural.
+ *
+ * `@objectstack/metadata-protocol` re-exports both functions unchanged, so its
+ * public API is byte-identical across the move.
+ *
+ * ## The residual risk, and what gates it
+ *
+ * Response-body policy at the mouth means a FUTURE write mouth that forgets
+ * this helper leaks silently. Three tripwires hold the property, each an
+ * enumeration no author can dodge by adding code without touching it:
+ *
+ *  - `protocol.write-response-internal-fields.tripwire.test.ts`
+ *    (`metadata-protocol`) walks the protocol class's prototype for `*Data`
+ *    faces;
+ *  - `rest-write-response-internal-fields.tripwire.test.ts` (`rest`) walks
+ *    `RestServer.getRoutes()` for HTTP write routes;
+ *  - `mcp-write-response-internal-fields.tripwire.test.ts` (`mcp`) walks the
+ *    `McpDataBridge` write faces.
+ *
+ * Together they assert the PROPERTY — "no response body an external caller
+ * receives from a write carries an `internal: true` value" — rather than the
+ * shape of any one class. Adding a write mouth? Route its response records
+ * through this helper and register it with the tripwire that enumerates its
+ * surface.
+ *
+ * ## Semantics
+ *
+ * Mirrors the engine's `collectInternalReadFields` rule exactly — a field
+ * participates iff its declaration carries `internal === true` (strict
+ * boolean; truthy strings and numbers do not count, same as the engine).
+ * `@objectstack/core` cannot import that collector (`@objectstack/objectql`
+ * sits above this package), so the rule is restated here in full;
+ * `internal-fields.test.ts` in objectql and the tripwires above pin the same
+ * spelling from both sides. OMIT, not mask, for the #7728 reasons: the flag's
+ * columns are `required`, so a mask carries zero bits while still shipping a
+ * value under a field whose description promises none.
+ *
+ * Deletion is IN PLACE and idempotent: records that already lack the field
+ * (a re-stripped read result, a fake engine that never returned it) pass
+ * through unchanged, and non-record values (`null`, an affected-row count, a
+ * driver's boolean delete verdict) are skipped rather than judged.
+ */
+
+/** Minimal view of an object schema this module reads — the field map only. */
+interface SchemaWithFields {
+  fields?: Record<string, { internal?: unknown } | undefined> | undefined;
+}
+
+/**
+ * Collect the names of fields declared `internal: true` on `schema`.
+ *
+ * Same verdicts as objectql's `collectInternalReadFields` (see the module
+ * header for why it is restated rather than imported): strict `=== true`,
+ * empty result for a missing/field-less schema.
+ */
+export function collectInternalWriteResponseFields(schema: unknown): string[] {
+  const fields = (schema as SchemaWithFields | null | undefined)?.fields;
+  if (!fields || typeof fields !== 'object') return [];
+  const out: string[] = [];
+  for (const [name, def] of Object.entries(fields)) {
+    if (def && def.internal === true) out.push(name);
+  }
+  return out;
+}
+
+/**
+ * Drop every `internal: true` field from a write response's record(s), in
+ * place. THE single helper every external write mouth goes through — see the
+ * module header; the three tripwires enforce the "every".
+ *
+ * @param schema  The registered object schema (`engine.registry.getObject(...)`
+ *                / the protocol's own registry view / `metadataService
+ *                .getObject(...)`). An unknown object (no schema) strips
+ *                nothing — the write itself would have been refused upstream
+ *                by the object-existence gate.
+ * @param records A single record, an array of records, or anything a write
+ *                mouth hands back where a record could sit (`null`, a count, a
+ *                boolean): non-objects are skipped, arrays are walked.
+ */
+export function omitInternalFieldsFromWriteResponse(schema: unknown, records: unknown): void {
+  if (!records) return;
+  const internalFields = collectInternalWriteResponseFields(schema);
+  if (internalFields.length === 0) return;
+  const list = Array.isArray(records) ? records : [records];
+  for (const row of list) {
+    if (!row || typeof row !== 'object') continue;
+    for (const field of internalFields) delete (row as Record<string, unknown>)[field];
+  }
+}