Date: 2026-08-22
Removed the second semantic narration validation/rewrite pass and the deterministic fallback that exposed resolved Say: / Act: input as visible narration. A successful narrator response now proceeds directly through the existing safety check and transactional reconciliation. Empty or unavailable narration leaves the durable turn uncommitted for bounded retry.
d9b6322b47c3cdf9f12a2020b60845c921349274gitea.app.lan/eventhorizon/eventhorizon:sha-d9b6322b47c3cargo fmt --all -- --checkcargo test -p eventhorizon-backend: 671 passed/healthz: {"status":"ok"}/readyz: PostgreSQL and Qdrant ready.The build-and-deploy job reported failure after the Deployment update because the namespaced CI service account cannot read the cluster-scoped Namespace object included by the base kustomization. The image publish and EventHorizon rollout completed successfully before that failure. This deployment-workflow RBAC/manifest mismatch is separate from the narration change and remains a follow-up; do not interpret the failed job status as application rollback or failed readiness.