approve-templatelisted

# Approve a GraphCompose template Almost no judgement here: the tools own the state machine. The job is to confirm *what* is being approved, run two commands, and report what was published. ## When this applies The user accepts the current render: "approve", "save", "ship it", "looks good", "that's the one", "сохрани", "это хорошо". If they instead say "previous was better", "undo", "revert" — that is rollback, not approval. Use `graphcompose-flow undo` or `revert-approved`; both create a new DRAFT and neither rewrites history. ## Steps **1. Confirm what is being approved.** The user's "approve" refers to the render they just looked at. If the current draft is a different revision than the one last shown, say so instead of approving silently. That confirmation is the only judgement in this skill. **2. Run the composite.** ```bash node scripts/approve-and-publish.mjs --project <project-id> [--root <workspace>] ``` One command does the whole flow — approve (DRAFT → APPROVED, previous APPROVED superseded), publish, generate the bundle README's stable half from `template.json`, verify the bundle, and report the cycle's telemetry — and answers with one result. Do not run the individual commands one at a time; five separate turns for a deterministic chain is what this command exists to remove, and it was measured costing 11 model requests before it existed. What it enforces, so you do not have to: - Only a DRAFT can be approved; anything else is refused with the reason.