Rolled out EventHorizon commit ca273f78b36a with image gitea.app.lan/eventhorizon/eventhorizon:sha-ca273f78b36a.
Follow-up rollout published commit 820231446b3a with image gitea.app.lan/eventhorizon/eventhorizon:sha-820231446b3a so frontend turn details expose every active AI entity action returned by the backend.
canonical_profile, template_profile, inner_state.template_profile, actor_view, and ai_view when available, so ambiguous visible items can still have stable operational identity for AI/rule use.turn.entities[] action with the entity name, falling back to the legacy persona debug field only when no entity list is present.Initial rollout:
cargo fmtcargo check -p eventhorizon-frontend --target wasm32-unknown-unknowncargo test -p eventhorizon-backend passed: 136 tests.sha256:82c2b5b6ef14bbef2a4d244215fc92a406d6fc31f347f577179cb071ab5fb5f6.event-horizon/event-horizon rolled out successfully.event-horizon-86c9f69646-wxwpk, image gitea.app.lan/eventhorizon/eventhorizon:sha-ca273f78b36a, ready 1/1./healthz returned {"status":"ok"} and /readyz returned ready for Postgres and Qdrant.Follow-up rollout:
cargo fmtcargo test -p eventhorizon-backend narrator_turn_prompt_lists_each_active_entity_action -- --nocapturecargo check -p eventhorizon-frontend --target wasm32-unknown-unknowncargo test -p eventhorizon-backend passed: 137 tests.sha256:413aa2d3dd2b6fedd40bb515ca7e817e3b0a66084c34c4b357aa4554b6cee635.event-horizon/event-horizon rolled out successfully.gitea.app.lan/eventhorizon/eventhorizon:sha-820231446b3a, ready 1/1./healthz returned {"status":"ok"} and /readyz returned ready for Postgres and Qdrant.The bare /health path returns 404; the deployed application exposes /healthz and /readyz, matching the Kubernetes probes.