Skip to content

v3.0.0-beta.2

Pre-release
Pre-release

Choose a tag to compare

@thunderdew-dawn thunderdew-dawn released this 15 Jun 23:44
· 77 commits to v3/alpha since this release
d0e9cd5

fls-pilot v3.0.0-beta.2

This beta release is the next milestone in the fls-pilot v3 release train.

v3.0.0-beta.2 introduces the new Control Center, improves guided setup and read-only project review workflows, and continues to harden release readiness, documentation, safety wording, and GitHub project hygiene.

This is still a beta release. It does not mark the full v3.0 release effort as complete.

Highlights

  • Added the new Control Center as the recommended first-run and daily runtime surface.
  • Added guided setup and local readiness checks to make onboarding easier.
  • Added read-only project review panels for faster insight into FL Studio project state.
  • Improved the assistant-facing workflow model around Mix Review, Project Preflight, and Project Organizer proposal-mode flows.
  • Improved README restructured docs/ for better user faced information and user-guidance.
  • Continued release-train cleanup across CI, documentation, labels, project automation, and dependency maintenance.
  • Consolidated mcp server surface to user/dev environments scopes.
  • MCP Server now supports prompts and also context resources, and knowledge-base access for more LLM support (scope).

User-facing changes

The new Control Center makes - while still beta status - fls-pilot easier to start and understand.
It provides a local overview for setup checks, runtime status, ports, MCP snippets, and project-review information.

The Control Center is useful both with and without an AI agent. Without an agent, it exposes read-only access to useful fls-pilot review tools. With an agent, it helps visualize information, discuss findings, plan changes, and safely execute approved workflows.

Plugin and EQ automation guidance is clearer about a hard safety rule: unknown normalized parameter mappings must be verified instead of guessed, interpolated, or silently applied.

Safety and reliability

  • Reinforced the rule that normalized plugin/EQ parameter values must not be mapped without verified calibration data.
  • Kept persistent FL Studio writes approval-gated.
  • Added or refined CI permissions, project automation, docs builds, and release evidence.
  • Maintained the proposal-first workflow model for actions that can affect FL Studio projects.

Developer / maintenance notes

  • Version 3.0.0b2 is a breaking release.
  • do not expect anything! we refactored many smal and big things to prepare fls pilot for higher flights. :-)
  • Dev Docs are now separated from agent-docs for LLM scope Efficiency.
  • MCP prompts, context resources, and knowledge-base access were added.
  • dev tools are no longer published by default via mcp server.

Known limitations

  • This is still a beta release.
  • Full v3.0 release readiness is not complete yet.
  • Some Control Center review tools are still beta and intentionally read-only.
  • Risk scoring may still be incomplete or imprecise in some review panels.
  • fls-pilot must not infer unknown plugin parameter mappings without verified calibration data.

Upgrade notes

No migration step is expected for users of the previous beta.

For source installs, update to the v3.0.0-beta.2 release/tag and verify that the package version reports 3.0.0b2.

What's Changed

Breaking Changes

Safety and Release Gates

  • v3.0.0-beta.2 — New Control Center, Guided Setup, and Read-only Project Review Panels by @thunderdew-dawn in #114

Other Changes

Full Changelog: v3.0.0-beta.1...v3.0.0-beta.2

What's Changed

Breaking Changes

  • refactor: consolidate tool retirement logic into a dedicated module a… by @thunderdew-dawn in #112

Safety And Release Gates

  • v3.0.0-beta.2 — New Control Center, Guided Setup, and Read-only Project Review Panels by @thunderdew-dawn in #114

Other Changes

Full Changelog: v3.0.0-beta.1...v3.0.0-beta.2