Delivery summaries explain the outcome
Agents close work with a concise account of what changed, what was verified, and what remains.
Overlord keeps the objective, delivery notes, artifacts, and file-change rationales next to the work so reviewers can evaluate whether the result matches the ask, not just whether the diff looks plausible.
Agents close work with a concise account of what changed, what was verified, and what remains.
Meaningful behavioral changes can be described with the reason, impact, and relevant hunks.
Test results, URLs, notes, screenshots, and context references live with the ticket instead of a separate chat.
The activity feed shows the events that happened on the ticket: one checkpoint, an agent update, a user follow-up, the delivery, and the file changes with rationales the reviewer reads next.
Shipped the Checkpoints subpage in Project Settings.
It lists every local git checkpoint Overlord created for the project with commit id,
timestamp, and the objective that triggered it. The list scrolls past 8 rows, each row
has a delete affordance, and a Prune all stale checkpoints action collapses everything
whose objective is complete and whose ref is no longer reachable.
Added a popover next to the prune button per follow-up — it explains what counts as stale in one sentence with an example.
Please add a small popover next to the Prune button that explains what "stale" means — I want reviewers to understand it without reading code.
Scanned lib/actions/checkpoints.ts and the existing project settings modal. Plan: add a new Checkpoints subpage with a scrollable table, a per-row delete, and a Prune all stale button. Stale = checkpoints whose objective is complete and whose ref no longer points to a reachable commit.
Created local git checkpoint for objective manage-checkpoints.
Agent-readable detail
Agents should explain behavioral changes in review language: what changed, why it changed, impact, and verification.