12. 404 - schema not registered

The URL targets a schema id that is not registered for this tenant. Same root cause as the SQL unknown_table 400, but surfaced at the REST resource layer rather than through the SQL translator.

A direct GET against a schema id that doesn't exist.

curl "https://$OC_HOST/v1/tenants/$OC_TENANT/schemas/does.not.exist" \
  -H "Authorization: Bearer $OC_TOKEN"

{
  "error": "schema_not_found",
  "message": "no schema 'does.not.exist' for tenant",
  "retry": false
}

• List schemas registered for this tenant: GET /v1/tenants/:t/schemas.
• Register the manifest with PUT /v1/tenants/:t/schemas/:id if it should exist.
• Confirm the schema id is fully qualified - the catalog stores shop.customers, not customers.
• retry: false - register the schema first, then retry.