From 88c09c9863c05f3502c76c34dff523f29e43715d Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 20 Aug 2026 15:37:19 +0000 Subject: [PATCH] docs(api): teach the singular `/meta/:type` spelling as the canonical one (#10078) `metadata-api.mdx` taught the plural as a co-equal address ("singular or plural -- `object` and `objects` address the same type", "both forms exist in the wild"). The 2026-08-17 re-weigh of the #9180 ruling scopes step 3 to internal spelling correction across the self-owned repos: the direction ("singular is the only canonical spelling") stands, and our own docs stop teaching the plural as an equal alternative. The boundary fold stays exactly as it is -- undocumented, and not a documented promise. Nothing here changes what the API accepts or refuses; this page stops advertising a tolerance, which is the whole of the change. Part of #10078 --- content/docs/api/metadata-api.mdx | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/content/docs/api/metadata-api.mdx b/content/docs/api/metadata-api.mdx index e4564b59c4..f4b8c6816b 100644 --- a/content/docs/api/metadata-api.mdx +++ b/content/docs/api/metadata-api.mdx @@ -28,13 +28,16 @@ List all items of a metadata type. | Parameter | Location | Description | |:----------|:---------|:------------| -| `type` | path | Metadata type name, singular or plural — `object` and `objects` address the same type | +| `type` | path | Metadata type name — the **singular** spelling (`object`, `view`, `flow`) | -Both spellings are accepted and behave **identically**: the same audience gate -(ADR-0046 §6.7 books/docs), the same RBAC filtering of privileged apps, and the -same response shaping apply either way. Metadata type names are singular by -convention (Prime Directive #3) while REST paths are plural, so both forms exist -in the wild. +Metadata type names are singular (Prime Directive #3) and this segment is the +type name itself, so the spelling to send is `object` — never `objects`. The +plurals elsewhere in this API name something else: a collection of *records* +(`/data/:object`) or a package-manifest key (`objects: [...]`). Neither carries +across to a `/meta` type segment. + +Listing applies the ADR-0046 §6.7 audience gate to books and docs, RBAC +filtering to privileged apps, and the usual response shaping. **Response**: `{ type: "object", items: [{ name: "account", ... }, ...] }`