[superche]

Summary

• add Seedance 2.5 to the video model catalog and make it the default generation model
• remove pippit/seedance-2.0-fast from public catalogs and request schemas because the upstream model has no available capacity
• keep video editing on Seedance 2.0 Vision by default, while preserving explicit Seedance 2.5 native partial edits
• normalize Seedance 2.5 request fields inside the TypeScript SDK
• re-upload generated source videos before editing so the edit uses a fresh linked EverPhoto asset_id and Pippit pippit_asset_id
• expose deterministic internal runtime hashes and richer upstream diagnostics for Dev App verification
• update MCP, ChatGPT App, OpenCode, widget, documentation, contracts, and tests

Why

The /skill/submit_run video validation path hydrates references through the Pippit asset library and requires a resolvable EverPhoto source. A generated thread artifact can expose both IDs without its Pippit asset record being upload-backed, which caused edits of successfully generated videos to fail with 视频素材信息缺失，请重新上传后重试.

The skill endpoint also interprets top-level asset_ids as Pippit asset-library IDs. They are distinct from the nested EverPhoto/cloud asset_id values and cannot be interchanged.

This change sends generated edit sources back through the ordinary upload path and centralizes the upstream ID/request normalization in the SDK. The OpenRouter Facade continues to express ordinary generation or edit semantics without depending on provider protocol details.

Impact

• ordinary video generation defaults to Seedance 2.5
• video segment editing defaults to Seedance 2.0 Vision
• edit submissions incur one controlled source-video download and upload before generation
• Dev App error cards and diagnostics include stable internal versions and upstream Log IDs
• no production marketplace activation or npm publication is included

Validation

• npm test -w @pippit-bridge/sdk — 21 passed
• npm test -w @pippit-bridge/openrouter-facade — 87 passed
• env PATH=/Users/bytedance/.nvm/versions/node/v24.15.0/bin:/usr/bin:/bin npm run codex:dev:full-gate
  • MCP tests: 160 passed
  • plugin contract check: passed
  • Dev gateway smoke: passed
• cold-started the isolated Codex Dev App and verified matching cache/gateway/Facade artifacts
• manual Dev App acceptance: passed