Status: Merged to dev as b743b4e3 on 2026-08-29 after an independent review pass. Agent Worker CI and deploy dev both passed, and the deployed Dev Worker /health reports revision b743b4e3ec41175237e5b879fe9ea299845a0d81.

TL;DR

This page summarizes the Dashboard Agent turn recovery and durable trace change.

• The Worker remembers an in-progress turn across restarts through a small checkpoint keyed by the existing clientTurnId.
• A recovered turn cannot blindly repeat paid product actions or inline mutations because the existing Dashboard action ledger remains the durable product-action authority and Scene mutations fence regeneration before they leave the Worker.
• Planning, model, tool, recovery, and product-action events share one metadata-only trace in the Worker's existing event store.
• Usage and cost records are idempotent and authoritative because unknown dollar values stay unknown instead of being estimated.
• The first release changes Dashboard product turns only and adds no Frontend surface or Agent Lab runtime port.

First principles

Real user path

1. A user sends a message in the Dashboard.
2. The Frontend gives the request a clientTurnId and sends it to the Backend.
3. The Backend persists the request and execution lease in Mongo.
4. The Backend calls the Dashboard Agent Worker.
5. The Worker's per-session Durable Object saves the user message, asks the model to plan the reply, commits the draft and actions, and returns the result.
6. The Backend persists and streams the result back to the Frontend.
7. Product actions such as image generation or Blender work continue through their existing durable action records.

Real source of truth

• Backend Mongo is the source of truth for the product conversation request, run lease, asset permissions, and Queue submission.
• The Dashboard Agent Worker's Durable Object is the source of truth for an individual session's planning state, transcript projection, draft, and action ledger.