Butter

Ask the user what comes next for what endSession built: it renders the card with the next steps, and returns the build report to relay — the project link, what became editable, what did not survive. Call it after repairProject: straight away when it reports nothing to repair, or with `repaired` on the build once its repairs are made. Call it ONCE per request, with every build the request produced in `builds` — one entry even when there is just one; the one card lets the user choose next steps for each — and with `suggestedOptions` when this user's stored preferences point to a step the standard choices do not offer. The card renders below everything said before it.

Ask the user one or more questions in a form: they tap a suggested answer, type their own, or skip. Use it for anything you need before building that the user has not told you, no source gives you and their userPreferences do not settle, and tailor the questions and options to those preferences. It runs inside a live session: first call startSession — or startEditSession when the user wants a built project changed — and pass the sessionId it returned. After calling it, end your turn — the answers arrive as the user's next message.

Duplicate a built Butter project, everything surviving verbatim — custom blocks and studio edits included. Use it when the user wants a new version with small changes while keeping the original: clone, then startEditSession on the clone. A new take that re-authors the video is a fresh startSession instead, informed by describeProject.

Read the current state of a built Butter project — including every edit made in the studio since it was built. Call it before building a variant or adaptation of a project, so those edits carry forward; the session html only knows the project as originally built. Custom blocks and unknown components are listed as opaque references.

Close edit sessions as soon as the requested changes are saved — do not wait for the user to approve first. Call it ONCE per request, with every edit session the request opened in `sessions` — one entry even when there is just one; the one card lets the user choose next steps for each edited project. Each entry carries the summary of what actually changed in that project, and any requested change you could not make in its `failures`. The result renders the next-steps card again, built from each project as its edit left it; the card is how the user reviews and asks for more.

Finish the session and turn a submitted version into an editable Butter project. Call it straight after prepareEndSession, without waiting for the user's approval. It cannot be called until prepareEndSession has been called for the same version: that returns the instructions for building the manifest this takes. A successful result carries only the ids; call repairProject with them next — the project link and the build report reach the user through the card it routes to. A successful endSession ends the session for good: it accepts no further calls, and only repairProject and askNextSteps still take its ids. Any work after it starts a session of its own, the way the next steps route it.

Get the full instructions for one Butter workflow — the questions to ask, what to gather, what to keep and vary, how many videos to make, how to build each one, and the handoff. Follow what it returns exactly.

List the Butter workflows available for making ads and videos, optionally for one intent (create, remix-ad, scale-winners). Returns each workflow title with when to use it; pick one, then call getWorkflow with its title.

Provides the instructions for ending the session: how to measure a submitted version into the manifest endSession requires. Call it as soon as the version you are shipping is submitted with no blocking lint findings, without showing it to the user or waiting for their approval, then call endSession — endSession cannot be called for a version until prepareEndSession has been called for it, and a version with blocking findings is refused.

The next-steps card calls this by itself to refresh project links after one is opened. You never need to call it, and its result carries nothing to relay.