Skip to main content

​
Release notes

The canonical runtime changelog lives in the system repository at CHANGELOG.md. This page mirrors the operationally important notes for docs readers. For the current runtime topology and compatibility boundary, see current runtime snapshot.

​
0.3.0 — 2026-05-15

  • Added durable worker callback outbox and replay support for transient callback failures.
  • Added queue-alert auto-reconciliation for stale active lanes when a completed decision artifact is present.
  • Added Research Facility quality signals, post-prompt diagnostics, bounded-follow-up prioritization, and janitor candidate review support.
  • Tightened paper-production gates so only explicit positive decisions enter the write-needed lane.
  • Fixed stale active-lane handling, database connection lock release, janitor run-cycle integration, and corpus ledger idempotency.
  • Updated dependency locks and pinned GitHub Actions away from floating major tags.

​
0.2.0 — 2026-05-09

  • Package name changed to enoch-control-plane.
  • Python module changed to enoch_control_plane.
  • FastAPI entrypoint changed to enoch_control_plane.app:app.
  • Preferred config variable is ENOCH_CONFIG; ENOCH_CONTROL_PLANE_CONFIG is accepted when an explicit control-plane name is useful.
  • Preferred API/dashboard token field is control_api_bearer_token.
  • Preferred worker decision artifact path is .enoch/project_decision.json.
  • Legacy .omx/project_decision.json, omx_inbound_bearer_token, and /omx/event remain compatibility surfaces for older runs and integrations.

​
0.1.0 — 2026-05-04

  • Initial Enoch control-plane release with queue state, worker preflight, pause/resume controls, dashboard read models, paper pipeline gates, Supabase-backed runtime ledgers, and public-release validation tooling.

​
Version policy

  • Runtime version is tracked in the system repo VERSION and pyproject.toml.
  • Every runtime release should update CHANGELOG.md and this docs page.
  • /control/api/v1/* is the preferred bounded read API for dashboards and integrations.
  • Broad status and legacy dashboard endpoints are compatibility/debug surfaces unless a page explicitly says otherwise.