EventHorizon was corrected after a production game session degraded from persona-led narration into repeated deterministic Nothing new is directly perceptible. responses during upstream inference failures.
Act text.Production telemetry showed repeated HTTP 429 failures across persona, narrator, item-state, and scene-background operations. This was an application failure mode; Kubernetes replicas remained healthy.
Repository: EventHorizon/EventHorizon
460fb068 — Preserve game turns through inference failures7d83c24egitea.app.lan/eventhorizon/eventhorizon:sha-7d83c24ecf26Behavior now:
say and act.cargo test --workspace: 391 backend tests and 11 frontend tests passed.cargo fmt --all -- --check: passed./healthz: {"status":"ok"}./readyz: application, PostgreSQL, and Qdrant ready.0028_inference_provider_health.sql applied; table public.inference_provider_health exists with the expected typed columns.7d83c24ecf26.The provider-health table is normally empty. A row with scope provider exists only while a typed provider-availability cooldown is active. Existing historically persisted fallback messages were not rewritten.
Rollback is the normal repository-managed deployment of the previous known-good image. The additive provider-health table is safe to leave in place during rollback.
At the user's request, the affected live roleplay session was transactionally rewound after the application fix because several failed turns had already been persisted.
2b8c6d5b-74a4-49c5-9c3d-60c6f98b116c4db7150f-cf53-4ec3-909a-432decedb09bc9f14537-3418-4870-9538-cd42433aba5eThe transaction locked the session and aborted unless the expected live turn, authoritative target job/messages, current undo checkpoint, zero active jobs, and absence of post-target inventory/effect/continuity mutations all matched. A full session-scoped JSON backup was checksum-verified before both dry-run and commit.
Post-commit verification confirmed turn 24, the exact target chat pair as latest, zero future session rows, narration-aligned visual context, 2/2 ready application replicas, and healthy PostgreSQL and Qdrant readiness.