Class CatalogClient

Open a curation case (ADR-0013). Admin.

Decide a curation case (approve / reject / request-changes). Admin.

Fetch one template's full detail (manifest included). Public.

get, but a WITHDRAWN (or unknown) template/version resolves to null instead of throwing.

Yank state is not a field on any public response — the backend expresses it ONLY through absence (backend/src/routes/handlers/catalog.ts):

• toSummary (:156-170) carries no yanked* field, so neither the index nor the detail response ever reports it;
• getTemplateHandler (:327) 404s an explicit ?version= read of a yanked version, and 404s the latest read when every version is yanked;
• the repository's public list drops fully-yanked templates and repoints the LATEST row to the newest surviving version on yank (CatalogTemplateRepository.ts:288-290, :475-483).

So a 404 IS the yank signal, and this method is what a caller uses to confirm a version it learned about elsewhere (a cached index row, an app's templateRef) is still serveable — e.g. the "update available" badge verifying the advertised latest before advertising it.

Any non-404 failure still throws (a network blip must not read as "yanked").

Resolve a presigned URL for a compose bundle by digest. Public.

List published templates, optionally filtered. Public — no credentials required.

One row per template at its latest SERVEABLE version: the backend excludes fully-yanked templates and repoints LATEST past a yanked version, and no row carries yank state. A row is therefore a point-in-time claim — re-confirm with getAvailableVersion before acting on a cached one.

List curation cases, optionally filtered by status (queue view). Admin.

Publish a template version (manifest + bundle digest + image map). Admin.

Report a nightly verification outcome for a template (Phase 8 writer). Admin.