Use app-managed Suno web surface
This commit is contained in:
@@ -84,15 +84,15 @@ and explicitly apply the processed text before any Suno handoff.
|
|||||||
|
|
||||||
## Suno Boundary
|
## Suno Boundary
|
||||||
|
|
||||||
The initial requirement is browser/site handoff to the Suno Create page
|
The initial requirement is an app-managed web surface for the Suno
|
||||||
in Custom mode. The integration attempts to fill the supported title,
|
Create page in Custom mode. This avoids relying on a particular user
|
||||||
|
browser. The integration attempts to fill the supported title,
|
||||||
lyrics and style fields but does not press Generate. If a field cannot
|
lyrics and style fields but does not press Generate. If a field cannot
|
||||||
be filled, it returns a field-specific result so Presentation can report
|
be filled, it returns a field-specific result so Presentation can report
|
||||||
it and offer the approved text for copying. Treat this integration as
|
it and offer the approved text for copying. Treat this integration as
|
||||||
replaceable because website UI/behavior can change. The macOS
|
replaceable because website UI/behavior can change. The field filler is
|
||||||
Accessibility-based field filler is an adapter behind a protocol so it
|
an adapter behind a protocol so it can be replaced without changing
|
||||||
can be replaced without changing SongProject, prompt compilation or UI
|
SongProject, prompt compilation or UI review logic.
|
||||||
review logic.
|
|
||||||
|
|
||||||
## Instrument Selector Boundary
|
## Instrument Selector Boundary
|
||||||
|
|
||||||
|
|||||||
@@ -15,8 +15,9 @@ finalized.
|
|||||||
- Exact list of supported languages/dialects for MVP.
|
- Exact list of supported languages/dialects for MVP.
|
||||||
- Arabic diacritization policy: full tashkeel vs
|
- Arabic diacritization policy: full tashkeel vs
|
||||||
pronunciation-targeted tashkeel.
|
pronunciation-targeted tashkeel.
|
||||||
- Resolved: Suno handoff opens the browser-based Create page in Custom
|
- Resolved: Suno handoff presents the Create page in an app-managed web
|
||||||
mode and attempts to fill title, lyrics and style fields. It never
|
surface in Custom mode and attempts to fill title, lyrics and style
|
||||||
|
fields. It never
|
||||||
starts generation. Field-fill failures are reported with the
|
starts generation. Field-fill failures are reported with the
|
||||||
approved text available for copying.
|
approved text available for copying.
|
||||||
- Whether Suno integration is permitted/reliable under the intended
|
- Whether Suno integration is permitted/reliable under the intended
|
||||||
|
|||||||
+2
-1
@@ -19,7 +19,8 @@ instructions for Suno.
|
|||||||
4. User reviews and manually edits every generated component.
|
4. User reviews and manually edits every generated component.
|
||||||
5. Project versions are saved.
|
5. Project versions are saved.
|
||||||
6. User presses **Send to Suno**.
|
6. User presses **Send to Suno**.
|
||||||
7. The app opens the Suno Create page in Custom mode and fills the
|
7. The app presents the Suno Create page in an app-managed web surface
|
||||||
|
in Custom mode and fills the
|
||||||
supported title, lyrics and style fields. It does not trigger
|
supported title, lyrics and style fields. It does not trigger
|
||||||
Generate. If a field cannot be filled, the app reports that result
|
Generate. If a field cannot be filled, the app reports that result
|
||||||
and keeps its approved text ready for the user to copy.
|
and keeps its approved text ready for the user to copy.
|
||||||
|
|||||||
Reference in New Issue
Block a user