Update to PixVerse

{
  "description": "Video delivery: recover PixVerse results, download existing assets, continue a project or package final files. Run media QA when explicitly requested.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 247
    }
  ],
  "name": "pixverse-delivery",
  "skill_md_contents": "---\nname: pixverse-delivery\ndescription: \"Video delivery: recover PixVerse results, download existing assets, continue a project or package final files. Run media QA when explicitly requested.\"\n---\n\n# PixVerse Delivery\n\nWhen this workflow generates images or video, apply `../../skills-shared/quality-policy.md`:\nSunburst 2K/high for images, Seedance 2.5 1080p with automatic prompt enhancement for video,\nand a stopped upgrade/fallback choice for Free/Basic or model-entitlement rejection.\n\n\nUse this to recover, inspect or export an existing project. Ordinary image/video generation completes directly in its creation workflow; it does not need this skill or QA. In this skill, load quality playbooks and perform inspection only when the user requests QA or a specialized workflow explicitly requires named checks. Editing requests enter `../pixverse-video-editing/SKILL.md` directly; production workflows own their final handoff.\n\nBefore any new paid generation or retry, follow `../../skills-shared/cli-workflow.md`.\n\nFor an explicitly selected Canvas target, use `../pixverse-canvas/SKILL.md` as the direct entry. If its\ninternal Canvas playbook is already loaded, continue under it without restarting the handoff or\nloading ordinary local-delivery playbooks merely because this entry was also selected.\n\n## Installed Command\n\nBefore running helper commands, resolve the absolute plugin root from this `SKILL.md` path: it is two directories above this skill directory and contains `.codex-plugin/plugin.json`. In every new shell session, set:\n\n```bash\nPVX=\"<absolute-plugin-root>/scripts/pvx\"\n```\n\nRun helper commands through `\"${PVX}\"`. Do not assume the user's current working directory is the plugin checkout, and do not bypass the installed wrapper with a module invocation.\n\n## Internal Playbooks\n\n- project memory, preferences, useful decisions, asset mapping, rejections: `../../skills-internal/pixverse-agent-project-memory/SKILL.md`\n- QA, inspection, retry logic, final delivery checks: `../../skills-internal/pixverse-agent-quality/SKILL.md`\n- stitching, subtitles, BGM, narration overlay, trimming, packaging: `../pixverse-video-editing/SKILL.md`\n- asset info, task ids, downloads, CLI syntax: `../../skills-internal/pixverse-agent-gateway/SKILL.md`\n- Canvas-native editing, graph reuse, composition, compression, and guarded mutation: `../../skills-internal/pixverse-agent-canvas/SKILL.md`\n\n## Canvas Delivery Routing\n\nApply this routing only when Canvas has been selected as the current target under the Canvas\nplaybook's activation boundary. Then prefer current executable capability-declared Canvas nodes such as\n`video_compose`, reuse the existing graph assets, and avoid\ndownload/edit/re-upload loops. Local finishing remains available for requirements the Canvas schema\ncannot express, an explicitly requested local master, or final delivery-only packaging. If a local\nfallback must return to Canvas, upload only its final result once.\n`video_compress` is currently a reserved, non-executable, non-authorable compatibility type and must\nnot be constructed or dispatched.\n\nFor every non-Canvas source project or ordinary queue delivery, skip Canvas capability discovery and\nretain the existing local preview, download, FFmpeg, subtitle, QA, assembly, and packaging workflow.\nAn unrelated or historical Canvas binding does not change that route.\n\nFor the explicit Canvas target, follow the Canvas skill's **Cloud Preview And On-Demand Delivery**\ncontract throughout delivery and recovery. Preview in Canvas; do not automatically download even\nintermediate assets, run local QA, refresh the balance, or assemble an invoice. Follow cloud status\nand reuse node/asset references. Use `project resume [hint] --surface canvas --format markdown` and\n`project handoff <slug> --surface canvas --format markdown`, not queue-only `qa project` or ledger\nrecovery. Report stage, cloud nodes, remaining work, and unverified technical properties. If IAB is\nunavailable, return the Canvas link without silently downloading or claiming visual QA passed.\n\nAutomatic Canvas review also follows **Preserve The User's Viewing State** in that playbook: no\nenlarged dialogs, zoom, fullscreen, or maximization without the user's explicit enlargement request.\nPreserve an already enlarged user view; failed controls leave checks unperformed, not permission to\nchange the viewing mode.\n\nAn explicit request for local files enables only the required export/download and targeted file QA;\ncredit reporting remains a separate opt-in. Record a completed file handoff with\n`--delivery-mode local --deliverable-path <actual-file>`; cloud completion does not need local media.\n\n## Ordinary Queue And Local Production Delivery Contract\n\nThe remaining queue/ledger workflow is for non-Canvas production. For requested Canvas file delivery,\napply only its relevant local file checks; keep the Canvas follow/recovery contract above.\n\n`queue run` downloads every successful generated asset under `projects/<slug>/assets/` and returns an absolute `local_path`. As soon as that path exists, show the primary image/video from the local file using the host's local-media syntax. Do not use the provider URL as the Codex inline preview source; it remains useful only for audit or external sharing. Do not hold the local preview behind deep QA, billing reconciliation, ledger recovery, packaging, or analysis. Use the returned result for ordinary delivery; only perform QA afterward when requested or explicitly required by a specialized workflow.\n\nIf `local_preview_status` is not `ready`, say that generation succeeded but local delivery failed. Retry the free `pixverse asset download` path by task id; do not regenerate and do not fall back to a remote URL for Codex display.\n\nWhen continuing an existing project, read memory before acting:\n\n```bash\n\"${PVX}\" project resume [title-or-slug-hint] --format markdown\n\"${PVX}\" project portfolio --format markdown\n\"${PVX}\" project search <slug> \"<asset, task id, style, rejection, or cue>\"\n\"${PVX}\" project ledger <slug> --format markdown\n```\n\nUse `project resume` first for “continue”, “the earlier one”, or a fuzzy title. It returns the likely project, stage, compact memory, latest assets, unresolved work, and one recommended next action without dumping provider payloads. Use `project portfolio` when multiple projects may match; reserve `project summary` for deep raw trace inspection.\n\nWhen QA is requested or a specialized workflow explicitly requires inspection, verify the relevant items:\n\n- promised generated assets exist as local files; a provider URL alone is not a completed Codex delivery\n- media type, aspect ratio, duration, and audio match the brief\n- product, character, UI, or text constraints survived well enough\n- the result obeys the user's intended aesthetic, including deliberate roughness, historical texture, or imperfect capture\n- no required reference, product plate, storyboard frame, or control mode was silently dropped\n- project memory records useful task ids, absolute local preview paths, provider URLs, and creative decisions\n- `project ledger <slug> --format markdown` or `queue run` output gives the final invoice-style asset ledger\n- retry recommendations are cost-aware and explicit\n\nFor local inspection:\n\n```bash\n\"${PVX}\" qa project <slug>\n\"${PVX}\" qa inspect <file-or-url> --project <slug>\n\"${PVX}\" qa inspect <video> --project <slug> --expect-duration <seconds> --expect-aspect-ratio <ratio>\n```\n\nWhen project QA is requested, prefer `qa project <slug>` for the latest completed run so technical checks, the generated-asset ledger, and the invoice are recovered together instead of one asset per host-tool call.\nWhen whole-project QA is requested after several generation batches, use `qa project <slug> --all-runs` to inspect every unique historical asset in one call; idempotent reruns are deduplicated while each asset keeps the expectations from its own quote.\n\nFor a non-Canvas story queue made of `shot-01`, `shot-02`, and later shots, close the local post-production loop in one call:\n\n```bash\n\"${PVX}\" story assemble <slug> --output projects/<slug>/deliverables/final-story.mp4 --sample-frames\n```\n\nIt reads ordered story assets from the latest ledger, reuses local downloads or downloads missing clips by task id, stitches them through FFmpeg, checks the combined duration, runs technical QA, samples the full timeline when requested, and records the deliverable in project memory. Pass ordered `--asset-id` values for an older run or explicit ordered `--clip` paths for a custom cut.\n\nFor subtitles and narration, use actual audio as the clock and an aligned SRT/ASS for rendering. Follow `../pixverse-captions/SKILL.md`; a caption-only edit does not regenerate voice. Use `../pixverse-voiceover/SKILL.md` and the segmented voice-queue helper below only for an explicit fixed-window take plan. Preserve spoken text and honor the requested display typography:\n\n```bash\n\"${PVX}\" subtitles clean projects/<slug>/prompts/narration.srt projects/<slug>/prompts/narration.clean.srt\n\"${PVX}\" subtitles inspect projects/<slug>/prompts/narration.clean.srt\n\"${PVX}\" subtitles style --format force-style\n\"${PVX}\" subtitles voice-queue projects/<slug>/prompts/narration.clean.srt projects/<slug>/voice-queue.json --project <slug> --segments-dir projects/<slug>/prompts/tts-segments --voice-id <voice_id> --language zh --speed 0.9\n```\n\nDo not end displayed subtitle lines with sentence punctuation unless the user explicitly asks for that typography.\n\nKeep generated media, manifests, quality reports, and notes under `projects/<slug>/`.\n\nAt the end of every meaningful stage—not only final delivery—show the project handoff:\n\n```bash\n\"${PVX}\" project handoff <slug> --stage <planning|character-lock|storyboard|control-assets|preview|render|final> --format markdown\n```\n\nThis makes editable plans, prompts, queues, project memory, QA/audit files, generated media, and deliverables visible instead of hiding project management inside the plugin.\n"
}