v1.1.0 — review-mode deliverables

adveloop now supports an Evaluator-first starting point per deliverable. Each deliverable in .adveloop/deliverables.md carries a Mode field:

• Mode: build (default) — Generator runs first, Evaluator verifies. Existing behavior.
• Mode: review — Evaluator runs first against the existing codebase; if it passes, the deliverable is done with zero Generator runs; if it fails, the verdict becomes the first feedback round and the Gen→Eval loop begins. Use for audits, hardening, and fixing existing code.

A single /adveloop run can mix both — build one deliverable greenfield and review another against the current codebase, in order.

New

• Per-deliverable Mode field in deliverables.md (Planner infers it from intent; user approves or revises).
• Initial-review sub-procedure (R1–R4) in Phase 3 for review-mode deliverables. Skipped entirely for build mode.
• ## Mode: <build|review> header threaded into eval-task.md so the Evaluator prompt branches unambiguously.
• Mode-aware resume classification: review deliverables without gen-result.md resume correctly at round 0 or at Gen round 1 depending on artifacts.
• "Edit deliverable" escalation now restarts a deliverable from the mode branch, so mid-run mode swaps take effect.

Rules that did not change

• The 3-fail retry cap still counts Gen→Eval pairs only — the free initial review does not consume a slot, so review deliverables still get three fix attempts before the Planner escalates.
• Signal naming unchanged. Review mode emits adveloop-<run_id>-eval-done-<N>-0 with no matching gen-done-<N>-0 — no collision.
• Evidence-quality rules unchanged. A review verdict with thin evidence is as invalid as a build verdict with thin evidence.

Backward compatibility

Deliverables without a Mode: field are treated as build. Existing .adveloop/ directories resume unchanged.

Install / update

/plugin marketplace update adveloop

See the README for the updated usage examples and the full deliverable-modes reference.