The first pod that survived long enough to answer returned:
"Model 'bge-m3' is not available. Use one of: " — nothing after the
colon. A pod starts with an EMPTY catalogue. A per-model pod is seeded
with its one model, but a capability pod has no model entry at all, so it
refused everything.

Capability pods are now seeded with this deployment's models OF THAT
CAPABILITY — only ones the pod can actually fetch (a HuggingFace repo id
or a URL), since registering a local path would turn a clear "not
available" into a confusing load failure.

The seeding was also unreachable for any pod with an explicit image: the
coderai branch returned early only when the image was UNSET, and
capability pods always have one now (the published default). Both cases
go through one path that carries the auth token and the catalogue
together.

What the live run did prove, before failing on the catalogue: GPU
selection with price ranking and capacity fallback, the boot health gate,
pod bearer auth (our token accepted; an unauthenticated call gets 401),
gateway forwarding to the pod URL, idle reaping after 120s, and the spend
ledger ($0.033 for the run).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0182DhR1eFNPQyGmDrpHbedY