graph-running

# Graph running Run an approved graph the way it was drawn. The graph-engineering skill designs the work and stops at approval. This skill picks up from there. ## Start only from an approved graph You need three things from graph-engineering before you begin: the confirmed alignment contract, the graph with each job's owner and output, and the user's approval of that graph. If any is missing, go back to `claude-vibes:graph-engineering`. Do not improvise a graph here, because a graph nobody approved has no authority to guide the work. Approval of the graph is not approval of every step in it. Each human gate in the graph still needs its own yes at the moment the work reaches it. ## Save the graph before running it If the approved graph recommends manual lanes, a shared note the user keeps is enough. Otherwise write the graph to a file first, so the work survives a closed session and anyone can see what was decided and why. - A whole-project graph lives in `docs/01-START/roadmap.md`, which the `04-plan-roadmap` command writes and the `05-track-progress` command maintains. Use that file's format and do not create a second one. - Any other graph goes in `docs/graphs/<short-name>.md`, with these sections: the alignment contract, the diagram, a checklist with one line per job (owner, what it depends on, its output, any gate), a "State" section that collects each job's result, and a dated change log. Run `date +%Y-%m-%d` before writing a date. ## Run the jobs 1. **Follow t...