stroblmeandClaude Fable 5 af3ba51571 Keep the engine's own history, and a screen that reads it ...

A second bus subscriber folds executions, errors, timings and queue lag
into per-minute rollups, keeps failures with their traceback and an audit
trail of who published what, and records one row per cascade — manual runs
and previews included, under an id of their own that writes no idempotency
markers. Read back through /observability/*, which always answers 200 so a
degraded engine still renders its own health screen.

Also fixes two things found on the way: node-health alerts read `status`
where the engine publishes `health`, so a device dropping never alerted
anyone, and the Redis queue reported `parked: 0` whatever was held.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017MeiWk3Yq12n2pTvnQWYvt

2026-08-16 22:29:32 +02:00

..

routes

Keep the engine's own history, and a screen that reads it

2026-08-16 22:29:32 +02:00

__init__.py

Vendor backend and frontend into the monorepo

2026-08-09 15:14:54 +02:00