@starreel/mcp 0.1.257 → 0.1.259

package/SKILL.md

@@ -94,6 +94,7 @@ announces a condensed version as MCP `instructions` at connect time.
 | Their own portraits / scene / prop / shot images | `upload_image` · `set_character_portrait` · `upload_scene_image` · `upload_prop_sheet` · `upload_shot_frame` — **check the image before uploading** (see *Customer-supplied images* below); after a portrait swap, `generate_character_sheet` for that character (the old sheet is invalidated and **not** regenerated automatically) | rendering a "fix" elsewhere and uploading it — use `generate_shot_frame`; uploading a group photo, a captioned/watermarked image, or a multi-view sheet as a portrait; uploading a scene photo with people in it |
 | Their own **footage** for a shot (screen recording, product b-roll, an existing clip) | `upload_shot_footage` → that shot is no longer AI-generated (frames/video skipped, final cut uses the clip as-is, duration written back from the clip); **it overwrites whatever AI video that shot already had**, and afterwards every AI video call on it (including `edit_video_shot`) is refused with **409** until you `clear_shot_footage` or pass `replace_user_footage: true` | pasting an externally AI-generated clip to "fix" a shot — it carries none of this film's identity / style anchors; use `regenerate_shot_video` instead |
 | A **greybox / 3D previs** or any clip whose motion, camera move and blocking a shot should be **generated from** | `create_motion_reference` (greybox: `kind` = `greybox_coarse` / `greybox_fine`) → `attach_motion_reference` — with several proxies pass `greybox_bindings` (which coloured proxy is which character) → `quote_videos` / `generate_videos` as usual; the shot's first/last frames are not sent and identity comes from the character references. Coarse greyboxes built from simple primitives work best; keep trail lines / axes / camera frustums out of fine greyboxes | `upload_shot_footage` (that makes the clip the finished shot); a greybox with several characters and no bindings — identities get swapped |
+| Shot size / camera move / blocking keep coming out wrong and the client has **no greybox** | `generate_greybox_previs` (`dry_run=true` first to see which fields and fallbacks it uses; fix fields with `update_shot`) — the platform renders a coarse greybox from the storyboard fields and fills `greybox_bindings` → `get_greybox_previs` → `review_frames` → `quote_videos` / `generate_videos`. Tell the client first: first/last frames are not sent and the video quote rises by about 20% | Using it on insert shots, shots with no on-screen character, shots over 15 s or state-change shots (it returns the reason instead) |
 | A clip that should **drive the motion** of an AI shot (a blocking/previz pass, a dance or action reference) | `edit_video_shot` with `reference_video_urls` — the shot keeps its AI video and borrows the clip's movement. To make the clip itself the source and restyle it in place, `upload_shot_footage` it first, then `edit_video_shot` with `replace_user_footage: true` | `upload_shot_footage` alone — that registers the clip as the finished shot, so nothing gets restyled and every later AI call on it returns 409 |
 | A clip whose **motion should be kept while the people / outfits are redrawn** (video repaint) — their own footage or a shot already generated here | `get_repaint_capabilities` (is it enabled for this drama; `relayMaxSegments`) → for their own clip, `upload_shot_footage` it onto a shot first → `quote_repaint_shot_video` → `repaint_shot_video` (prompt + reference image; with no `reference_image_url` the shot's character portrait is used — without any reference the person is redrawn too) **or** `quote_reskin_shot_video` → `reskin_shot_video` (`first_frame_url` = an already-reskinned first frame that matches the original first frame's composition, pose and props exactly) → `get_repaint_status` with the returned id until `completed` → `restore_repaint_original` to switch back (free). Motion, lip timing and camera move follow the source and its audio is carried over. ≤5 s is one charge (billed as 5 s); with long-shot relay enabled, 5–~14 s is split into ≤3 relayed segments, one charge each, and the quote is the total and the charge cap. A quote is tied to the shot's current video — if that video changes, generating returns 409; re-quote (free) | `edit_video_shot` to swap the whole cast or wardrobe (it edits by instruction); clips longer than ~14 s (`split_shot` first) |
 | `review_storyboards` reports `forbidden_term` (light / color-temperature / BGM wording in the shot text) | every hit is listed at once in the finding's `hits` (`shot`, `field`, `term`) → `get_shot_prompts` to read that field (`description` is returned there too) → `update_shot` to remove the term from that field; if the intent is lighting, move it to `update_shot`'s `lighting` field (not scanned, and video / image generation read it); a hit with `field=sound_effect` is fixed with `update_shot`'s `sound_effect` field (its current value is in `get_shot_prompts` too) → `review_storyboards` again | rewriting the whole shot blind, or putting the lighting back into `description` / prompts in other words |
@@ -230,6 +231,15 @@ Don't ask the user at every step. Sort work into three tiers:
    `video_style_prompt`) are all free and the foundation that steers every later
    generation. Set them up front via `create_drama` / `update_project_settings`
    — don't build an empty shell, or all downstream generation drifts.
+   **Free aspect ratio (Seedance 2.5 only, rolled out per drama).** Besides the
+   fixed presets, `aspect_ratio` accepts a number such as `2.35` (or `"2.35:1"`
+   / `"47:20"`, width÷height within 0.4–2.5). It requires `video_engine`
+   `seedance-2.5`, a Seedream `image_model` and a non-4k resolution; the video
+   follows the first-frame size, so every shot needs a first frame — scene
+   groups, reference-to-video, keyframe groups and text-to-video can't use it.
+   A drama that isn't enabled gets a 400: tell the user and pick a fixed preset.
+   At creation it only works once fully rolled out — otherwise create with a
+   fixed preset, then change it with `update_project_settings`.
    **Honor explicit creative requirements.** `creative_contract` on
    `create_drama` / `update_project_settings` accepts `version: 1`, optional
    `speech` (`unspecified` / `forbidden` / `required`), `music`

package/dist/i18n/tools.en.json

@@ -1,7 +1,7 @@
 {
   "get_capabilities_guide": "★Capability map (free · local · offline · no credits). **Call this first when you are new to this server, when a client asks “what can you do / where should we start”, or when you are unsure which tool fits the client’s materials**. Returns: entry_points(client has novel / mature script / wants external AI rewrite / finished storyboard table / own assets / voice sample / song / product / existing final cut to revise / wants to edit locally / multilingual → which tools to use and which path to avoid), pipeline(10-step production line, tools per step, free vs paid, review gates), review_gates(three free hard-gate rules), qa_tools(pick diagnostics and fixes by symptom), optional_boosts(optional enhancements and timing), billing(quote confirmation and free families), common_requests(client wording → action), local_postproduction(★full workflow when client wants to download shots to **their own computer** for color grading / third-party AI post / editing / scoring / subtitle burn-in / transition optimization / narration patch: phase order, execution location, per-shot/per-line audio checks, acceptance criteria), model_guide(★tested pros/cons, prices, selection steps and recommended combinations for image models and video engines—read before project model selection or when client asks “which model is better / why are hands bad / how to save money”), action_film(★workflow for action / fight / skill-demo films: asset images follow the rewrite backbone while storyboards use your own table, first frame freezes at wind-up, group adjacent action shots, trim draggy tails, engine tests and cost reference—read before action films or “can this reference video be made”). Pass section to fetch one part only. ★Tool descriptions answer “what does this tool do”; this tool answers “when should I use which tool”. If a client gives a finished storyboard table but you run set_script→rewrite_script and turn it into prose, you skipped this map.",
   "list_project_options": "List all project creation options: project type(short drama/ad/MV/brand film), aspect ratio, video resolution, video engine(Seedance 2.5/MiniMax H3, with price and capability differences), with Chinese/English labels + descriptions + defaults. Call before create_drama, let the user choose, then pass keys to create_drama. Free.",
-  "create_drama": "Create a new short-drama project shell. ★Strongly recommended: set base project settings at creation—project_type/setting_brief(worldview · ERA LOCK)/ethnicity/aspect ratio/resolution, plus consistency anchors(cinematography_prompt/art_bible/visual_lock). All are free and form the foundation for full-pipeline consistency; creating an empty shell with title only will derail later generations and cause paid rework. Automatically creates N empty episodes from total_episodes, returns drama_id and episode_id per episode. Free.",
+  "create_drama": "Create a new short-drama project shell. ★Strongly recommended: set base project settings at creation—project_type/setting_brief(worldview · ERA LOCK)/ethnicity/aspect ratio/resolution, plus consistency anchors(cinematography_prompt/art_bible/visual_lock). All are free and form the foundation for full-pipeline consistency; creating an empty shell with title only will derail later generations and cause paid rework. Automatically creates N empty episodes from total_episodes, returns drama_id and episode_id per episode. Free. ★Seedance 2.5 dramas can use a free aspect ratio (e.g. 2.35); see the aspect_ratio parameter for limits and the per-drama rollout.",
   "set_script": "Set the **original script** (content) for an episode. This is the input for AI rewriting, not the final shootable draft. Free. Put synopsis/outline/self-written finished draft here; after setting it you **must call rewrite_script for AI rewriting**—do not skip rewriting and paste the draft directly into edit_rewritten_script (it will be rejected). ★★【Execution-mode master guide·read before starting】For dramas with a confirmed opening plan, first call get_production_plan and read autopilot: professional mode (pro, or autopilot.enabled=false, or plan not confirmed) → every later “tell the customer; proceed only after customer agrees” is literal; one-click (auto)/hybrid (custom) **managed stages** → do not ask the customer: proceed in order by get_pipeline_status next_action, self-confirm quotes within the hard budget cap, and after each layer still run review_* + agent QC; the review/QC returned autopilot.next_step tells you how to proceed for that layer (whitelisted error with auto_acknowledge:true / self-fix round number / pause and ask customer), follow it; for choices follow autopilot.default_decisions; autopilot.never_auto_actions (mode=replace, delete assets, overwrite customer-uploaded images, allow_era_ref_conflict, voice cloning, delivery acceptance) always require customer approval in every mode. ★In managed stages, re-generating frames for the same shot (generate_shot_frame) is capped at 3 rounds, re-generating videos (regenerate_shot_video / edit_video_shot) capped at 3 times; at the cap the platform returns 409 AUTOPILOT_SHOT_REGEN_LIMIT (no charge)—do not bypass with another tool; stop and ask the customer: if they agree to more, quote normally and pass customer_approved_more_regens:true when generating (grants another cap); if they accept the current result, continue, and pass acknowledge_review:true on the next paid call to record confirmation. 402 BUDGET_WOULD_EXCEED / 409 MODEL_UNAVAILABLE / 409 AUTOPILOT_SHOT_REGEN_LIMIT / 400 AUTOPILOT_MUST_ASK with must_ask_customer=true / non-empty pending_questions → pause and ask the customer **once with a consolidated summary** of get_autopilot_log pending_questions; customer-controlled stages follow professional-mode asking. After final cut, deliver to customer using get_autopilot_log report. ★Three-tier execution strategy (do not mix the tiers when asking the customer): ①【Basic project settings·free·mandatory foundation·set when creating the drama; do not create an empty shell】project_type/setting_brief (worldview·ERA LOCK)/ethnicity/aspect ratio and resolution, plus consistency anchors cinematography_prompt (cinematography DNA)·art_bible (art bible)·visual_lock (visual lock)—all free, the foundation driving full-chain consistency; if not set, all later generation drifts and rework costs money. Set directly with create_drama/update_project_settings. ★visual_lock/art_bible should only contain frame-level/world-level locks (camera language·environment·art tone·forbidden elements), **never pin clothing/hairstyle/appearance details for specific characters**—the only source of truth for character appearance is the character profiles from extract_assets (change via update_character); writing both inevitably conflicts: character sheets vs profiles, concept images vs visual lock, consistency gates reject by character sheet → concept images/shot frames get **structurally rejected repeatedly**, no number of rerolls will pass, pure wasted spend. ★★【Era contract·free·mandatory before image generation for non-contemporary or surreal subjects】The worldview in setting_brief is **free text**, only provides background and cannot constrain images; the real override stronger than visual lock is the **structured era contract**: use set_era_contract to set the episode tier (modern/republican/historical/fantasy/surreal), get_era_contract to read current value. **Unset means empty**—the platform can only stack words in prompts; modern objects appearing in ancient images, scene images rendered in the wrong era, are mostly caused by this being empty. ★Xianxia/fantasy/wonderland types **must use fantasy, not historical**: historical demands evidence-based realism and will mark glowing aura, floating terrain, non-human forms as “not era-compliant”, pulling images toward realistic antiquity. For a single scene exception (e.g. modern flashback in a fantasy world), use update_scene era_contract to override; scene-level overrides episode-level. ★★【Per-stage review protocol·all free·main line preventing waste, not optional】After each stage output, review first, tell the customer the conclusion verbatim, then proceed. **Five hard gates (failing causes 400 rejection; ④⑤ and agent QC below)**: ① after rewritten draft → review_script (before extract_assets / generate_storyboards); ② after storyboards → review_storyboards (before generate_frames); ③ after shot images → review_frames (before generate_videos). Each review returns review_token; pass it to downstream paid tools. Explain findings one by one to customer (code=issue type·shots=hit shot numbers·action=which tool to fix with); after fixing per action, **review again** before proceeding. If content changes after review → token invalidates automatically; re-review once (free). error blocks by default; only if the customer is explicitly informed and insists may you pass acknowledge_review:true (acknowledge_review only means the customer personally agreed; every execution mode requires explicit customer agreement, including managed). Managed stages may use auto_acknowledge:true only for whitelisted heuristic errors (see 【Execution-mode master guide】). **Soft guidance (non-blocking but strongly recommended, also free)**: before image/video generation run run_precheck (finds shots vendors will reject, prevents wasted spend)—★**for whole-drama scan, first run run_drama_precheck** (drama-level summary·free·read-only): get issue counts per episode and attention (which episodes to fix first), prioritize accordingly, then run run_precheck on those episodes for details; do not blindly scan episode by episode. Note not_covered—the drama-level scan skips the only lint requiring images; “0 drama issues” ≠ “everything checked”. ★After issues are found, do not blindly edit yourself: plan_precheck_fix lets the platform compute proposals → apply_precheck_fix commits selected ones (for managed=accept all according to execution mode: professional mode / unconfirmed plan / customer-controlled current stage → tell customer and proceed only after agreement; do not decide for them; managed current stage → do not ask, follow get_production_plan autopilot.default_decisions, platform records in get_autopilot_log); after storyboards run get_health_report; after character sheets are done use get_characters to verify every on-screen character has image/sheet; after frames use get_storyboards to inspect frame_status and fail_reason/fail_hint (fix failed shots before continuing; do not make videos from bad frames); after videos inspect video_status similarly; before final cut use get_pipeline_status to confirm no missing shots. ★**Never generate all the way through blindly**: pushing generate calls without review amplifies issues at every layer and can waste the whole episode; every image/video rework is charged. Reviews are all free; catching issues costs nothing. ★Changing clothing edits structured bindings: update_shot active_wardrobe_id (whole shot) / appearance_wardrobes (per character in multi-character shots), can override or clear—text description changes do not change clothes, and the customer need not edit on the website. ②【Production mainline·in order, no skipping·★storyboard before assets】set_script→rewrite_script→★review_script→extract_assets→storyboards (storyboard first·pure-text shot breakdown)→★review_storyboards→★Script discipline (endpoint-enforced, cannot be bypassed): all raw material (synopsis/outline/finished draft) goes in set_script, **must pass rewrite_script to produce the AI rewritten draft**—pasting a self-written script directly into edit_rewritten_script to bypass rewriting will be rejected with 400 (without a rewritten draft there is nothing to edit); extract_assets also requires the rewritten draft. All post-rewrite edits must use AI-output structured formats: script edits via edit_rewritten_script (polish/correct), character profiles via update_character, storyboards via update_shot/replace_shot_dialogue—do not replace the whole script again or write a second truth source in settings; conflicting truth sources are the #1 consistency accident. ★★**After one successful rewrite, do not rerun rewrite_script**: it restarts from the whole original, discards all current fixes, and the new version is not guaranteed to preserve fixed parts (three-version tests oscillate). To fix, use edit_rewritten_script targeted edits (get_script full text → change only those scenes, copy all else verbatim → submit whole text), free, instant, deterministic; if rerun by mistake, use get_script(include_previous=1) to recover the previous version. generate_portraits_and_sheets (character sheets + turnaround sheets·build after storyboards: first use delete_character to delete on-screen characters that **do not appear in any episode of the whole drama and are not planned for later episodes** before image generation—characters are drama-level; after deletion, every episode’s frame assembly will no longer include them; you cannot judge by this episode’s storyboards alone, keep if unsure (one character sheet costs far less than losing an identity anchor in a later episode); this step generates images for **all undeleted on-screen characters**, regardless of storyboard binding, and charges for all kept characters; off-screen voice characters (char_type=voiceover narrator/phone voice) do not get images and have no storyboard binding, **do not delete them**, dubbing still needs them)→★generate_color_script (color script·unified grading)→assign_voices (assign voice colors; if narrator/character library has no suitable voice → design_voice by description, then set_character_voice after sample confirmation)→★quote_scene_images+generate_scene_images (empty scene plates·mandatory before frames)→frames (default only first frames)→★tail_frame_plan (free·which shots need independent last frames)→frames(frame_type=last_frame)→★chain_frames (seams·dry_run:true first)→★review_frames→videos→generate_tts→compose; ★★【Do not skip seams·after last frames complete, before review_frames】After first/last frames are ready, call chain_frames(dry_run:true, free) to see the platform seam plan and estimated_points (copy free, reframe costs one image per seam), tell customer and after confirmation execute without dry_run; already chained seams are excluded from the plan, repeated calls do not double-charge. ★After execution, reframe is **async image generation**: use get_jobs to watch the first_frame generation rows for shots in the plan, wait until all pending/processing finish (for failed, inspect error_msg; use chain_shot_from for a single seam), then run review_frames—while the old first frame remains, get_storyboards frame_status is still ready and cannot show whether the new image is generating or failed. After get_jobs is clear, use get_storyboards to verify seam_state: replacement images rejected during promotion are not kept in get_jobs, that seam remains unchained (review_frames also reports seam_unchained); reconnect per its action. If you review before it lands, you review the old first frame; the token invalidates when the new first frame lands. Episodes with per-shot/batch frame generation usually were not auto-chained (get_storyboards seam_state=unchained means this); skipping it does not error—the cost is discontinuity between shots and jump cuts in final cut. ★★【Do not skip last frames·frame generation is two-pass】generate_frames defaults to first frames only. About 30% of shots have **end state ≠ start state** (large camera move/object released/state change); these need an independent last frame, and the criterion is platform-side, not guessable from storyboard text—therefore after first frames finish you must call the free tail_frame_plan once for the per-shot list, then fill with frame_type=last_frame (shots_needing_last_frame in generate_frames response is this number; if not 0, do not go directly to review_frames). Skipping does not error or block—the cost is those videos having only the first frame as anchor, leaving end state to the model: action incomplete, large camera moves end by returning to start composition. Production tests: in 32 episodes, 30 generated only first frames; 23 of those proceeded all the way through video. ★★【When last frames are blocked by TERMINAL_DESC_GATE: edit text, do not retry】For shots reporting “this shot is marked as state change but nowhere says what it looks like at the end”, use update_shot to write **what the image looks like at the end** into that shot’s last_frame_prompt, then regenerate the last frame. ★Better: **avoid hitting it**—before last frames, call get_storyboards and list all terminal_desc_missing=true shots for the episode at once (free), fill their last_frame_prompt first, then generate; zero rejections needed. Per-shot also possible via get_shot_prompts same field, but do not do that for dozens of shots. Retrying without the description is ineffective—the vendor prompt has no terminal-state segment, so it still draws the first-frame pose and will fail terminal review again, with normal charges each time (production test: last-frame success 9.4% without terminal text, 40.2% with it). Only for shots that truly “almost do not change” use generate_shot_frame allow_missing_terminal. ★★【Do not skip empty scene plates·third parties often miss this】Scene images are **background anchors**: every shot frame in the same scene anchors to them. Frames can still be generated without plates, with no error and no block—the cost is **the first shot of every scene has no background anchor at all** (platform fallback is “if missing image is discovered, generate one in background”; that generated plate is used by later shots in the same scene, but the triggering first shot cannot wait for it), and the first shot is often the tone-setting shot; backgrounds also drift among later shots. They pair with character sheets: character sheets anchor people, scene images anchor environments; whichever is missing drifts. Progress self-check: generate_scene_images step in get_pipeline_status (completed/total); review_storyboards also reports scene_plate_missing before frames. ★★【Do not skip turnaround sheets·character sheet ≠ turnaround sheet】A character sheet is a single-person single-image identity anchor; a turnaround sheet is a multi-view turnaround generated by the platform from the character sheet, the root consistency anchor for shot frames/videos (angle changes·lighting changes·clothing mostly depend on it). Frames can still be generated with only character sheets, no error—the cost is characters drift when angle changes and clothing differs every shot. Use generate_portraits_and_sheets for one-click two-step (each call advances one step; after character sheets are complete, call again to generate turnaround sheets), or call generate_character_sheets after character sheets. Progress self-check: get_pipeline_status generate_character_sheets step (completed/total, portrait_only=characters with only character sheets). ★Customer-provided images: character sheets must be single person, single image, single angle, no text; scene images must be empty scenes with no people and no overlay text—set_character_portrait/upload_scene_image auto-check and reject noncompliance with 422. ★Do not build character images/prop sheets/motion templates before storyboards—storyboards are pure text and need no images; the cast is finalized after storyboards, so delete non-appearing characters first to save (motion templates also must be after storyboards). Paid steps follow current quote confirmation flow. Ads additionally need add_product+generate_product_sheet; MV uses set_mv_lyrics→generate_mv_story→generate_mv_script (if no existing song: after set_mv_lyrics first suggest_mv_song_styles→quote_mv_song→generate_mv_song→get_mv_song→select_mv_song). ★★【④⑤ two new hard gates + agent personal QC】④ asset layer: after character sheets/turnaround sheets/scene images/prop images → review_assets (before generate_frames / generate_shot_frame; its token is asset_review_token and is passed together with the storyboard-layer review_token); ⑤ video and audio layer: after videos/dubbing/music → review_videos (before compose_episode); after final cut run review_final_cut. ★After every layer review you must also **personally QC**: follow returned agent_qc, inspect assets one by one (download images, sample video frames, read text), answer the checklist, submit via submit_qc_report; for grayscale dramas, without the report the review_token cannot enter the next step; report issues block by default like errors. The platform judges existence; you judge likeness and correctness. ★★【Single-shot path is also gated】generate_shot_frame must also pass storyboard-layer review_token; regenerate_shot_video must also pass shot-image-layer review_token—do not expect per-shot tools to bypass reviews (a tested workflow generated all 25 shots by single-shot frames without any gate; all final-cut rework cost real credits). Generating frames does **not** invalidate storyboard-layer token (fingerprint only looks at storyboard content); only changing storyboard content—update_shot / import / add-delete shots / change character bindings—requires one free quick re-review. Generating one shot’s frame invalidates the **shot-image-layer** token; before regenerate_shot_video for the next shot, run review_frames once. ★★【For native-audio dramas, lock voices before batch videos】When use_clip_audio=true (default), each shot’s voice is sampled separately by the video vendor; without locking, it will drift and later unification requires per-shot video regeneration. If customer-authorized source audio exists → clone_voice+set_character_voice before generate_videos; otherwise → for each speaking character first use single-shot quote_regenerate_shot_video→regenerate_shot_video to generate one shot with longer dialogue (generate_videos has no per-shot parameters and only batch-fills missing videos; single-shot regeneration also works for shots with no video yet), use set_voice_anchor_from_shot to choose that voice line, then generate remaining shots. get_pipeline_status native_voice_anchor lists unanchored_speakers still unlocked and stale_shots generated before locking that need regeneration. ★Worldview concept image = mandatory by default (improves whole-drama consistency; many third-party platforms miss this): after storyboards, call generate_world_concept by default, still following quote confirmation (tell customer estimated credits, confirm before charging)—do not silently charge, and do not skip. ★★【Color script】generate_color_script unifies grading across the whole film, done after storyboards and before frames; text step has no quote_* and is postpaid by usage. Progress self-check: get_pipeline_status generate_color_script; review_storyboards reports color-script gaps. ★Motion templates are optional experimental: call generate_motion_templates (motion template extraction) only when the customer explicitly requests it, after storyboards; text step postpaid by usage. First/last frames do not inject motion templates by default; missing templates do not need backfill and do not block images/videos/final cut. Video templates may be cropped; no delivery or gain is guaranteed. ★Scene Bible (detailed scene settings) order is **after scene images are generated**—complete it based on finished scene images (no MCP tool yet; do on official site); do not do Scene Bible before scene images. ★Audio defaults to video native audio (use_clip_audio on by default; skip TTS and use AI video’s built-in audio): when creating/updating a drama, the AI should proactively tell the customer “Default uses video native audio; if TTS dubbing is needed set use_clip_audio to false” and let them choose. ★Default image model is ChatGPT Image 2.5 Flare (gpt-image-2.5-flare·unified whole-drama style): set image_model in create_drama/update_project_settings; omitted means this default; options: gpt-image-2.5-sunburst (same price·more accurate Chinese glyphs/details)/gemini-3.1-flash-image (Nano Banana 2·71 credits)/gemini-3-pro-image (Nano Banana Pro·more detailed·175 credits)/gemini-3.1-flash-lite-image (Nano Banana 2 Lite·cheap·31 credits)/doubao-seedream-5-0-260128 (Seedream5.0); generate_frames can temporarily override for one run. ★2.5 charges by input volume (base 11 credits + 18 credits per reference image), Nano Banana/Seedream are flat-price—budget must include this for shots with many references. ★Four video engine choices (drama-level·when AI creates a drama it must proactively guide selection by genre and show price differences for customer decision):【Selection decision tree】★Call get_production_menu first: whether each engine is currently available for realistic live-action / anime and other subject classes is decided by the availability it returns (unavailable entries carry customer_note and expected_until—relay them to the customer verbatim); do not assume from this description that any model is unavailable, and do not recommend models the menu marks unavailable. ①Realistic live-action drama→seedance-2.5 (strongest instruction following / face detail · pricing baseline 720p = 1×), or hailuo-3 when budget-sensitive (about 1/3 cost, 720p ≈0.33× · strong fidelity editing · can output 2K · but about 6 minutes per shot); ★After choosing, pass video_engine explicitly in create_drama / update_project_settings (the one the menu lists as available for this subject class)—if omitted, the platform only applies a style-based fallback stamp that is not guaranteed to be an engine the menu marks available; ② stylized/animation/3D cartoon drama·empty shots·product shots→wan3.0 (about 40% cost, 720p ≈0.4×ond·max 30 seconds·min 2-second billing·each shot ~2 minutes), use wan3.0-prime for rush delivery (720p ≈0.6×·~1 minute); ★Always quote prices as relative multiples (seedance-2.5 720p = 1×); call quote_* before giving the customer absolute credits; ③★Never choose wan3.0/prime for realistic live-action drama—WAN output-side real-human face review consistently rejects at 720p+ and retries cannot fix; ④★★Use wan3.0/prime cautiously for narrative dramas (dialogue, coherent story, stable shot rhythm): WAN will **self-cut hard camera changes inside a single storyboard shot** (test: 11/12 shots had intra-shot jump cuts, vs seedance-2.5 only 1/6 and hailuo-3 0/5), final cut feels like “the image jumps around within one shot and cuts too fast”; this is weak vendor instruction following and cannot be stopped by prompt constraints (our negative constraints are already included and tested ineffective), fix afterward only by regenerating with another engine. WAN suits inherently short-fast stylized/empty/product shots; for stable single-shot narrative choose seedance-2.5 or hailuo-3. After generation, use scan_intra_shot_cuts to inspect; ④b★★Use hailuo-3 cautiously for dialogue-heavy drama (different from the previous “intra-shot self-cut”; this is about **whether all dialogue is spoken**): native-audio engine stops reading when the shot ends and may ad-lib; tests show “dialogue not fully spoken” rate hailuo-3 **50%** (26 shots, all generated after 8-30 native-audio fixes, so engine-intrinsic), seedance-2.5 **23%** (294 shots); wan3.0 has **insufficient sample, not tested** on this dimension (26 samples all before same fix, only 2 shots after fix)—do not conclude WAN is bad from this. When customer says “line not finished”, first run scan_dialogue_coverage and categorize; do not default to lengthening shots (even with sufficient shot length, 32% still missed full lines). ⑤★Shot duration control (all engines, especially visible on WAN): keep each shot 3~5 seconds. Longer shots give the model more room to improvise—test: one 16-second shot (neighboring shots 3~5 seconds) changed scenes 4 times inside the shot, the character disappeared for 4 seconds and then grew back from the edge; customer sees “a person appeared out of nowhere”. For long performance, split into multiple short shots and connect with frame chaining; do not write single shots over 15 seconds. 【Resolution decision】Draft/iteration: WAN dramas 480p (≈0.2× cheapest), others 720p; final delivery: seedance dramas 720p (for HD delivery choose 1080p, about 2.5× 720p), hailuo-3 dramas 1080p (=2K·≈0.53×ond), WAN dramas 1080p (≈0.8×ond); hailuo-3 has no independent 480p tier (selecting it bills as 768P); set video_engine/video_resolution in create_drama/update_project_settings, ★both must be decided before video generation—switching does not back-propagate to generated shots, and mixing within one drama causes style/identity drift. ★Slow image generation ≠ failure: each image takes tens of seconds to minutes; a full episode may take over ten minutes. Poll get_storyboards frame_status—pending=still generating (wait patiently; do not call generate_frames repeatedly and waste credits), ready=done, failed=real failure. ★To change a specific shot image / make a new character sheet take effect, use **single-shot regeneration generate_shot_frame** (platform automatically includes identity anchors, scene/prop references, style anchors for that shot, preserving whole-film consistency); generate_frames only batch-fills shots with **missing frames** and skips shots that already have first frames (normal, not “refusal”). ★After first frames, call free tail_frame_plan to see which shots need independent last frames, then batch-fill with frame_type=last_frame. After changing a character sheet (set_character_portrait), response stale_frames are shots polluted by the old image and requiring per-shot regeneration. ★Never use external tools to make first/last frames and upload_shot_frame to “change the image”—external images lack identity/style anchors, so characters/clothing/style will drift; that is the real root of waste. upload_shot_frame is only for customer-owned real footage/assets. ③【Optional enhancements·AI proactively tells customer·quote confirmation required】Art bible generation / visual lock extraction / scene groups / lip sync / poster / sound effects / music / subtitle translation—these improve consistency/quality and are mostly paid. ★AI should proactively tell the customer these are available and quote them (whether to run depends on execution mode: professional mode / unconfirmed plan / customer-controlled current stage → tell customer and proceed only after agreement; do not decide for them; managed current stage → do not ask, follow get_production_plan autopilot.default_decisions, platform records in get_autopilot_log); neither silently skip nor charge without permission. ★Two lock disciplines: ①**Aspect ratio** is set in create_drama, locked at drama level, used by all later images/videos/final cuts, **do not change midstream** (generated content would have inconsistent aspect ratios and drift); default 9:16 if unset. ②**5-7 seconds per storyboard shot is a normal AI-video-optimized duration**, do not mistakenly re-split because “shots seem long”—generate_storyboards **replaces all storyboards in the episode**, wasting generated images; backend blocks if storyboards already exist and requires confirm_replace. ★Rewrite fidelity (default auto intelligent routing): when the set_script original **is already script-shaped** (scene headers/dialogue-line structure), rewrite_script automatically runs two-pass fidelity—customer dialogue is machine-gate locked line by line (dropping one line triggers internal rejection and redo), AI never adds plot; dramaturgical gaps (hooks/emotional anchors) are not auto-filled but listed in get_script dramaturgy_suggestions (whether to adopt depends on execution mode: professional mode / unconfirmed plan / customer-controlled current stage → tell customer and proceed only after agreement; do not decide for them; managed current stage → do not ask, follow get_production_plan autopilot.default_decisions, platform records in get_autopilot_log). If original is novel/outline, it auto-runs creative rewriting (AI builds hooks/emotional beats). Both customer types get the right path; no manual switch needed. To override defaults, use update_project_settings rewrite_pipeline (auto/two_pass/single_forced) and fidelity_enforce (1=hard fidelity gate). Handling “AI changed my script too much”: ①confirm full original is in set_script; ②set rewrite_pipeline to two_pass and rerun rewrite_script; ③after customer confirms character appearance, use update_character profile_locked=1 to lock profiles and prevent later extraction from overwriting appearance and changing the character sheet face. ★If customer wants to rewrite the script on **another AI platform** (common: third-party model judges our rewrite “changed too much”, customer wants control over change degree): first call get_script_format_spec to get the platform-accepted format contract (markdown template + external_prompt directly forwardable to the external model + blank skeleton), send external_prompt+template+customer original to that platform; after receiving the organized draft, **first call check_script_format** for self-check (free·rules only·no model). After errors clear, two exits: 【A】adopt_external_script directly commits it as shootable draft (our AI not involved·instant·free, provided the external draft contains production-layer annotations); 【B】set_script back into the original slot + rewrite_script through two-pass fidelity (choose this when the external draft only handles story layer; platform adds annotations; customer-written annotations are stripped and rewritten on this path). ★Do not put externally organized drafts into edit_rewritten_script (400 if no rewrite has run), and do not skip check_script_format before ingesting—noncompliant scripts are still gate-blocked and waste a run. ★★If the customer provides an **already finished storyboard table** (per-shot seconds/shot size/camera movement), neither path above applies—use import_storyboard_table directly to create storyboards, skipping rewrite and shot breakdown. The rewrite path will strip seconds/shot size/camera movement/STYLE/text cards as non-story content (production test: 8 shots 36 seconds → 20 shots 109 seconds). ★Both import channels are deterministic—errors are imported as-is, so **get the contract first, self-check, then import**: storyboard table path uses get_storyboard_table_spec → check_storyboard_table → import_storyboard_table; if customer tools/tables export structured data, or external AI can produce JSON directly, use get_bulk_import_spec → check_bulk_import → bulk_import_storyboards (storyboards only; characters/scenes/props are extracted from script by extract_assets, import binds existing items by name—extract first, then import). Both imports default with auto_complete (background AI fills professional fields + image/video prompts, text step postpaid; inform customer before calling): if receipt started=true, poll get_autofill_status until done before review_storyboards—autofill changes shots, so a token reviewed earlier invalidates. Use get_pipeline_status for progress (returns project-type-specific steps). ★★【Opening plan·first thing after creating drama·free】First ask basic video parameters (project type/aspect ratio/episode count × minutes per episode/genre: realistic_human·stylized·product/native audio or dubbing), then call get_production_menu to fetch the **currently available** three-tier packages (effect description + real-time estimate including text steps + recommended budget + excluded items) and present them to customer—do not recommend models from memory; some models may be temporarily unavailable for some genres, and the menu is already filtered. Then ask customer to choose execution mode (pro control every step / auto one-click final cut / custom select managed stages), budget budget_points, and automatic overrun cap (0/10/20/30/50%): **default recommendation** budget=selected tier recommended_budget (non-text upper bound ×1.2 plus text estimate), overrun=menu recommended_overrun_pct (30%)—QC regenerations are not in the upper bound and are covered by overrun; recommendation is only recommendation, final numbers are customer-decided; if customer changes them, follow customer. Clearly summarize and only after explicit customer agreement call confirm_production_plan(customer_confirmed:true)—never confirm on behalf of customer. For dramas with confirmed plans: before paid dispatch, platform rechecks model availability and quote upper bound ≤ budget×(1+overrun%); if blocked (402 BUDGET_WOULD_EXCEED / 409 MODEL_UNAVAILABLE), stop and ask customer, do not switch models or adjust budget yourself. confirm returns 403 PRODUCTION_PLAN_NOT_OPEN = drama not open (grayscale); follow original step-by-step confirmation flow.",
   "rewrite_script": "AI rewrite: convert the source script into a shootable script (read content → write script_content). Automatically selects the rewrite agent by project type. ★Fidelity auto-routing: if the source is already in script form, automatically uses two-pass fidelity (dialogue locked line by line by machine, AI does not add plot; dramaturgical gaps go into dramaturgy_suggestions; whether to adopt follows execution mode: pro mode / unconfirmed plan / customer-controlled step → explain to customer and do only with customer approval, do not decide for them; autopilot step → do not ask customer, follow get_production_plan autopilot.default_decisions, platform records in get_autopilot_log); if the source is a novel/outline, uses creative rewrite. (Ads use ad rewrite; MV is blocked from standard rewrite.) Backend async (minutes), text step is token postpaid, no arrears, no quote needed. After completion use get_script to review, edit_rewritten_script to revise. ★Typical time 2~4 minutes (production observed ≈169 seconds). **No result within 60 seconds is normal, not failure**—use get_run_status to check whether it is still running; do not rush to resubmit. ★★**This tool is \"redo from the entire source\", not \"make another revision\"**: rerunning when a shootable script already exists overwrites the current script and all prior fixes, and the new version **does not guarantee preserving parts already fixed in the old version** (production test across three versions: long narration split in the previous version was merged back in the next; correct period costume in the previous version drifted in the next). overwrites_existing_script=true in the response means exactly this. Therefore **after the first successful rewrite, all later changes must use edit_rewritten_script for targeted edits**—free, seconds-level, only touches the specified scenes, everything else remains byte-identical, deterministic with no lottery; rerun this tool only when a \"completely different version\" is required. If rerun by mistake, use get_script(include_previous=1) to retrieve the previous version. ★★【Execution-mode master rules · read before starting】For dramas with a confirmed opening plan, first get_production_plan and read autopilot: pro mode (pro, or autopilot.enabled=false, unconfirmed plan) → every later \"explain to customer and do only with customer approval\" is literal; auto / custom **autopilot steps** → do not ask customer: advance in order per get_pipeline_status next_action, self-confirm quotes within the hard budget cap, after each layer still run review_* + agent QC, and follow autopilot.next_step returned by review/QC (whitelisted error with auto_acknowledge:true / which self-fix round / pause to ask customer); for choices follow autopilot.default_decisions; autopilot.never_auto_actions(mode=replace, asset deletion, overwrite customer-uploaded images, allow_era_ref_conflict, voice cloning, delivery acceptance) always require customer approval in every mode. ★For the same shot in autopilot steps, generate_shot_frame regeneration max 3 rounds and regenerate_shot_video / edit_video_shot max 3 times; at the limit platform returns 409 AUTOPILOT_SHOT_REGEN_LIMIT (no charge)—do not bypass with another tool; stop and ask customer: if customer approves more regenerations, quote normally and generate with customer_approved_more_regens:true (grants another limit); if customer accepts current state, continue, and include acknowledge_review:true on the next paid call to record confirmation. 402 BUDGET_WOULD_EXCEED / 409 MODEL_UNAVAILABLE / 409 AUTOPILOT_SHOT_REGEN_LIMIT / 400 AUTOPILOT_MUST_ASK with must_ask_customer=true / nonempty pending_questions → pause, summarize get_autopilot_log pending_questions **once** and ask customer; customer-controlled steps follow pro mode. After final cut, deliver to customer using get_autopilot_log report. ★Three execution tiers (do not mix the three when asking customer): ①【Basic project settings · free · mandatory foundation · set when creating drama, do not create an empty shell】project_type/setting_brief (worldview · ERA LOCK)/ethnicity/aspect ratio resolution, plus consistency anchors cinematography_prompt (cinematography DNA) · art_bible · visual_lock— all free, the foundation driving full-pipeline consistency; if not set, all later generation drifts and rework costs again. Set directly with create_drama/update_project_settings. ★visual_lock/art_bible should contain only image-level/world-level locks (shot language · environment · art direction · forbidden elements), **never pin costume/hairstyle/appearance details for specific characters**—the single source of truth for character appearance is the character profiles output by extract_assets (change via update_character); writing both inevitably conflicts, character sheet vs profile and turnaround vs visual lock, consistency gates reject by character sheet → turnarounds/shot frames get **structural consecutive rejection**, no number of rerolls can pass, pure wasted money. ★★【Era contract · free · must set before image generation for non-contemporary or surreal subjects】The worldview in setting_brief is **free text**: it only provides background and cannot constrain images; what can truly override visual lock is the **structured era contract**: use set_era_contract to set this episode tier (modern/republican/historical/fantasy/surreal), get_era_contract to read current value. **Unset means empty**—the platform can only stack prompt text to fight the model; modern objects entering ancient images and scene images drawn as another era are mostly caused by this being empty. ★Xianxia/fantasy/fairyland **must use fantasy, not historical**: historical requires researched realism and will judge glowing aura, floating terrain, nonhuman forms as \"era-inconsistent\", pulling images toward realistic ancient style. For an exception in one scene (e.g. a modern memory in a fantasy world), use update_scene era_contract override; scene-level overrides episode-level. ★★【Per-step review protocol · all free · main line preventing bad films, not optional】After each step output, review first, tell customer the conclusion verbatim, then proceed. **Five hard gates (otherwise 400 rejected; ④⑤ and agent QC below)**: ①After rewritten script → review_script (before extract_assets / generate_storyboards); ②After storyboards → review_storyboards (before generate_frames); ③After shot images → review_frames (before generate_videos). Each review returns review_token; pass it to downstream paid tools. Explain findings to customer item by item (code=issue type · shots=hit shot numbers · action=which tool to fix with); after fixing per action, **review again** before proceeding. If content changed after review → token auto-invalidates; one re-review is enough (free). error blocks by default; only if customer is explicitly informed and insists may you pass acknowledge_review:true (acknowledge_review only means the customer personally agreed; any execution mode requires explicit customer approval, autopilot included). In autopilot steps only whitelisted heuristic errors may carry auto_acknowledge:true (see 【Execution-mode master rules】). **Soft guidance (non-blocking but strongly recommended, also free)**: before images/videos run run_precheck (catches shots vendors will certainly reject, avoiding wasted credits)—★**to scan the whole drama, run run_drama_precheck first** (drama-level summary · free · read-only): get issue counts and attention per episode in one call (which episodes to fix first), prioritize by it, then run run_precheck on those episodes for itemized details; do not blind-scan episode by episode. Note its not_covered—drama-level skips the only lint that needs images, so \"0 issues for whole drama\" ≠ \"everything checked\". ★After findings, do not blindly edit yourself: plan_precheck_fix lets platform compute proposals → apply_precheck_fix persists them (which to accept; autopilot=accept all per execution mode: pro mode / unconfirmed plan / customer-controlled step → explain to customer and do only with customer approval, do not decide for them; autopilot step → do not ask customer, follow get_production_plan autopilot.default_decisions, platform records in get_autopilot_log); after storyboards run get_health_report; after character sheets are done, use get_characters to verify every appearing character has image/sheet; after frames, use get_storyboards to inspect frame_status and fail_reason/fail_hint (fix failed shots before proceeding; do not generate videos from bad frames); after videos likewise inspect video_status; before final cut use get_pipeline_status to confirm no missing shots. ★**Never just generate all the way through**: pushing without reviews amplifies issues at every layer and finally forces redoing the whole episode—every image/video retry is charged. Reviews are all free; catching early costs nothing. ★Changing costume is a structured binding edit: update_shot active_wardrobe_id (whole shot) / appearance_wardrobes (per-character in multi-character shots), can override or clear—editing text description does not change clothes, and customers need not change it on the web. ②【Production trunk · ordered, no skipping · ★storyboard before asset creation】set_script→rewrite_script→★review_script→extract_assets→storyboards (storyboard first · pure text shot breakdown)→★review_storyboards→★Script discipline (endpoint-enforced, cannot bypass): all raw material (synopsis/outline/finished script all count) goes into set_script and **must pass rewrite_script to produce an AI rewritten script**—pasting your own script directly into edit_rewritten_script to bypass rewrite will be 400 rejected (no rewritten script means no editable object); extract_assets likewise requires the rewritten script. All post-rewrite edits use the structured AI-output format: edit_rewritten_script (polish/correct), update_character, update_shot/replace_shot_dialogue—do not go back and replace the whole script or write another truth source in settings; dual sources of truth are the top cause of consistency accidents. ★★**After one successful rewrite, do not rerun rewrite_script**: it redoes the whole source, losing all current fixes, and the new version does not guarantee preserving old fixed parts (three-version tests drift back and forth). To fix, use edit_rewritten_script targeted edit (get_script full text → change only those scenes, copy the rest byte-identically → submit full script), free and seconds-level, deterministic; if rerun by mistake, recover previous with get_script(include_previous=1). generate_portraits_and_sheets (character sheets + turnarounds · create after storyboards: first use delete_character to remove appearing characters that **do not appear in any episode of the whole drama and are not intended for later episodes** before image generation—characters are drama-level; once deleted, frame assembly for every episode will no longer include them; this cannot be judged from this episode's storyboards alone, keep if unsure (one character sheet costs far less than losing the identity anchor in a later episode); the character sheet step generates images for **all undeleted appearing characters**, regardless of storyboard bindings, and all kept characters are charged; voiceover characters (char_type=voiceover narrator/phone voice) are not imaged and have no storyboard binding, **do not delete**, audio still needs them)→★generate_color_script (color script · unified grading)→assign_voices (assign voice types; no suitable narrator/character-library voice → design_voice from description, then set_character_voice after sample approval)→★quote_scene_images+generate_scene_images (empty scene plates · required before frames)→frames (default first frames only)→★tail_frame_plan (free · which shots need independent tail frames)→frames(frame_type=last_frame)→★chain_frames (seams · first dry_run:true)→★review_frames→videos→generate_tts→compose; ★★【Do not skip seams · complete tail frames before review_frames】After first/tail frames are ready, call chain_frames(dry_run:true, free) to see the platform's seam plan and estimated_points (copy free, reframe costs one image per seam); explain to customer and, after confirmation, execute without dry_run. Already chained seams are excluded, repeat calls do not double charge. ★After execution, reframe is **async image generation**: use get_jobs to watch the planned shots' first_frame jobs, wait until all pending/processing are done (for failed, inspect error_msg; use chain_shot_from for a single seam), then review_frames—the old first frame still exists so get_storyboards frame_status remains ready and cannot show whether the new image is running or failed. After get_jobs clears, use get_storyboards to check seam_state: replacement images rejected on promotion do not remain in get_jobs; that seam remains unchained (review_frames will also report seam_unchained), reconnect per its action. If you review before landing, you review old first frames; the token expires when the new first frame lands. Episodes generated shot-by-shot/batch often have not been auto-chained (get_storyboards seam_state=unchained); skipping causes no error—the cost is visual mismatch between shots and jump cuts throughout the final cut. ★★【Do not skip tail frames · frames are two passes】generate_frames defaults to first frames only. About 30% of shots have **end state ≠ start state** (large camera moves/object release/state change) and need an independent tail frame; the criterion is platform-side and cannot be guessed from storyboard text. Therefore after first frames, you must call the free tail_frame_plan once for a per-shot list, then fill frame_type=last_frame (shots_needing_last_frame in generate_frames response is this count; if not 0, do not go directly to review_frames). Skipping causes no error and does not block you—the cost is those shots only have a first-frame anchor when generating video, so the model improvises the end state: actions miss, large camera moves end back at the starting composition. Production observed 30 of 32 episodes generated only first frames; 23 still generated videos all the way. ★★【When tail frame is blocked by TERMINAL_DESC_GATE: edit text, do not retry】For shots reporting \"this shot is marked as state-changing but nowhere describes what the end looks like\", use update_shot to write **what the image looks like at the end** into that shot's last_frame_prompt, then regenerate the tail frame. ★Better: **avoid hitting it**—before tail frames, call get_storyboards once; terminal_desc_missing=true lists all such shots in the episode (free). Fill their last_frame_prompt first, then generate, with zero rejections. You can also query per shot via get_shot_prompts same field, but do not do that for dozens of shots. Retrying without adding description is ineffective—the vendor prompt has no terminal-state segment, so it still draws the starting pose and will be rejected again by terminal review, while each try is still charged (production observed tail-frame success 9.4% without terminal description, 40.2% with it). Only for shots that truly should be \"almost unchanged\" use generate_shot_frame allow_missing_terminal to bypass. ★★【Do not skip empty scene plates · this step is often missed by third parties】Scene images are **background anchors**: every shot frame in the same scene anchors to them. Frames can still be generated without plates, with no error and no blocking—the cost is **the first shot of each scene has no background anchor at all** (platform fallback image generation is \"when missing image detected, generate one in background\"; later shots in the same scene use it, but the triggering shot itself cannot wait for it), and the first shot is often the tone-setting shot; backgrounds also drift across later shots. It pairs with character sheets: character sheets anchor people, scene images anchor setting; whichever is missing drifts. Progress self-check: `get_pipeline_status` generate_scene_images step (completed/total); `review_storyboards` also reports scene_plate_missing before frames. ★★【Do not skip turnarounds · character sheet ≠ turnaround】A character sheet is a single-person single-image identity anchor; a turnaround is a multi-view turnaround generated by the platform from the character sheet, the root consistency anchor for shot frames/videos (angle changes · lighting changes · costumes mostly rely on it). Frames can still be generated with only character sheets and no error—the cost is character drift when angle changes and costumes differ every shot. Use generate_portraits_and_sheets for both steps (each call advances one step; after character sheets are complete, call again to generate turnarounds), or call generate_character_sheets after character sheets. Progress self-check: get_pipeline_status generate_character_sheets step (completed/total, portrait_only=characters with only character sheets). ★Customer-provided images: character sheet must be single person, single image, single angle, no text; scene image must be empty environment, no people, no overlaid text—set_character_portrait/upload_scene_image auto-check and reject noncompliance with 422. ★Do not create character images/prop sheets/motion templates before storyboards—storyboard is pure text and depends on no images; only after storyboards is the cast fixed, so delete non-appearing characters before images to save (motion templates must be after storyboards anyway). Paid steps follow the existing quote confirmation flow. Ads additionally need add_product+generate_product_sheet; MV flow is set_mv_lyrics→generate_mv_story→generate_mv_script (if no existing song: after set_mv_lyrics run suggest_mv_song_styles→quote_mv_song→generate_mv_song→get_mv_song→select_mv_song). ★★【④⑤ two new hard gates + agent hands-on QC】④Asset layer: after character sheets/turnarounds/scene images/prop images → review_assets (before generate_frames / generate_shot_frame; its token is asset_review_token and is passed together with the storyboard-layer review_token); ⑤Video and audio layer: after videos/voiceover/music → review_videos (before compose_episode); after final cut, run review_final_cut. ★After every review layer you must also **personally QC**: follow returned agent_qc, inspect each asset yourself (download images, sample video frames, read text), answer checklist items, submit via submit_qc_report; for gray-release dramas, a review_token without the report cannot enter the next step; report problems block by default just like error. Platform judges whether it exists; you judge whether it looks right and is correct. ★★【Single-shot path is also review-gated】: generate_shot_frame also requires storyboard-layer review_token; regenerate_shot_video also requires shot-image-layer review_token—do not expect single-shot tools to bypass reviews (production observed a workflow generating all 25 shots via single-shot frames without hitting any gate, and all final-cut rework was truly charged). Generating frames **does not** invalidate the storyboard-layer token (fingerprint only checks storyboard content); only changing storyboard content—update_shot / import / add-delete shots / change character bindings—requires one re-review (free, seconds). Generating one shot's frame invalidates the **shot-image-layer** token; before regenerate_shot_video for the next shot, just run review_frames once. ★★【For native-audio dramas, lock voices before batch video】When use_clip_audio=true (default), each shot's voice is sampled by that video vendor, and will drift if not locked; unifying later requires regenerating shot by shot. With customer-authorized source audio → clone_voice+set_character_voice before generate_videos; without it → for each speaking character, first use single-shot quote_regenerate_shot_video→regenerate_shot_video on a shot with relatively long dialogue (generate_videos has no per-shot parameters and only batch-fills missing videos; single-shot regeneration also works on shots with no video yet), use set_voice_anchor_from_shot to select the voice from that shot, then generate remaining shots. get_pipeline_status native_voice_anchor lists unanchored_speakers and stale_shots generated before locking that need regeneration. ★World concept image = required by default (improves whole-drama consistency; many third-party platforms skip it): after storyboards, call generate_world_concept by default; still follows quote confirmation (tell customer estimated credits and confirm before charging)—do not silently charge, and do not skip. ★★【Color script】generate_color_script unifies color grading for the whole film; do after storyboards and before frames. Text step has no quote_* and is usage-postpaid. Progress self-check: get_pipeline_status generate_color_script; review_storyboards reports color-script gaps. ★Motion templates are optional experimental: call generate_motion_templates (motion template extraction) only when customer explicitly requests, after storyboards; text step usage-postpaid. First/tail frames do not inject motion templates by default; missing templates need not be created and do not block images, videos, or final cut. Video templates may be cropped; delivery or benefit is not guaranteed. ★Scene Bible (detailed per-scene settings) order is **after scene images are generated**—refine based on generated scene images (no MCP tool yet; do on official site); do not do Scene Bible before scene images. ★Audio defaults to native video audio (use_clip_audio default on; skip TTS and use AI video's built-in audio): when creating drama/changing settings, AI should proactively tell customer \"default uses native video audio; set use_clip_audio false if TTS dubbing is needed\" and let customer choose. ★Default image model is ChatGPT Image 2.5 Flare (gpt-image-2.5-flare · unified style across drama): set image_model in create_drama/update_project_settings; default if omitted. Options: gpt-image-2.5-sunburst (same price · better Chinese glyphs and details)/gemini-3.1-flash-image (Banana 2 · 71 credits)/gemini-3-pro-image (Banana Pro · more detailed · 175 credits)/gemini-3.1-flash-lite-image (Banana 2 Lite · cheaper · 31 credits)/doubao-seedream-5-0-260128 (Seedream5.0); generate_frames can temporarily override for one run. ★2.5 charges by input volume (base 11 credits + 18 credits per reference image); Banana/Seedream are fixed-price—budget must account for many-reference shots. ★Four video engine options (drama-level · when AI creates drama, must proactively guide selection by drama and show price differences for customer decision): 【Selection tree】★Call get_production_menu first: whether each engine is currently available for realistic live-action / anime and other subject classes is decided by the availability it returns (unavailable entries carry customer_note and expected_until—relay them to the customer verbatim); do not assume from this description that any model is unavailable, and do not recommend models the menu marks unavailable. ①Realistic live-action drama→seedance-2.5 (strongest instruction following / face detail · pricing baseline 720p = 1×), or hailuo-3 when budget-sensitive (about 1/3 cost, 720p ≈0.33× · strong fidelity editing · can output 2K · but about 6 minutes per shot); ★After choosing, pass video_engine explicitly in create_drama / update_project_settings (the one the menu lists as available for this subject class)—if omitted, the platform only applies a style-based fallback stamp that is not guaranteed to be an engine the menu marks available; ②Stylized/animation/3D cartoon dramas · empty shots · product shots→wan3.0 (about 40% price, 720p ≈0.4× · max 30 sec · min 2 sec billing · about 2 minutes per shot), for urgent delivery use wan3.0-prime (720p ≈0.6× · about 1 minute); ★Always quote prices as relative multiples (seedance-2.5 720p = 1×); call quote_* before giving the customer absolute credits; ③★Never choose wan3.0/prime for realistic live-action dramas—WAN output-side human-face review rejects consistently at 720p+, retries cannot fix; ④★★Use caution with wan3.0/prime for narrative dramas (dialogue, coherent story, stable shot rhythm needed): WAN will **hard-cut to new camera angles inside a single storyboard shot** (observed 11/12 shots with intra-shot cuts, vs seedance-2.5 only 1/6, hailuo-3 0/5); final-cut feel is \"image jumps around within one shot, cuts too fast\". This is weak vendor instruction following; prompt-level blocking cannot solve it (our negative constraints already included and tested ineffective). Only remedy after generation is regenerate with another engine. WAN suits fast short stylized/empty/product shots; for stable single-shot narrative choose seedance-2.5 or hailuo-3. After generation use scan_intra_shot_cuts to check; ④b★★Use caution with hailuo-3 for dialogue-heavy dramas (different from the previous \"intra-shot self-editing\"; this is about **whether all dialogue is spoken**): native-audio engine stops when the shot ends and may ad-lib; observed \"dialogue not fully spoken\" rate hailuo-3 **50%** (26 shots, all generated after 8-30 native-audio fix, so engine-inherent), seedance-2.5 **23%** (294 shots); wan3.0 has **insufficient sample size, untested** on this dimension (26 samples all before the same fix; only 2 after fix)—do not infer WAN is bad from this. When customer reports \"line was not finished\", first run scan_dialogue_coverage to segment causes; do not default to lengthening shots (observed that among shots with enough duration, 32% still did not speak all lines); ⑤★Shot duration control (all engines, especially obvious on WAN): keep each shot 3~5 sec. The longer the shot, the more freedom the model has—observed one 16-sec single shot (neighbors were 3~5 sec) changed scene 4 times inside the shot, a character disappeared for 4 sec then grew back from frame edge; customer perceives \"someone appeared out of nowhere\". For long performances, split into multiple short shots and connect with frame chaining; do not write single shots longer than 15 sec. 【Resolution decisions】Draft/iteration: WAN dramas 480p (≈0.2× cheapest), others 720p; final delivery: seedance dramas 720p (for HD delivery choose 1080p, about 2.5× 720p), hailuo-3 dramas 1080p (=2K · ≈0.53×), WAN dramas 1080p (≈0.8×); hailuo-3 has no separate 480p tier (choosing it still bills as 768P). Set video_engine/video_resolution in create_drama/update_project_settings; ★both must be decided before video generation—switching does not retroactively change generated shots; mixing in one drama causes style/identity drift. ★Slow image generation ≠ failure: each image takes tens of seconds to minutes, a whole episode may take over ten minutes; poll get_storyboards for frame_status—pending=still generating (wait patiently, do not repeat generate_frames and waste credits), ready=done, failed=real failure. ★To change one shot's image / make a new character sheet take effect, use **single-shot regeneration generate_shot_frame** (platform automatically includes that shot's identity anchors · scene/prop references · style anchor, preserving whole-film consistency); generate_frames only batch-fills shots with **missing frames** and skips existing first frames (normal, not \"rejection\"). ★After first frames, call free tail_frame_plan to see which shots need independent tail frames, then batch-fill with frame_type=last_frame. After set_character_portrait, stale_frames in the response are shots polluted by the old image and must be regenerated shot by shot. ★Never use external tools to make first/tail frames and upload_shot_frame to \"change image\"—external images lack identity/style anchors, so characters/costumes/style will drift, which is the real source of bad films; upload_shot_frame is only for customer-owned real footage. ③【Optional enhancements · AI proactively informs customer · quote confirmation required】Art Bible generation / visual lock extraction / scene groups / lip sync / posters / sound effects / music / subtitle translation—these improve consistency/quality and are mostly charged. ★AI should proactively tell customer these are available and provide quotes (whether to run follows execution mode: pro mode / unconfirmed plan / customer-controlled step → explain to customer and do only with customer approval, do not decide for them; autopilot step → do not ask customer, follow get_production_plan autopilot.default_decisions, platform records in get_autopilot_log); neither silently skip nor charge without permission. ★Two locking rules: ①**Aspect ratio** is set at create_drama, locked at drama level; all later images/videos/final cut use it, **do not change midstream** (changing makes generated content aspect-inconsistent and drift); default 9:16 if unset. ②**5-7 sec per shot in shot breakdown is normal duration optimized for AI video generation**; do not misjudge as \"shots too long\" and rebreak—generate_storyboards **replaces all storyboards in the episode** and wastes generated images; backend blocks if storyboards already exist and requires confirm_replace. ★Rewrite fidelity (default auto smart routing): when set_script source is **already in script form** (scene headings/dialogue-line structure), rewrite_script automatically uses two-pass fidelity—customer dialogue is locked line by line by a machine gate (missing any line triggers internal rejection and redo), AI never adds plot; dramaturgical gaps (hooks/emotional anchors) are not auto-filled, but written into dramaturgy_suggestions returned by get_script (whether to adopt follows execution mode: pro mode / unconfirmed plan / customer-controlled step → explain to customer and do only with customer approval, do not decide for them; autopilot step → do not ask customer, follow get_production_plan autopilot.default_decisions, platform records in get_autopilot_log). If source is novel/outline, automatically uses creative rewrite (AI lays hooks and emotional points). Both customer types get appropriate handling with no manual switch. To override default, use update_project_settings rewrite_pipeline(auto/two_pass/single_forced) and fidelity_enforce(1=fidelity hard gate). If customer says \"AI changed my script off-track\": ①confirm full source was put into set_script; ②set rewrite_pipeline to two_pass to force fidelity, then rerun rewrite_script; ③after customer confirms character appearance, use update_character profile_locked=1 to lock profile and prevent later extraction from overwriting appearance and changing the face in character sheets. ★If customer wants to rewrite on **another AI platform** (common: third-party model judges our rewrite \"changed too much\", customer wants to control change degree): first call get_script_format_spec to get the platform-accepted format contract (markdown template + external_prompt directly forwardable to external model + blank skeleton), send external_prompt+template+customer source to that platform; after receiving organized script, **first call check_script_format to self-check** (free · rule-only · no model). Once errors are zero, two exits: 【A】adopt_external_script to directly adopt as shootable script (our AI not involved · seconds-level · no charge, requires external script includes production-layer annotations); 【B】set_script back into source slot + rewrite_script with two-pass fidelity (choose this when external only handles plot layer; platform fills annotations; customer-written annotations on this path are stripped and rewritten). ★Do not put external organized script into edit_rewritten_script (400 rejected if rewrite has never run), and do not skip check_script_format and ingest directly—noncompliant scripts are still blocked by gates and waste a run. ★★If the customer provides a **finished storyboard table** (per-shot duration/shot size/camera movement), neither path above applies—use import_storyboard_table directly to create storyboards, skipping rewrite and shot breakdown. The rewrite path strips duration/shot size/camera movement/STYLE/text cards as non-plot content (production observed 8 shots 36 sec → 20 shots 109 sec). ★Both import channels are deterministic—even wrong content is created as-is, so **get contract first, then self-check, then import**: storyboard table path is get_storyboard_table_spec → check_storyboard_table → import_storyboard_table; if customer's own tools/spreadsheets can export structured data, or external AI can directly produce JSON, use get_bulk_import_spec → check_bulk_import → bulk_import_storyboards (creates storyboards only; characters/scenes/props are extracted by extract_assets from the script; import binds existing ones by name—extract first, then import). Both imports default with auto_complete (backend AI fills professional fields + image/video prompts, text step postpaid; inform customer before call): if receipt started=true, poll get_autofill_status until done, then review_storyboards—autofill changes shots, so any earlier review token expires. Use get_pipeline_status for progress (returns project-type-specific steps). ★★【Opening plan · first thing after creating drama · free】First ask basic video parameters (project type/aspect ratio/episode count × minutes per episode/subject: realistic_human · stylized anime · product empty-shot/native audio or dubbing), then call get_production_menu to get the **currently available** three package tiers (effect notes + real-time estimate including text steps + recommended budget + exclusions) and explain to customer—do not recommend models from memory; some models may be temporarily unavailable for certain subjects, menu is already filtered. Then let customer choose execution mode (pro controls every step / auto one-click final cut / custom choose autopilot steps), budget budget_points, and automatic overrun cap (0/10/20/30/50%): **default recommendation** budget=selected tier's recommended_budget (upper bound excluding text ×1.2 plus text estimate), overrun=menu recommended_overrun_pct (30%)—QC regenerations are not in the upper bound and are covered by overrun. Recommendations are only recommendations; final numbers are set by customer, and if customer changes them, use customer's values. Explain the summary clearly; only after explicit customer agreement call confirm_production_plan(customer_confirmed:true)—never confirm for the customer. For dramas with confirmed plans: before paid dispatch, platform rechecks model availability and that quote upper bound ≤ budget×(1+overrun%); if blocked (402 BUDGET_WOULD_EXCEED / 409 MODEL_UNAVAILABLE), stop and ask customer; do not change model or budget yourself. confirm returning 403 PRODUCTION_PLAN_NOT_OPEN = this drama is not enabled (gray release); follow the original step-by-step confirmation flow.",
   "get_script": "Read the raw episode content + AI-rewritten shootable script + rewrite status + dramaturgy_suggestions (dramatic gaps AI identified but did not auto-fill in two-step fidelity mode—hooks/emotional anchors; whether to adopt them depends on execution mode: professional mode / unconfirmed plan / client-controlled step → explain to client and do only after client agrees; do not decide for client; hosted step → do not ask client, follow get_production_plan autopilot.default_decisions, platform records it in get_autopilot_log; ignoring them does not affect the production pipeline). Free. ★Revision workflow: first use this tool to retrieve the full rewritten_script → edit only the scenes the client wants changed → submit with edit_rewritten_script (do not rerun rewrite). previous_script_available=true means a previous-version snapshot exists; pass include_previous=1 to retrieve the full previous version (recovery path for accidental rerun/bad edits; omitted by default to avoid doubling the response).",
@@ -88,7 +88,7 @@
   "apply_extend_final": "Set an extension output as this episode's **final cut** (free, pure pointer switch).\n★This step **overwrites** the episode's current final cut link: the previous final cut is no longer the public version. First use get_extend_final to inspect final_url and confirm the customer is satisfied before calling.\n★If compose_episode (final assembly) is run again later, the final cut will be overwritten by the final assembly result, and applied automatically becomes false.",
   "export_sheet_compare": "Export **character sheet comparison version** (side-by-side composite of character sheets and final cut frames, for marketing/delivery). Triggers backend compositing; poll with get_sheet_compare.\n★This capability is **off by default**: it is a drama-level switch (not every title is allowed to export this externally). When off it returns **403**. If you see 403, do not retry and do not treat it as failure—tell the customer to enable it in **Drama Settings** on the official site.\nIf character_id is omitted, export the whole episode; if provided, export only that character.",
   "get_sheet_compare": "Poll export status for the character sheet comparison version. Free. Returns enabled (whether the drama switch is on)/processing/result/error.\n★enabled=false means the drama switch is not enabled—not an error. Enable it in Drama Settings on the official site, then export again.",
-  "update_project_settings": "Modify project settings after creating the drama. Besides aspect ratio/resolution/worldview Brief/ethnicity/genre/director style, now also covers ★whole-drama visual consistency anchors (cinematography DNA cinematography_prompt/art bible art_bible/visual lock visual_lock/video style positive and negative prompts/visual motifs motifs), audio (bgm_source own vs native/bgm_volume_preset volume/use_clip_audio use original video audio), subtitles (show_subtitles/bilingual subtitle_secondary_lang/position/margins/animation), transitions—i.e. all common settings on the project settings page. Free. ⚠️ After changing worldview Brief/ethnicity/aspect ratio/consistency anchors, already generated content will not update automatically; regenerate the corresponding content. ★frame_chain_mode controls cross-shot frame chaining for the whole drama: off = none at all (the auto-chain after frames settle, chain_frames and bookends dispatch no images and change no frames, and quotes no longer include them); reframe = default; strict = adjacent seams only copy the previous shot's last frame, no regeneration (bookends already set still regenerate as reframes and are still quoted; use off for no images at all). To use chain_frames after turning it off, switch back to reframe/strict first; changing the mode does not regenerate existing frames.",
+  "update_project_settings": "Modify project settings after creating the drama. Besides aspect ratio/resolution/worldview Brief/ethnicity/genre/director style, now also covers ★whole-drama visual consistency anchors (cinematography DNA cinematography_prompt/art bible art_bible/visual lock visual_lock/video style positive and negative prompts/visual motifs motifs), audio (bgm_source own vs native/bgm_volume_preset volume/use_clip_audio use original video audio), subtitles (show_subtitles/bilingual subtitle_secondary_lang/position/margins/animation), transitions—i.e. all common settings on the project settings page. Free. ⚠️ After changing worldview Brief/ethnicity/aspect ratio/consistency anchors, already generated content will not update automatically; regenerate the corresponding content. ★frame_chain_mode controls cross-shot frame chaining for the whole drama: off = none at all (the auto-chain after frames settle, chain_frames and bookends dispatch no images and change no frames, and quotes no longer include them); reframe = default; strict = adjacent seams only copy the previous shot's last frame, no regeneration (bookends already set still regenerate as reframes and are still quoted; use off for no images at all). To use chain_frames after turning it off, switch back to reframe/strict first; changing the mode does not regenerate existing frames. ★Besides the fixed presets, aspect_ratio accepts a free aspect ratio (a number such as 2.35, or \"2.35:1\" / \"47:20\"; width÷height within 0.4–2.5). It only works with Seedance 2.5 + a Seedream image model + non-4k resolution; video follows the first-frame size, so scene groups, reference-to-video, keyframe groups and pure text-to-video are not available (the vendor only outputs 6 fixed ratios). Rolled out per drama: dramas not enabled get a 400 — relay it and use a fixed preset instead.",
   "generate_world_concept": "(★Default required·many third-party platforms miss this step·still uses quote confirmation) Generate worldview concept images (fixed 4 panels: panorama/era/main location/color) to improve whole-drama visual consistency. ★Call this by default after storyboard; do not skip. But still tell the customer the estimated credits (whether to run depends on execution mode: Professional mode / unconfirmed plan / this step is customer-controlled → explain to the customer and run only after customer approval; do not decide for them. This step in autopilot → do not ask the customer; follow get_production_plan autopilot.default_decisions, and the platform records it in get_autopilot_log). Before dispatch, the platform prechecks budget by missing slots × single-image upper bound; if it exceeds the hard cap, returns 402, with no charge. Requires setting_brief ≥30 characters. Image step, fixed-cost postpaid, no arrears.",
   "generate_art_bible": "Generate the art bible (palette/materials/atmosphere, reads characters + metadata). Text step, postpaid, no arrears.",
   "extract_visual_lock": "Extract \"visual lock\" rules from worldview Brief + characters (writes visual_lock, unifies image style/ethnicity). Text step, postpaid, no arrears.",
@@ -281,5 +281,7 @@
   "create_motion_reference": "Register a **motion / camera reference clip** in your own motion reference library (free), then attach it to a shot with attach_motion_reference — the AI video for that shot is regenerated following the clip's motion, camera move and blocking. ★**Greybox (3D previs) goes here**: set kind to greybox_coarse / greybox_fine and the platform tells the model to use the greybox only for camera movement, rhythm, shot size, motion paths and blocking — never its proxy shapes or untextured look. Greybox tips: coarse works best — build people/objects from simple primitives; model only the torso, or if you model limbs/wings animate them fully, otherwise limbs come out stiff; one clip ≤30 s (Seedance 2.5), 1–5 subjects work best. ⚠️ Not the same as upload_shot_footage: that one says \"this clip IS the finished shot\"; this one says \"regenerate the shot following this clip\".",
   "list_motion_references": "List the clips in your own motion reference library (greyboxes included), free. Returns id / name / kind / video_url; pass the id to attach_motion_reference.",
   "get_shot_motion_reference": "Show the motion reference / greybox attached to a shot and its proxy-to-character bindings (free). greybox_gray_on=false means greybox rendering is not enabled for this drama yet and a greybox is treated as a plain motion reference.",
-  "attach_motion_reference": "Attach a motion reference / greybox to a shot (free); asset_id=null detaches it (bindings are cleared too). Then quote_videos / generate_videos as usual: the shot switches to the reference-video path — motion, camera move, blocking and shot size follow the clip, first/last frames are not sent (the vendor treats the two as mutually exclusive), identity comes from the character reference images, and review_frames is still required before video. ★**When the greybox has several proxies, always pass greybox_bindings** saying which proxy is which character (e.g. [{proxy:\"red model\",character_id:12},{proxy:\"blue model\",character_id:15}]); the platform writes each character's reference image number into the prompt — without bindings, multi-character shots tend to swap identities. Write proxy exactly as the colour/number in the client's greybox; character_id must be a character of this drama (get_characters). Bound characters not on the shot's cast list get their reference images added automatically. Omitting greybox_bindings keeps the existing bindings for the same clip and clears them when the clip changes."
+  "attach_motion_reference": "Attach a motion reference / greybox to a shot (free); asset_id=null detaches it (bindings are cleared too). Then quote_videos / generate_videos as usual: the shot switches to the reference-video path — motion, camera move, blocking and shot size follow the clip, first/last frames are not sent (the vendor treats the two as mutually exclusive), identity comes from the character reference images, and review_frames is still required before video. ★**When the greybox has several proxies, always pass greybox_bindings** saying which proxy is which character (e.g. [{proxy:\"red model\",character_id:12},{proxy:\"blue model\",character_id:15}]); the platform writes each character's reference image number into the prompt — without bindings, multi-character shots tend to swap identities. Write proxy exactly as the colour/number in the client's greybox; character_id must be a character of this drama (get_characters). Bound characters not on the shot's cast list get their reference images added automatically. Omitting greybox_bindings keeps the existing bindings for the same clip and clears them when the clip changes.",
+  "generate_greybox_previs": "**Auto-generate a coarse greybox** for a shot from the fields the storyboard already has and attach it (free): shot size, camera height and side, camera move (push/pull/pan/tilt/track/crane/arc), blocking, facing, duration and action (approach, back away, turn, sit down…). The platform renders a primitive-geometry greybox clip (one colour per character, torso only), registers it as greybox_coarse and **fills greybox_bindings automatically** — the client does not have to build a greybox. The point is to turn shot size / camera move / blocking from text hints into pixel constraints when shots ignore the staging. ★Once attached the shot uses the reference-video path: **first/last frames are no longer sent** (identity comes from the character references) and **the video quote rises by roughly 20%** (reference video is billed per second) — tell the client both before generating. ★Run dry_run=true first to see which fields were used and what was assumed (assumptions = fallbacks for missing fields); fix fields with update_shot before generating. Shots it does not apply to come back with a reason: insert shots, no on-screen character, longer than 15 s, state-change shots (they rely on the end-frame state; pass include_state_change=true to force). A motion reference the client attached themselves is never overwritten (409) unless replace_existing=true. Pass episode_id without storyboard_id for a whole episode (≤40 shots per call; pick shots with storyboard_ids). Returns 409 while the drama is not enabled (gradual rollout). Afterwards review_frames → quote_videos → generate_videos as usual.",
+  "get_greybox_previs": "Inspect a shot's auto greybox (free): attached = whether the attached motion reference is a platform-generated greybox; stale=true means the shot fields changed since and the greybox is outdated — run generate_greybox_previs again; current is the plan and assumptions the current fields would produce; skip is the reason when the shot does not apply."
 }