Take any Aseprite request end to end

The other workflows each do one thing well. This one decides which of them the request needs, runs them in the order that keeps mistakes cheap, and owns the result until it is finished. It does not replace them: at every step, read the workflow it names and follow that, do not do the step from memory.

Procedure

1. Pick the Aseprite, then preflight. Two places the work can happen: live, the user's open window, which they watch and can undo; or headless, a batch Aseprite this server runs with no window, where the only results are your look previews and the files you save. Decide before the first call, from the request, see Live or headless below, and pass it: preflight mode="headless" or preflight mode="live". When the request says nothing either way, call preflight without mode and keep the mode the server started in.

   If not ready, stop and tell the user what to fix. Nothing below works without Aseprite, and editing files on disk instead is never an acceptable recovery. In headless there is no window: show previews as you go and save (sprite_manage op save_as) before reporting.

2. Read the room. sprite_info on whatever is open. An open sprite changes the plan: "make it bigger" means a sprite that exists, and its canvas and palette answer questions you would otherwise have to ask.

3. Classify the request against the table below. Most requests are one row; a big one ("animated knight, export for Godot") chains several. Write the chain down before starting, it is the plan you report progress against.