[kasvith]

Summary

The v1 work: operator controls, observability and workflow timeouts in the engine,
and a dashboard redesign built on them, with page tests for every screen.
13 commits, ordered so each one builds on its own (core and dashboard commits were
compiled and tested one by one).

Engine

• Operator controls — Durable.retry/2 resumes a failed run from its failed step
  with a fresh attempt budget; Durable.rerun/2 starts a new run with the same (or
  edited) input, linked back. Runs record what started them (trigger: api, schedule,
  parent, rerun). Cancel uses a status compare-and-set. Queues can be paused and
  resumed across every node.
• Workflow options — evaluated at compile time; unknown options fail the compile.
  timeout: is enforced (a run past its deadline fails before its next step, through
  the normal path, so compensations run; waiting runs are woken and failed). queue:
  is honoured.
• Observability — Durable.Telemetry (documented events, Telemetry.Metrics
  definitions, an optional default logger), Durable.Stats, Durable.Activity (what
  Durable did on its own), a node registry, a per-minute queue sampler and a pruner.
• Errors — exceptions, exits and throws are stored as type, readable message and
  stack (file and line per frame) for steps, compensations, the worker and a branch's
  on:.
• Fixes
  • Parallel and branch block ids are stable across compiles; they changed on every
    compile, which broke resuming suspended runs after a deploy.
  • Re-enabling a schedule no longer crashes.
  • A resumed run keeps its first started_at; it was overwritten on every resume,
    which skewed durations and queue wait.
  • Durable's own log lines no longer land in a step's captured logs.

⚠️ Requires migrations. v20261016000000_add_operator_controls and
v20261016000001_add_deadlines_and_history. Run Durable.Migration.up() (the demo's
upgrade migrations are included as examples).

⚠️ Behaviour changes.

• Unknown workflow options now fail the compile (:max_retries is gone).
• timeout: is enforced.
• A run's started_at is its first start, not its last resume.

Dashboard

Every page reworked against DESIGN.md, in dark and light:

• Overview: KPIs, charts, failing workflows, slowest steps and a live feed.
• Runs:
  • A query bar that holds every filter as a tag, with typing suggestions.
  • Saved views, and a bulk bar that floats over the list.
  • New runs wait behind a pill instead of shifting the rows.
• A run's page:
  • Trace waterfall, and a graph whose parallel blocks end in a join node and whose branches have gateway nodes.
  • One step inspector shared by both views, showing the error with a readable stack.
  • Logs, Context and Family views.
• Workflows: a page per workflow with a structure map.
• Operations:
  • Inbox, Queues & nodes (pause and resume, backlog history), and Schedules (on/off, a page per schedule).
  • Telemetry and Settings pages.
• Across the dashboard:
  • One styled tooltip, including chart data points.
  • ⌘K finds pages, saved views, workflows, schedules and any run by id.
  • Access levels (viewer, operator, admin) via a resolver, with an audit telemetry event per action.

Tests: DurableDashboard.LiveCase mounts the real LiveViews against a Durable
instance on Postgres, with runs from real workflows executed inline. 237 dashboard
tests, including access enforced server-side. The dashboard CI job gets a Postgres
service.

Demo

Adopts the v1 schema; adds a resolver (the demo user is an admin), telemetry (Durable's
logger, the dashboard audit log, Durable's metrics) and LiveDashboard at /dev/dashboard.
Moves to phoenix_live_view ~> 1.2.

Notes

• The dashboard depends on durable as a path dependency on this branch: it needs
  core APIs that aren't on Hex yet. Switch back to Hex with the core release.
• Dashboard tests now need Postgres locally: docker compose up -d (port 54321).
• Known follow-ups:
  • A workflow's deadline can't interrupt a step that's still running.
  • An input with on_timeout: :fail still ends its run as cancelled.
  • The graph doesn't draw compensation steps.

Test plan

• durable: mix test (483), mix credo --strict, mix compile --warnings-as-errors
• durable_dashboard: mix test (237, three runs in a row), tsc --noEmit, biome check
• Every page and run view loads (HTTP sweep of 58 URLs against the demo)
• Walked every page in the browser, dark and light; exercised rerun, queue pause/resume, an inbox approval and schedule on/off