P3: Project metadata and timebase review/probe workflow

[thunderdew-dawn]

Source: Extension Ideas and API Consolidation review, 2026-06-08.

Classification: should implement cautiously.

Scope:

• Add a project metadata/timebase review and safe planning workflow.
• Read title/author/genre where available; probe whether setters exist before promising metadata writes.
• Treat time signature and PPQ as high-impact settings requiring explicit user approval, readback, changelog, and rollback where supported.

Acceptance criteria:

• Metadata setters remain probe-only unless documented and rollback-safe.
• Time signature/PPQ plans clearly state project interpretation risk.
• Any persistent write has scoped snapshot, readback, changelog, and rollback.

[thunderdew-dawn]

The FL Studio MIDI scripting API does expose read-only project metadata via general.getProjectTitle(), general.getProjectAuthor(), and general.getProjectGenre().

However, I do not see documented metadata setters for title, author, or genre. Therefore this should not be treated as a metadata write feature. A safe implementation should be read-only:

• add a small fl_get_project_metadata / project metadata report
• return title, author, genre where available
• explicitly report metadata writes as api-limited / setter not documented
• keep PPQ and time-signature changes as high-impact operations requiring explicit approval, readback, changelog, and rollback

Suggested resolution: either implement the small read-only metadata getter and then close this issue, or close it as “read-only metadata available; metadata setters not supported by the documented API.”