Repository navigation
Align Suno API capabilities and branding - #2
Merged
Merged
Conversation
8 of 12 tasks
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
1 participant
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.
Align Suno with the current API/MCP contract and existing system branding. Request schemas preserve unions and conditional inputs; tools expose structured outputs and task/batch states. No logo is generated or redrawn.
Validation: 46 passed, 1 warning in 1.36s; Ruff, SDK registration, official Marketplace package validator, and installation of the exact packaged artifact in serverless mode passed. Package SHA256:
1932c4d2e528d2145c05290deb4648ad4763ffaac3f214dd62125a3e9e276680.Real Dify CE 1.17.1 browser runs, final service status, unmodified screenshots, media decoding and owned-credential billing reconciliation are in tests/e2e-audit.json. This audit records 9 browser workflows for this plugin; historical primary-operation evidence remains in tests/e2e-results.json. Task-query regressions reuse previous successful generations and never repeat their charges. Recorded failures and corrections remain visible. Optional untested model/action combinations are not claimed as passed.
Source merge is authorized after current-head CI. Official Marketplace approval/publication and Marketplace-install verification are separate outstanding gates.
No production deployment, maintainer-approval bypass or agreement attestation is included. Local implementation review completed; no separate adversarial-review agent was requested.