A dated record of every behavior-changing release. Categorized additions, behavior changes, and fixes. Entries are written in the language a DMZAgent operator uses when discussing the system; not marketing copy.
POST /v1/connector-instances/{id}/run now returns a 202 with a queued job id; the connector → delegate → reasoning pipeline runs in a background worker. The dashboard subscribes to a per-job Server-Sent Events stream so the run-for-real chip animates from queued to running to terminal in real time.
Recent Jobs panel updates without polling. Container restarts recover orphaned jobs at boot: in-flight rows are marked failed, queued rows are re-enqueued.
Service operators can edit free allowances, per-unit rates, and volume tier breakpoints from the dashboard at /service-admin/rates. Every publish writes to the platform ledger as a controlled record, snapshots the canonical JSON to R2 (current + versioned + history), and fires the marketing-site rebuild webhook so the pricing page reflects the new schedule within minutes.
The customer billing usage page and the rate card on dmzagent.com both read from the same R2 source — a rate change can no longer drift between the live bill and the public schedule.
The reasoning core now runs as a managed container fronted by our edge-hosted Worker, replacing the prior cloud-managed deployment. One-provider stack, no cross-internet seam between the dashboard and the reasoning core, and live tail logs surfaced in the operator console for every request and every container stdout line.
Every product surface — analyst dashboard, marketing site, docs — was relaid on a shared federal-records visual system: white paper background, federal navy 0a2540, treasury red c8102e for hairline accents, Public Sans for body, JetBrains Mono for identifiers. The codex is the source of truth; the surfaces present it.