Apply with agent freezes one persistent run containing only approved, exactly mapped changes and every affected viewport, theme, and state. Queued for agent means the batch is stored locally. Handoff received means an agent has claimed a renewable lease. Applying source changes is the first state that confirms editing has begun.
If a listener disconnects before source editing begins, Foundry safely returns the run to the queue and blocks the stale claimant from updating it. Reconnect agent restores the listener without creating a duplicate run.
If the agent disappears during source editing, rebuilding, or verification, Foundry preserves the same run in Needs attention. Resume with agent requires your approval, then the next listener must reinspect the current source before continuing. Foundry does not assume that repeating a partial source edit is safe.
If source changed since the reviewed baseline, inspect the changed files and explicitly confirm the current revision before resuming. The original reviewed baseline is preserved; recovery does not revert your files or silently replace the request.
After editing, the agent runs relevant project checks and asks Foundry to reload the rendered surface. Foundry measures the rebuilt result against the requested values, even if Review was closed, reopened, or refreshed during the run.
A run passes only after source changed and every reviewed context returns acknowledged rendered evidence matching the request. If verification finds a mismatch, Foundry explains it and waits for explicit retry authorization.