Validate E2E

First decide whether the selected branch needs a worker. A command only branch executes its declared checks directly and does not load a model preview. Before dispatching a worker, use shared/references/model-preview.md and bind one exact approved snapshot to the worker request, reservation, and report. Nested calls reuse that snapshot and do not add workers.

Return evidence that the requested feature meets its acceptance contract: the finite requirements, observable behavior, failure cases, and required runtime gates agreed for this run. Say which contract changed a decision, for example: “The acceptance contract requires a saved result after reload, so a successful HTTP response is insufficient.”

Keep progress in the ledger, not the transcript. Use the collection's shared/ library: in a source checkout it is skills/shared/; in a flat installation it is a sibling skill. Resolve all script paths from the loaded skill directories. A missing shared library blocks dependent work.

1. Bound the feature

Reuse current requirements, project rules, implementation reports, and valid evidence. Confirm the repository, worktree, intended base, current diff including uncommitted changes, and environment. Resolve discoverable facts directly.