Release v0.14.0 - 2026-07-03

Highlights

Added live-pricing source readiness details so admins can see whether each provider is ready to refresh, blocked by policy, missing credentials, or waiting on provider-specific configuration.
Added environment-based source policy and credential support for live pricing, making it easier to enable providers per deployment without storing provider secrets in the database.

The live-pricing provider list now reports refresh readiness for each registered source, including whether automated refresh dispatch is effectively enabled and why a source is blocked.
The manual pricing source now clearly separates admin offer writes from automated refresh readiness, so manual catalog edits can remain available even when provider refresh dispatch is off.
Provider credentials supplied through deployment configuration take precedence over older stored source credentials on the default provider endpoints. Secret values are never returned by the API.

Added:
- Readiness fields on GET /v1/enzan/pricing/providers, including environment policy status, effective refresh readiness, blocker reason, secret configuration status, credential source, and legacy stored-secret presence.
- Manual-source offer-write readiness on the provider list so clients can distinguish manual catalog editing from automated provider refresh dispatch.
Changed:
- Live-pricing status and configuration reads remain available when automated refresh dispatch is globally disabled, while refresh trigger writes still fail until dispatch is enabled.
- Provider refresh attempts skip sources that are disabled by deployment policy, missing required credentials, or blocked by invalid provider configuration.

Clients that used a failed provider-list request as a signal that live-pricing refresh dispatch was disabled should now inspect the provider readiness fields or the refresh trigger response instead.
Provider-list clients should treat the new readiness fields as optional for compatibility with older server versions and custom admin tooling.
Runpod provider configurations that currently store only a bearer token should be updated before enabling refreshes; Runpod requires a usable API key, authorization header, or no credential for the public catalog path.

Updated the API reference, SDK docs, deployment guide, and environment reference for live-pricing source policy, provider credentials, and readiness reporting.