wakeflow-controllerlisted

# Wakeflow Controller Use this skill only from the controller window. `AGENTS.md` owns hard judgment; this skill owns the mechanical loop steps. ## Purpose Wakeflow Delivery Loop lets the controller fan out work to target windows, receive strict TargetResult records, inspect target-authored review inputs, run independent checks, and decide the next package. It does not replace planning, scope control, validation, or acceptance. Direct-thread dispatch is the normal transport. In explicitly enabled unattended mode, keep reviewing results, inspecting inputs, validating, deciding, planning next eligible packages, and dispatching until final completion, a hard gate, explicit user stop, missing review inputs that need human judgment, or no eligible TODO remains. After the host effect, record its exact outcome through `wakeflow_record_delivery operation=target-outcome`. Transport and bounded readback remain separate facts; `pending` or `unavailable` never authorizes a resend or lease release. The controller dispatch turn is then complete. Do not keep the turn open with `sleep`, repeated result review, repeated thread reads, or manual polling. The target returns later through one strict `wakeflow-target-result` TargetResult and, if policy allows, a controller-return delivery. ## Source Practices For Acceptance **Iron Law: NO ACCEPTANCE UNTIL THE CONTROLLER HAS PERSONALLY ESTABLISHED THE INTENDED BEHAVIOR FROM FRESH RAW INPUTS AND INDEPENDENT CHECKS.** A result envelope, a scri