aq-playbooks-and-gateslisted

# aq playbooks + gates Playbooks are deterministic DAGs that fire on bus events (`task.created`, `task.completed`, `spec.approved`, `proposal.ready`, `gate.resolved`). The framework runs them; no LLM is in the compile or dispatch path. Human-in-the-loop gates pause a run until a human answers. ## Inspect playbooks ```bash aq playbook list # every playbook + enabled state aq playbook get-source --playbook-id <id> # the playbook's markdown source aq playbook health # active runs, stuck, failure rate aq playbook show-graph --playbook-id <id> # DAG rendered as ASCII ``` ## Inspect runs ```bash aq playbook list-runs # recent runs across all playbooks aq playbook list-runs --playbook-id <id> --status running aq playbook inspect-run --run-id <run_id> # nodes, statuses, outputs ``` ## Resolve a paused run A run that hit a HITL node parks in status `paused`. Find it, read why it stopped, then hand it the decision: ```bash aq playbook list-runs --status paused # everything awaiting a human aq playbook inspect-run --run-id <run_id> # which node paused, and on what aq playbook resume --run-id <run_id> --human-input "approve" ``` `--human-input` is free text: it is appended to the run's conversation and is what the next transition is evaluated against, so say *approve* / *reject* plus the reason rather than a bare token. Gate rows can also be driven dir