wait_for_generation

Waits for one aicut generation to reach a terminal state, WITHOUT opening a widget or a card. It waits SERVER-SIDE for up to 15 seconds and returns the job's compact status. terminal is always present: true means the job is succeeded or failed and nothing further will arrive; false means it is still queued or processing. WHEN: immediately after generate_video, generate_image or generate_audio, and again every time it answers terminal: false. WHILE terminal IS FALSE: wait poll_after_seconds and call this tool again with the same id and media. Do not switch to get_video / get_image / get_audio, do not spawn a timer or a background shell, and do not narrate each attempt to the user. A video takes 1-3 minutes, so several calls in a row is the expected shape and costs the user nothing. EXCEPTION - a PARKED story episode: an AI Video Story job whose result carries story.stage: "frames_review" is WAITING FOR THE USER, not for time. It stays terminal: false until it is fired, so stop waiting, show the user the pictures and let them look. What happens next is THEIRS to say: regenerate_story_frame for a scene they dislike, and fire_story_video only on a priced go that names firing the scene videos - reaching the review is not that go. EXCEPTION - a story RENDER: after render_story_video, read story on each result. story.render.status: "failed" means the render failed and was refunded - it will NEVER become terminal, so stop waiting and call render_story_video again. story.stage: "rendered" is the finished state: story.render.url is the final file. A succeeded episode whose stage is still ready_to_render has NOT rendered - its url is only the raw scene preview. WHEN terminal BECOMES TRUE: say ONE short line about what came out, and stop. The generate_* call that started this job already put the aicut card in front of the user and the card has filled itself in, so do NOT call show_generation - that would put a second, duplicate card in the conversation. If status is failed, read error.message and tell the user what went wrong. IF YOU CANNOT RENDER AN AICUT CARD - a terminal, a plain SDK client, anything that did not negotiate the MCP Apps UI extension - then no card appeared and this result is all the user gets: give them the url from it directly. aicut builds a fresh session-less server per request and cannot see which clients render cards, so it sends the same answer to all of them. This tool spends no tokens, opens no card, and creates nothing. OUTPUT: this returns JSON for you to read, not to relay. Say nothing to the user between waits, and never paste this response, the job id or internal field names into the conversation - show_generation is what the user sees.