chore: release v1.0.0 (cross-platform, safety layer, documentation overhaul)

Author: thunderdew-dawn

CODE_OF_CONDUCT.md

@@ -0,0 +1,131 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -1,7 +1,7 @@
 # Contributing to flstudio-mcp
 
 Thanks for your interest in improving flstudio-mcp. This project is a Model
-Context Protocol server that lets Claude drive FL Studio 2025 — mixer, plugins,
+Context Protocol server that lets an AI assistant drive FL Studio 2025 — mixer, plugins,
 piano roll, routing, and project — through calibrated, safety-checked tools.
 Contributions of all kinds are welcome: bug reports, fixes, new tools, docs,
 and platform support.
@@ -11,6 +11,10 @@ This repository is the maintained `thunderdew-dawn/flstudio-mcp` fork of
 compatibility, but contributions should follow this fork's rollback-first
 safety layer, API-evidence discipline, and roadmap in `ROADMAP.md`.
 
+## Code of Conduct
+
+By participating in this project, you agree to abide by our [Code of Conduct](CODE_OF_CONDUCT.md). Please read it to understand the expectations for behavior in our community.
+
 ## Ways to contribute
 
 - **Report a bug** — open an issue with steps to reproduce, your FL Studio build, and the relevant Script output / server log.
@@ -35,13 +39,13 @@ You'll need the same environment as a user, plus an editable install:
 - Windows 10/11 or macOS 12+, FL Studio 2025+, Python 3.12
 - loopMIDI on Windows or the IAC Driver on macOS, with two ports named exactly
   FLStudioMCP RX and FLStudioMCP TX
-- Claude Desktop (or any MCP client) for end-to-end testing
+- An MCP client (like Claude Desktop or Cursor) for end-to-end testing
 
 Install steps: clone the repo, cd into it, run `scripts\install_windows.bat` or
 `./scripts/install_macos.sh`, then `pip install -e ".[audio]"` if you'll touch
 the audio analysis code. Wire the MIDI ports in FL (Options > MIDI Settings),
 confirm `[FLStudioMCP] Ready` in FL's Script output, start the bridge with
-`fl-studio-mcp-daemon`, then verify the link by asking Claude to call `fl_ping`.
+`fl-studio-mcp-daemon`, then verify the link by asking your AI assistant to call `fl_ping`.
 
 ## Project layout
 
@@ -72,7 +76,7 @@ Every tool that modifies the project must route through the snapshot → write 
 A good report includes:
 
 - FL Studio edition and build (e.g. Producer Edition v25.2.5 [build 5319])
-- What you asked Claude to do, and what happened vs. what you expected
+- What you asked the AI assistant to do, and what happened vs. what you expected
 - Relevant FL Script output and server/daemon logs
 - Whether fl_ping succeeds
 

README.md

@@ -1,21 +1,22 @@
 # flstudio-mcp
 
-**Control FL Studio with Claude: AI mixing, composition, and mix diagnosis through natural language.**
+**Control FL Studio with any MCP-compatible LLM: AI mixing, composition, and mix diagnosis through natural language.**
 
 ![version](https://img.shields.io/badge/version-1.0.0-blue)
-![status](https://img.shields.io/badge/status-beta-yellow)
+![status](https://img.shields.io/badge/status-stable-green)
 ![license](https://img.shields.io/badge/license-MIT-green)
 ![python](https://img.shields.io/badge/python-3.10+-blue)
-![platform](https://img.shields.io/badge/platform-Windows%20%7C%20macOS-blue)
+![Windows](https://img.shields.io/badge/Windows-0078D6?style=flat&logo=windows&logoColor=white)
+![macOS](https://img.shields.io/badge/macOS-000000?style=flat&logo=apple&logoColor=white)
 ![FL Studio](https://img.shields.io/badge/FL%20Studio-2025%2B-orange)
 
-![Claude diagnosing and fixing a mix in FL Studio](docs/demo.gif)
+![The LLM assistant diagnosing and fixing a mix in FL Studio](docs/demo.gif)
 
-*Claude diagnosing and fixing a mix in FL Studio through natural language.*
+*The LLM assistant diagnosing and fixing a mix in FL Studio through natural language.*
 
 ## Overview
 
-flstudio-mcp is a Model Context Protocol (MCP) server that lets Claude Desktop drive FL Studio 2025 directly — the mixer, plugins, piano roll, routing, and project — from plain-language requests. Ask for a mix diagnosis, a vocal chain, a chord progression in a particular scale, or a full arrangement, and Claude carries it out through FL's scripting API and a set of calibrated, safety-checked tools.
+flstudio-mcp is a Model Context Protocol (MCP) server that lets any MCP client (like Claude Desktop, ChatGPT, or Cursor) drive FL Studio 2025 directly — the mixer, plugins, piano roll, routing, and project — from plain-language requests. Ask for a mix diagnosis, a vocal chain, a chord progression in a particular scale, or a full arrangement, and the LLM assistant carries it out through FL's scripting API and a set of calibrated, safety-checked tools.
 
 It is genre- and producer-agnostic: nothing about it assumes a particular style of music.
 
@@ -45,7 +46,7 @@ fl-studio-mcp-daemon               :: start the bridge, keep it running
 .venv/bin/fl-studio-mcp-daemon     # start the bridge, keep it running
 ```
 
-Wire the two loopMIDI ports in FL (Options > MIDI Settings), arm `MCP_Apply` once in the piano roll, then ask Claude in plain language:
+Wire the two loopMIDI ports in FL (Options > MIDI Settings), arm `MCP_Apply` once in the piano roll, then ask the LLM assistant in plain language:
 
 > "Scan my mix and tell me what's wrong." — "Set up a vocal chain from my plugins." — "Export this arrangement to MIDI."
 
@@ -71,15 +72,15 @@ Full setup is below.
 - **Multi-track MIDI export** — generate a complete arrangement as a standard MIDI file to import.
 - **Multi-pattern arrangement** — create, name, clone, and mark sections.
 - **Note and chord writing** into the piano roll, with quantize to a grid (for new notes and existing ones).
-- **Composition in any scale or mode** — Western modes, pentatonic, ragas, maqam, and beyond — through the scale composer, where Claude supplies the notes for the requested scale.
+- **Composition in any scale or mode** — Western modes, pentatonic, ragas, maqam, and beyond — through the scale composer, where the LLM assistant supplies the notes for the requested scale.
 
 ### Audio analysis
 - Tempo and key estimation from an audio file.
 - Melody-to-MIDI transcription (CREPE pitch tracking, with a lighter fallback).
 
 The server exposes 117 tools across the production, mixing, composition, safety,
 and project-organization surface, plus 6 live resources (project, mixer,
-transport, channels, patterns, status) that Claude can read directly.
+transport, channels, patterns, status) that the LLM assistant can read directly.
 
 ## What sets it apart
 
@@ -89,7 +90,7 @@ flstudio-mcp is built as a mixing and production assistant, not only a note send
 
 These are properties of FL Studio's scripting API, stated plainly:
 
-- **Plugins, audio files, and rendering are UI-only.** FL's API cannot load a plugin, load an audio file, or render audio. The plugin and preset tools therefore *suggest* — you load the chosen plugin or preset, and Claude then configures it. Audio export is done manually (File > Export); Claude can analyze the rendered file afterward.
+- **Plugins, audio files, and rendering are UI-only.** FL's API cannot load a plugin, load an audio file, or render audio. The plugin and preset tools therefore *suggest* — you load the chosen plugin or preset, and the LLM assistant then configures it. Audio export is done manually (File > Export); the LLM assistant can analyze the rendered file afterward.
 - **Note writing is armed once per session.** A generated pyscript writes notes into the piano roll; FL exposes no API to run a pyscript, so you run "MCP_Apply" once from the piano roll's scripting menu at the start of a session.
 - **Micro-tonal and gamaka-heavy music is approximated.** Scales with intervals smaller than a semitone (e.g. Arabic maqam) are rounded to the nearest semitone, and traditions built on gamaka/ornamentation (e.g. Carnatic) get the *scale framework* — the correct swaras and intervals — not gamaka or micro-tonal rendering. That's a limit of 12-tone MIDI, not of the tools.
 
@@ -142,7 +143,7 @@ chmod +x scripts/install_macos.sh
 This script will copy the controller script, create a virtual environment (`.venv`), install the server inside it, and verify that the IAC Driver ports are online. It also pre-seeds the note-bridge script (`MCP_Apply.pyscript`) inside your FL Studio user data directory.
 
 > [!IMPORTANT]
-> **macOS Accessibility Permissions**: Since the note-writing tool simulates keyboard shortcuts (`Cmd+Opt+Y`) via `pyautogui` to trigger script runs in FL Studio, the application executing the MCP server (e.g., your terminal, iTerm, Warp, or the Claude/ChatGPT Desktop client app) must be granted Accessibility permissions. Go to **System Settings > Privacy & Security > Accessibility** and ensure the app you are running is enabled.
+> **macOS Accessibility Permissions**: Since the note-writing tool simulates keyboard shortcuts (`Cmd+Opt+Y`) via `pyautogui` to trigger script runs in FL Studio, the application executing the MCP server (e.g., your terminal, iTerm, Warp, or your MCP client app like Claude Desktop/ChatGPT) must be granted Accessibility permissions. Go to **System Settings > Privacy & Security > Accessibility** and ensure the app you are running is enabled.
 
 For optional audio/melody analysis extras:
 * Windows: `pip install -e ".[audio,audio-accurate]"`
@@ -158,11 +159,11 @@ For optional audio/melody analysis extras:
 
 ### 4. Connect to your MCP Client
 
-#### Option A: Claude Desktop (stdio)
+#### Option A: Claude Desktop, Cursor, or other stdio clients
 1. Start the MIDI bridge daemon (recommended so MIDI ports are held by a stable background process):
    * Windows: Run `fl-studio-mcp-daemon`
    * macOS: Run `.venv/bin/fl-studio-mcp-daemon`
-2. Configure Claude Desktop. Add this to your configuration file (Windows: `%APPDATA%\Claude\claude_desktop_config.json`, macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`):
+2. Configure your client (e.g., Claude Desktop). Add this to your configuration file (Windows: `%APPDATA%\Claude\claude_desktop_config.json`, macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`):
    ```json
    {
      "mcpServers": {
@@ -204,7 +205,7 @@ Verify the connection by asking your AI assistant to run `fl_ping`.
 |---|---|
 | loopMIDI ports not found / not detected | The two ports must be named **exactly** `FLStudioMCP RX` and `FLStudioMCP TX`. Recreate them in loopMIDI and re-run the installer. |
 | No `[FLStudioMCP] Ready` in FL's Script output | The controller isn't registered: set the `FLStudioMCP RX` input's **Controller type** to **FLStudioMCP** in MIDI Settings, confirm `device_FLStudioMCP.py` is in `Settings\Hardware\FLStudioMCP\`, then fully restart FL Studio. |
-| Claude can't reach FL / `fl_ping` fails | Make sure the daemon is running (`fl-studio-mcp-daemon`); check the transport matches (`FLSTUDIO_MCP_TRANSPORT=tcp` uses the daemon, unset uses direct MIDI); restart Claude Desktop after editing its config. |
+| The LLM assistant can't reach FL / `fl_ping` fails | Make sure the daemon is running (`fl-studio-mcp-daemon`); check the transport matches (`FLSTUDIO_MCP_TRANSPORT=tcp` uses the daemon, unset uses direct MIDI); restart your MCP client after editing its config. |
 | Note-writing does nothing | Run `MCP_Apply` once from the piano roll's scripting menu this session — it arms the note bridge. |
 | Audio tools error or are unavailable | Install the optional extras: `pip install -e ".[audio]"` (or `".[audio,audio-accurate]"`). |
 

ROADMAP.md

@@ -698,7 +698,7 @@ and compatibility with the safety contract.
    - Prefer generated reviewable script payloads over broad opaque commands.
 
 Tracking the full scope — eight phases shipping the MCP server, the scale/mode
-composition tools, the SKILL.md, evals, and the Claude Code plugin marketplace
+composition tools, the SKILL.md, evals, and plugin marketplaces
 bundle.
 
 Each phase is shippable on its own. Each ends with `python scripts/test_bridge.py`
@@ -715,7 +715,7 @@ minimum tool surface.
 - [x] Transport tools: ping, tempo get/set, play, stop, toggle, record,
       play-state, song-position get/set. **10 tools total.**
 - [x] `scripts/test_bridge.py` standalone harness.
-- [x] Install script for Windows. (macOS / Linux: not shipped — contributions welcome.)
+- [x] Install scripts for Windows and macOS.
 
 ## Phase 1 — Channel rack (~12 tools)
 
@@ -800,7 +800,7 @@ plugins; we expose the raw FL view and let the LLM map names.
 
 Genre- and producer-agnostic composition in any scale or mode: Western modes,
 pentatonic, the Carnatic melakarta and janya ragas, Arabic maqam, and beyond.
-Claude supplies the correct notes/intervals for the requested scale and writes
+the LLM assistant supplies the correct notes/intervals for the requested scale and writes
 them through the note bridge. Indian ragas are one supported family among many,
 not the headline.
 
@@ -826,11 +826,8 @@ so it ships inside the wheel.
 - [x] `skills/flstudio-production/SKILL.md` orchestration layer with deep
       content in `references/`. Under 500 lines.
 - [x] `evals/evals.json` — 10 questions exercising the full tool surface.
-- [ ] `.claude-plugin/marketplace.json` so this can live in
-      `rosasynthesiz-skills` as an installable plugin.
-- [x] `AGENTS.md` describing the agentic workflow for future Claude sessions
+- [x] `AGENTS.md` describing the agentic workflow for future AI assistant sessions
       working on this codebase.
-- [ ] Demo video and screenshots in `docs/`.
 - [x] GitHub Actions for linting and the standalone bridge tests (mock FL).
 - [x] Pin a known-working FL Studio version range in README.
 

docs/MIXING_ROUTING_REPORT.md

@@ -147,4 +147,4 @@ No delete operations are implemented.
 ## 8. Open housekeeping
 - The old heavy `_h_detect_cleanup` is now **dead code** in the controller
   (replaced by server-side judgement); remove on the next controller change.
-- New write tools require a **Claude Desktop restart** to register live.
+- New write tools require an **MCP client restart** to register live.