gormes-provider-parity

Provider parity issues are diagnosed and fixed by aligning configuration semantics, operator UX, gateway responses, and error handling for auth, credentials, endpoints, model-routing, streaming, and rate-limits between Hermes and Gormes.

Telegram-visible provider errors occur when Hermes parity gaps exist in error handling and gateway responses. Diagnosing these gaps aligns operator UX and restores expected Telegram-visible provider error behavior without relying on Python runtime services.

Provider parity alignment does not require Python runtime services. The skill provides safe, Python-free parity tooling that mirrors Hermes UX to reduce provider incidents and incident reproduction time across development and runtime environments.

Diagnose Hermes parity gaps in model-routing and streaming by comparing configuration semantics and gateway responses against expected Hermes behavior. The skill guides targeted diagnosis and fixes to restore aligned provider behavior in development and runtime.

The best way to align auth and credential behavior is to use dedicated parity tooling that mirrors Hermes UX semantics. This approach safely aligns configuration semantics and error handling without Python dependencies, reducing provider incidents.

Diagnose endpoint and rate-limit parity gaps whenever Hermes parity discrepancies are detected in development or runtime. Early diagnosis and aligned fixes reduce provider incidents and shorten incident reproduction time for provider-related tasks.