Add Seedance 2.5 desktop wire contracts - #1889
Open
matthewpenkala wants to merge 1 commit into
Open
Conversation
👷 Deploy request for artcraft-webapp pending review.Visit the deploys page to approve it
|
✅ Deploy Preview for storyteller-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for artcraft-dashboard ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
seedance_2p5_preview,seedance_2p5, andseedance_2p5_u.Why
The router supported the models, but the desktop request/event/task contracts did not represent all three variants end to end. That left deserialization and task/event metadata boundaries incomplete.
Validation
git diff --checkand contribution-scope scans pass.Origin and scope
This change was isolated from a broader downstream integration and reduced to a generic, self-contained upstream contribution. Private deployment/release-specific material and artifacts are intentionally excluded.