Seedance Submitter

# Seedance Submitter

## Use When
- Preparing, validating, submitting, polling, or debugging Seedance 2.0 jobs
  routed through PostPlus Cloud.
- Inputs can be product images, storyboard images, UGC scripts, voiceover copy,
  or existing Seedance request JSON.

## Do Not Use When
- The task belongs to ideation, QA, or another released skill listed in the handoff section.
- Required inputs are missing and guessing would change the result.
- Task class, hook logic, storyboard, or reference policy is still unresolved.
  Use `video-generation` and `video-request-architect` first.

## Execution Boundary
- This runner validates, submits, and polls normalized Seedance requests. It must
  not make creative strategy, task-classification, or reference-policy decisions.
- Interpret `sd2` as Seedance 2.0 unless the user names another model.
- Released endpoint keys are `video-seedance-2-image`,
  `video-seedance-2-image-turbo`, `video-seedance-2-text`, and
  `video-seedance-2-text-turbo`.
- `duration` is the provider bucket and must be `5`, `10`, or `15`. For edit
  targets like `7.5s`, use the next viable bucket in `duration` and set
  `targetEditDurationSeconds`.
- When `targetEditDurationSeconds < duration`, include
  `timeline.activePerformanceEndSeconds` and `timeline.tailStrategy`.
- If the target script or beat plan exceeds 15 seconds, split into independent
  submit-ready segments. Do not submit one oversized request.

## Source And Request
- Lock product/storyboard/reference media, script, duration bucket, target edit
  duration, output root, source basis, and whether the user wants submit or JSON
  only.
- Put timecoded action and spoken lines together in `promptPlan.prompt_storyline`.
  Put voice style, BGM, SFX, subtitle, and watermark constraints in
  `promptPlan.audio`.
- Bind references explicitly: say what `[image 1]`, `[image 2]`, `[audio 1]`,
  or `[video 1]` controls. Do not rely on `same as previous`, `content above`,
  or unbound local handles in final requests.
- Upload local reference images with the hosted media-file upload flow before
  submission and pass uploaded URLs into the Seedance request.

## Review And Handoff
- Before submission, verify validation passed, every segment is self-contained,
  references are bound, required media exists, source basis is explicit, and the
  output path is durable.
- If a render is pending, return the segment id, manifest path,
  `pollRequestPath`/`pollCommand`, generation handle, and expected local
  `renders/` output path. Do not keep polling in the conversation.

## Stop Conditions
- Stop when required user intent, source evidence, or owned input artifacts are
  missing and guessing would change the result.
- If an owned CLI or script command fails, report the exact error and stop. Do
  not bypass the failure with metadata-only answers, readiness probing, local
  payload rewrites, fallback providers, or unpublished tools.

## Public Command Boundary

- Choose the smallest matching command or workflow from the user input and run
  it directly.
- Readiness diagnostics: `postplus doctor --skill seedance-submitter`.
- If an owned CLI or script command fails, report the exact error and stop. Do
  not bypass the failure with metadata-only answers, readiness probing, local
  payload rewrites, fallback providers, or unpublished tools.
- Use `postplus media schema --json` only when constructing or repairing an unknown request shape.
- Hosted media capability: