feat(make): add Suno music app, chat companion and review materials

[acedatacloud-dev]

Problem and behavior

Make users looking for Suno need a service-specific app with music inputs and task outputs; a generic chat sample or manual HTTP call does not provide that experience. Add an independently deployable Suno by Ace Data Cloud app project under examples/make/suno, alongside the original chat app. No cloud app, official listing, invite URL, or named AI Agent provider is claimed.

Implementation

• Suno modules: Generate Suno music submits one /suno/audios request with async=true, explicit model choice, no callback placeholder or model fallback; Get a Suno task queries the same ID and only exposes audio after the envelope is finished and all tracks succeeded; a universal module completes the app project.
• Allowlisted query outputs, internal-envelope log sanitization, and RuntimeError for Suno 429/5xx avoid exposing request/credential data or configuring automatic billed replays. Make transport failures and scenario replays still need user inspection.
• Self-contained manifest/Connection/parameters/interfaces, EN/ZH onboarding, three provenance-recorded screenshots, four-field Make acquisition links, brand/search proposal, and technical/Community publication worksheet. The parent remains the chat companion; there is one canonical Suno source in this repository, no duplicate service repo.
• Make schema CI checks both projects; normal script test discovery includes task-state, failure/preview, same-ID, interface and shared-contract regressions. Existing universal-module double-slash regression and pairing fixes remain included.

Validation (2026-10-18)

• Official pinned Make schemas 6ff5f3dd9960ccbeb24de3beb1cca935de89eaa0: parent 10 JSON + Suno 13 JSON pass.
• python3 -m unittest discover -s scripts/tests -v: 21 passed; Ruff lint/format and git diff --check passed. The limited expression simulation is not Make's actual IML engine.
• Suno model choices and async request checked against current Backend main f288eb461f15d057e9f5cedd634ce1e5c4959552, rather than stale local snapshots.
• Read-only lookup of an already-successful historical Suno task returned HTTP 200, object response, finished envelope and two succeeded tracks. Only sanitized shape/state evidence was retained. No generation or new charge was requested.
• SDK main remains 1a09bc80bd1e899db9d9fd159770e54f84bd7648. All nine checks passed at current head df0276f (including the empty-pending-envelope regression): https://github.com/AceDataCloud/SDK/actions/runs/39059594735 . The PR remains OPEN and mergeable.

Distribution and remaining acceptance

The official AI Agent API documents fixed provider enums and GET inspection routes, not a public named-provider onboarding route. A compatible connection is not a branded Ace provider entry. The native-provider facts and owner review route are recorded in the publication packet; no production provider config is fabricated.

Custom App review and Community distribution have distinct eligibility gates. Community policy explicitly allows multiple partner apps for a service, but requires current signed-partner eligibility; the historical FAQ is not a current approval guarantee. The proposed public label requires Make's brand/trademark decision. Public Publish is irreversible and legal confirmations remain with the authorized owner.

Both manifests have empty origins. Make zone, Suno app ID/version, organization/team, and development credential remain unpaired. Private installation, real IML execution, fresh module scenarios, token redaction inspection, separately approved paid generation/terminal media/unique billing, official listing and external install remain pending. The official screenshot is a Geocodify reference, not Ace runtime evidence.

No merge, production deployment, app creation, paid request, legal acceptance, or third-party outreach was performed. Git/source changes are reversible; public publishing is not part of this PR action. Adversarial review was not requested.