measure: `/meta/diagnostics`' untyped sweep stays environment-wide on a justification that PR #14767 may have retired

[hotlong]

Filed so the gap survives #13753's retirement. PR #15689 carries Fixes #13753, and that card's body is currently the only place this gap is written down as a decision. This card is its new home.

The gap

GET /api/v1/meta/diagnostics has two arms. The typed arm (?type=) was repaired: it resolves the exec ctx and passes organizationIdForMetaRead(canonicalMetaUrlType(diagnosticsType), ctx?.tenantId), so Studio's per-type directory drill-down states the caller's organization. The untyped sweep — the whole-registry pass behind the governance dashboard — is deliberately left environment-wide.

Why the justification needs re-measuring rather than re-reading

The reasoning recorded beside it is, in substance:

targetTypes is then the whole registry while the request carries ONE organizationId, and getMetaItems unions env-wide rows with the named org's rows — so naming a tenant would read a non-overridable type's org-scoped rows (the pre-#6190 phantoms boot hydration walks past) back into a governance report.

⚠️ That leans on the same premise PR #14767 retired. Since 96326040f (merged 2026-09-03T02:51:39Z, "apply the allowOrgOverride read gate inside getMetaItems, so multi-type sweeps are scoped per type"), getMetaItems computes organizationIdForMetaRead(request.type, request.organizationId) on its own type — so a whole-registry sweep carrying one organization would gate per type, and a non-overridable type's phantom org rows would be dropped rather than unioned in. That is exactly the hazard the paragraph above exists to prevent.

⇒ The justification may now be describing a mechanism that no longer behaves that way. ⛔ This card does not assert the sweep should change — it asserts the reason on file is unverified against today's code, and a governance dashboard is a poor place to leave that.

⭐ Precedent, and the reason this is filed rather than assumed: the identical stale premise was carried for over a day on #13753 and produced a re-triage that refuted a correct fix and escalated it to the maintainer's inbox. See #13753 comments 5541727271 (the refutation) and 5548741000 (its retirement).

Scope — measurement first, decision second

1. Measure, on a real boot with a walled posture: does the untyped sweep, given a caller's organization, return a non-overridable type's org-scoped rows (the phantom hazard), or does the per-type gate drop them? Drive both — plant a pre-org 作用域的 flow overlay 只在「本进程内发布后」绑定触发器,重启后静默失绑——冷启动两条读路径都把 organization_id 非空的行滤掉了 #6190 phantom on a non-overridable type and an org-authored row on an overridable one — and read what the sweep returns for each. A control that cannot distinguish the two has measured nothing.
2. Then decide, and record the reason beside the code either way: keep the sweep env-wide (with a justification that matches today's behaviour), or state the caller's organization the way the typed arm does.
3. ⛔ Do not build a new predicate, parameter or contract surface. ADR-0131 D6/D7 retires this partition in v18 (feat(metadata-core,metadata-protocol,objectql,plugin-security): the sys_metadata family goes tenant-less; the per-organization overlay axis retires; managed content is sealed (ADR-0131 D6/D7/D13) #15206, C5), so anything new here has one major to live. If the answer requires new surface, stop and report — that is a decision, not an implementation.

Not this card

⛔ /meta/:type/:name/references — repaired by PR #15689. ⛔ The 501 envelope and message divergence on the references route — filed separately as #15685.

Refs: #13753 (this gap's former home, and its stale-premise history) · PR #15689 · PR #14767 / 96326040f · #6190 · #15206 (ADR-0131 C5).

[hotlong]

Duplicate of #15622 — closing. The dedupe failure is mine.

#15622 was filed 2026-09-05T00:14:42Z, roughly three hours before this card, and covers the same gap with more precision: it names the for (const t of targetTypes) loop inside getMetaDiagnostics, cites the gate by card (#14683) rather than by PR (#14767) — the same change, 96326040f — and states the product question this card only gestured at (an org-scoped caller would start seeing counts it did not see before).

⛔ Nothing here supersedes it. Everything this card said, #15622 says or implies.

Why it happened, stated rather than glossed: I filed this while closing out #13753, from the gap recorded in that card's body, and did not run a dedupe search first. The repo's own rule is to search keywords before filing — /meta/diagnostics and untyped sweep would both have returned #15622 immediately. A second card on a live needs-user-decision is worse than none: it splits the thread and invites two seats to answer the same question differently.

The one thing worth carrying over, and it is now recorded on #15622: this gap's justification leans on the same premise that the #13753 re-triage inherited without re-measuring — so the precedent for how it should be settled (measure, do not re-read) travels with it.

Closed as not planned — superseded, not resolved. Work continues on #15622.