v2.0.0-stable — first extended stable release after the fork

[thunderdew-dawn]

v2.0.0-stable — first extended stable release after the fork

v2.0.0-stable is the first materially extended stable release of this maintained fork after the initial fork line.

This release marks the project’s transition from a focused FL Studio MCP prototype into a broader rollback-first FL Studio production assistant for MCP-compatible LLM clients. It stabilizes the expanded direction of the fork before the upcoming breaking rename and package/API cleanup in the v3.x line.

What this release represents

This is the last extended stable release before the breaking v3.x rename path.

The goal of v2.0.0-stable is not to pretend that FL Studio exposes more automation than it actually does. Instead, this release formalizes a safety-first contract:

• supported write operations should be scoped, reversible, and backed by snapshots where possible;
• API-exposed actions should be preferred over UI automation claims;
• unavailable FL Studio API features should be documented as boundaries, not simulated or overstated;
• LLM-facing workflows should use conservative defaults, readback where available, and explicit human approval for risky mutations.

Highlights

• Expanded MCP workflow coverage for real FL Studio production tasks.
• Rollback-first safety model for supported project mutations.
• Clearer API-boundary documentation for unavailable FL Studio actions.
• Stronger positioning as a production assistant, not only a MIDI/note sender.
• Knowledgebase-backed value handling for safer parameter conversion and reduced LLM guesswork.
• More explicit roadmap separation between stable, API-dependent, and rejected/not-planned capabilities.
• GitHub-based release, roadmap, and governance tracking prepared for the breaking v3.x line.

Stable user-facing areas

This release establishes the stable direction for:

• mix review and live peak-watch workflows;
• project cleanup, naming, color, and organization assistance where FL Studio exposes metadata;
• routing review and safe bus-layout proposals;
• composition and scale workflows through the supported bridge approach;
• plugin and preset assistance within FL Studio API limits;
• audio analysis via local file analysis;
• MIDI export and preflight/export-readiness reporting;
• snapshot/changelog/rollback handling for supported writes.

Important limitations

This release intentionally keeps FL Studio API limits visible.

The project does not claim support for actions that FL Studio does not expose through its scripting API, including automatic plugin loading, arbitrary playlist clip editing, deep Audio Clip internals such as Stretch/Normalize/source-path control, or automatic audio rendering to WAV.

Where those actions are not exposed, the project should provide suggestion, checklist, report, bridge, or manual workflow support instead of unsafe automation claims.

Fork and attribution note

This repository remains a maintained fork of rosasynthesiz/flstudio-mcp.

The upstream project provided the foundation for this work. v2.0.0-stable documents the point where this fork has grown into its own release path, safety model, roadmap, and product direction.

Migration note

The next major line, v3.x, is expected to be breaking.

Users who need the last extended stable release before the breaking rename should use v2.0.0-stable.

Users following active development should expect the v3.x line to standardize the new fls-pilot naming, commands, imports, controller names, and environment-variable conventions without retaining old compatibility aliases.