orchestrate-content-by-steps

Do a content request the RIGHT way, end-to-end, through the frozen development-step process. Use whenever the owner asks for content work — "make me a page about Apple", "add a news section", "add 3 test news", "create a blog". You pass only the INTENT (an action + a topic); this orchestrator DECOMPOSES it by the site's state (does the section exist?) into dependent sub-steps, and runs EACH through the full lifecycle: open a development step → do it → deploy → RECORD the deployment → close the step. The deployment record is a GATE — a step never closes without it (the Vercel invariant). You do NOT chain tools yourself, do NOT decompose by hand, do NOT generate content or code. Prefer this over calling compose / create-page directly for any real owner request.