Update to PixVerse

{
  "description": "PixVerse Canvas: create, open, continue or edit a visual project with connected image/video nodes, references and native composition. Use for an explicitly selected Canvas workflow.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 287
    }
  ],
  "name": "pixverse-canvas",
  "skill_md_contents": "---\nname: pixverse-canvas\ndescription: \"PixVerse Canvas: create, open, continue or edit a visual project with connected image/video nodes, references and native composition. Use for an explicitly selected Canvas workflow.\"\n---\n\n# PixVerse Canvas\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 public entry to go directly into the Canvas workflow. Studio is not a prerequisite.\n\n## Installed Command\n\nBefore running helper commands, resolve the absolute plugin root from this `SKILL.md` path: it is two\ndirectories above this skill directory and contains `.codex-plugin/plugin.json`. In each new shell\nsession, set:\n\n```bash\nPVX=\"<absolute-plugin-root>/scripts/pvx\"\n```\n\nRun helpers through `\"${PVX}\"`, preserving the user's working directory. Do not assume the current\ndirectory is the plugin checkout or bypass the installed wrapper with a module invocation.\n\n## Direct Canvas Route\n\n1. Confirm that Canvas is the intended work target from the user's request or selected-project\n   continuation. An ambient browser tab or an old `.canvas-project.json` alone does not select this\n   route. An explicit non-Canvas request keeps its ordinary workflow.\n2. Read `../../skills-internal/pixverse-agent-canvas/SKILL.md` immediately. It is the single canonical\n   operating contract; follow it for binding, early browser handoff, graph operations, paid-work\n   authorization, cloud preview, recovery, and delivery. This entry does not define a second workflow.\n3. Before the first browser action, read `../../skills-shared/web-handoff.md`. Use the host's current\n   top-level Computer Use/CUA entrypoint when exposed, follow the documentation returned by its first\n   call, and apply the Codex IAB-only handoff and unavailable-browser fallback. With a resolved project,\n   make the early browser handoff the first visible milestone, not a final delivery step.\n\nDo not load Studio, Production, Delivery, or the full internal root merely to reach Canvas. Load other\nplaybooks only for a concrete need identified by the canonical Canvas contract. If that contract is\nalready loaded in this turn, continue from it without repeating initialization or browser handoff.\n\nThe canonical **Cloud Preview And On-Demand Delivery** rules override ordinary queue/local defaults\nonly for this selected Canvas target. Opening or inspecting a project is not permission to mutate or\ngenerate; creating media still follows the canonical preflight and effective confirmation policy.\n"
}