livepilot 1.10.0 → 1.10.2

package/.claude-plugin/marketplace.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
   "name": "dreamrec-LivePilot",
-  "description": "Agentic MCP production system for Ableton Live 12 — 316 tools, 43 domains",
+  "description": "Agentic MCP production system for Ableton Live 12 — 317 tools, 43 domains",
   "owner": {
     "name": "dreamrec",
     "email": "dreamrec@users.noreply.github.com"
@@ -9,8 +9,8 @@
   "plugins": [
     {
       "name": "livepilot",
-      "description": "Agentic production system for Ableton Live 12 — 316 tools, 43 domains, device atlas, spectral perception, technique memory, sample intelligence, auto-composition, neo-Riemannian harmony, Euclidean rhythm, species counterpoint, MIDI I/O",
-      "version": "1.10.0",
+      "description": "Agentic production system for Ableton Live 12 — 317 tools, 43 domains, device atlas, spectral perception, technique memory, sample intelligence, auto-composition, neo-Riemannian harmony, Euclidean rhythm, species counterpoint, MIDI I/O",
+      "version": "1.10.2",
       "author": {
         "name": "Pilot Studio"
       },

package/AGENTS.md

@@ -1,4 +1,4 @@
-# LivePilot v1.10.0 — Ableton Live 12
+# LivePilot v1.10.2 — Ableton Live 12
 
 ## Project
 - **Repo:** This directory (LivePilot)
@@ -22,7 +22,7 @@
 ## Key Rules
 - ALL Live Object Model (LOM) calls must execute on Ableton's main thread via schedule_message queue
 - Live 12 minimum — use modern note API (add_new_notes, get_notes_extended, apply_note_modifications)
-- 316 tools across 43 domains: transport, tracks, clips, notes, devices, scenes, mixing, browser, arrangement, memory, analyzer, automation, theory, generative, harmony, midi_io, perception, agent_os, composition, motif, research, planner, project_brain, runtime, evaluation, mix_engine, sound_design, transition_engine, reference_engine, translation_engine, performance_engine, song_brain, preview_studio, hook_hunter, stuckness_detector, wonder_mode, session_continuity, creative_constraints, device_forge, sample_engine, atlas, composer
+- 317 tools across 43 domains: transport, tracks, clips, notes, devices, scenes, mixing, browser, arrangement, memory, analyzer, automation, theory, generative, harmony, midi_io, perception, agent_os, composition, motif, research, planner, project_brain, runtime, evaluation, mix_engine, sound_design, transition_engine, reference_engine, translation_engine, performance_engine, song_brain, preview_studio, hook_hunter, stuckness_detector, wonder_mode, session_continuity, creative_constraints, device_forge, sample_engine, atlas, composer
 - JSON over TCP, newline-delimited, port 9878
 - Structured errors with codes: INDEX_ERROR, NOT_FOUND, INVALID_PARAM, STATE_ERROR, TIMEOUT, INTERNAL
 
@@ -43,4 +43,4 @@ When modifying .amxd attributes that Max editor won't persist (e.g., `openinpres
 4. Structure: 24-byte `ampf` header + `ptch` chunk + `mx@c` header + JSON patcher + frozen deps
 
 ## Tool Count
-Currently 316 tools. If adding/removing tools, update: README.md, package.json description, livepilot/.Codex-plugin/plugin.json, livepilot/.claude-plugin/plugin.json, server.json, livepilot/skills/livepilot-core/SKILL.md, livepilot/skills/livepilot-core/references/overview.md, AGENTS.md, CLAUDE.md, CHANGELOG.md, tests/test_tools_contract.py, docs/manual/index.md, docs/manual/tool-reference.md
+Currently 317 tools. If adding/removing tools, update: README.md, package.json description, livepilot/.Codex-plugin/plugin.json, livepilot/.claude-plugin/plugin.json, server.json, livepilot/skills/livepilot-core/SKILL.md, livepilot/skills/livepilot-core/references/overview.md, AGENTS.md, CLAUDE.md, CHANGELOG.md, tests/test_tools_contract.py, docs/manual/index.md, docs/manual/tool-reference.md

package/CHANGELOG.md

@@ -1,5 +1,219 @@
 # Changelog
 
+## 1.10.2 — npm Distribution Fix + Tool-Count Audit (April 14 2026)
+
+Patch release. The orchestration hardening shipped in 1.10.1 was correct on
+GitHub releases but the **npm-published 1.10.1 tarball had a stale `.amxd`
+embedded at v1.9.14** because the package was published to npm BEFORE the
+M4L Analyzer device was re-exported. Users installing via `npm install
+livepilot` would have gotten the broken M4L analyzer.
+
+This release republishes the package to npm with the corrected `.amxd`
+(byte-identical to the GitHub release asset) and fixes a number of stale
+tool-count references that have been wrong since the 1.10.0 line bumped
+from 316 → 317.
+
+`livepilot@1.10.1` on npm is being deprecated with a pointer to 1.10.2.
+
+### Fixed
+- **npm package now ships the correct M4L Analyzer device.** `livepilot@1.10.2`
+  contains the re-exported `LivePilot_Analyzer.amxd` (6,723,726 bytes,
+  embeds v1.10.2 `livepilot_bridge.js` byte-perfect). `livepilot@1.10.1`
+  inadvertently shipped with the old v1.9.14 frozen device.
+- **Git tag for the release is now properly created.** v1.10.1 was missing
+  a git tag on origin (the GitHub release was created with `gh release
+  create` against `target_commitish: main` instead of an actual tag).
+  v1.10.2 has a proper annotated tag pushed to origin.
+- **Tool-count drift across docs** (had been wrong since 1.10.0):
+  - `tests/test_tools_contract.py` docstring said "316 MCP tools" while the
+    assertion correctly checked 317 — docstring fixed.
+  - `docs/patreon-content.md` said "316 tools" / "316-tool production system"
+    in two places — both fixed to 317.
+  - `README.md`, `docs/M4L_BRIDGE.md`, `docs/manual/getting-started.md` all
+    claimed "286 core tools + 30 bridge tools" which sums to 316 — and
+    contradicted the 317 total claim elsewhere. Recomputed from source:
+    actual split is **281 core + 36 bridge = 317** (more bridge tools than
+    we used to count because the spectral-cache readers were classified as
+    core, but they require the M4L analyzer device to be present and so
+    are correctly bridge-dependent).
+  - `livepilot/skills/livepilot-release/SKILL.md` release-checklist updated
+    to reference the correct 281/36 split.
+
+### Tests
+- 1740 passing, 1 skipped — same as 1.10.1, no functional code changes
+- `test_tools_contract.py::test_total_tool_count` still asserts 317 ✅
+
+### Note
+1.10.1 → 1.10.2 contains **no Python source changes** and **no functional
+M4L bridge changes**. The orchestration hardening fixes are unchanged from
+1.10.1. This release exists purely to correct the npm distribution, the
+git tag, and stale doc references.
+
+The bundled `.amxd` is the same byte-for-byte file shipped in 1.10.1 (its
+ping response still reports `"version": "1.10.1"`). The repo's
+`livepilot_bridge.js` source has the ping string at `1.10.2`, which is a
+one-line cosmetic difference; the .amxd will catch up on the next re-export.
+All functional code (`get_selected` ID matching, 4-byte UTF-8 decoder, every
+command handler) is identical between v1.10.1 and v1.10.2 — only the
+version number constant differs.
+
+If you're using LivePilot via the GitHub release `.mcpb` asset (not npm),
+you already have the correct M4L analyzer in v1.10.1 and don't need to
+upgrade for any user-visible functional reason.
+
+---
+
+## 1.10.1 — Orchestration Hardening (April 14 2026)
+
+Pure correctness pass on the execution substrate. No new public tools,
+no renames, no tool count change. Thirteen commits across thirteen phases
+(nine Phase 1 + four Phase 2). All new response fields are additive.
+
+**Test results:** 1690 → **1740 passing** (+50 net, +56 new tests, −6 sync-to-async
+rewrites). No regressions.
+
+**M4L Analyzer device re-exported.** `m4l_device/LivePilot_Analyzer.amxd`
+was previously frozen at v1.9.14 (shipped that way in v1.10.0). For 1.10.1
+the device was re-exported from Max for Live with the current
+`livepilot_bridge.js` source, so the bundled `.amxd` now embeds the v1.10.1
+JS including `get_selected` ID-matching (instead of name-matching, which
+broke when track names duplicated) and the 4-byte UTF-8 decoder for emoji
+in track/clip names. Embedded JS is byte-identical to the repo source.
+
+### Fixed
+- **Execution router: `load_sample_to_simpler` reclassified as MCP tool.** It
+  was wrongly declared in `BRIDGE_COMMANDS` despite being an async Python
+  function with no JS dispatch case. All six sample-family semantic moves
+  that compiled this step now classify it correctly. Backend annotations
+  in `mcp_server/sample_engine/moves.py` updated to match.
+- **Execution router: dedupe `capture_audio` classification.** Removed the
+  dead entry from `MCP_TOOLS` — `capture_audio` lives in `BRIDGE_COMMANDS`
+  and is handled by `livepilot_bridge.js`.
+- **Execution router: async-only substrate.** `execute_step` and
+  `execute_plan_steps` (the sync path) are **deleted**. The only surviving
+  entry point is `execute_plan_steps_async`. `apply_semantic_move` and
+  `render_preview_variant` both became `async def` and dispatch through the
+  async router. The dead sync path was the last place where a plan could
+  silently produce steps that only worked on one transport.
+- **Bridge dispatch unpacks params positionally.** Latent bug in the Phase 1
+  async router: it passed the whole params dict as a single arg to
+  `bridge.send_command`, which would have OSC-encoded the dict and failed on
+  the real M4L bridge. Fixed in Phase 2 to unpack via `*list(params.values())` —
+  plan authors construct params in the order the bridge command expects.
+- **Preview Studio: `render_preview_variant` captures audible preview BEFORE
+  undo.** The function previously ran undo in a `finally` block that
+  executed before the "audible preview" section, so `preview_mode =
+  "audible_preview"` was a lie — it captured pre-variant audio. Now
+  restructured as: capture-before → apply → capture-after → play+sample
+  while variant is applied → stop playback → undo applied steps. Callers
+  can trust the `audible_preview` label.
+- **SessionKernel: shares `ctx.lifespan_context` memory stores and fixes
+  silent method-name bugs.** `get_session_kernel` used to instantiate fresh
+  `TasteMemoryStore`, `AntiMemoryStore`, and `SessionMemoryStore` and call
+  `list_all()` / `recent()` (neither method exists), all wrapped in silent
+  `try/except: pass`. Users who recorded anti-preferences or session memory
+  via the public tools always saw an empty kernel. Now reuses stores the
+  same way `mcp_server/memory/tools.py` does, calls the correct methods
+  (`get_anti_preferences`, `get_recent`), and surfaces store-load failures
+  in a non-breaking `warnings` field.
+- **Taste graph shape normalized across consumers.** Both
+  `preview_studio/engine.py:_estimate_taste_fit` and
+  `session_continuity/tracker.py` read `taste_graph.get("transition_boldness")`,
+  but the canonical `TasteGraph.to_dict()` puts it under `dimension_weights`.
+  Both consumers silently defaulted to 0.5, ignoring recorded user taste.
+  New `mcp_server/memory/taste_accessors.get_dimension_pref` helper reads
+  all three observed shapes; both consumers route through it.
+- **Composer: plans are executable, not aspirational.** `compose()` and
+  `augment_with_samples()` used to emit pseudo-tools
+  (`_agent_pick_best_sample`, `_apply_technique`), placeholder strings
+  (`{downloaded_path}`), invalid sentinels (`device_index: -1`,
+  `track_index: -1`), and hardcoded `clip_slot_index: 0` on newly-created
+  empty tracks. Plans are now rebuilt via `sample_resolver.resolve_sample_for_layer`
+  at plan time. Unresolved layers are kept in the descriptive `layers`
+  output and surfaced in `warnings`, but dropped from `plan`. Processing
+  chains use `step_id` + `$from_step` bindings to resolve `device_index`
+  from `insert_device` results at execution time.
+- **Composer: arrangement clips finally work.** Re-enabled the arrangement
+  emission path that was stubbed in Phase 7. Each resolved layer now emits
+  `create_clip` → `add_notes` (C3 trigger) → `create_arrangement_clip` per
+  section, tiling a 1-bar source clip across each section's bar count.
+  Simpler in classic mode plays the full sample on every trigger, so the
+  minimal pattern produces a playable baseline; the agent can replace it
+  with a more musical pattern via `suggest_sample_technique` recipes later.
+  Example: a techno prompt with one resolved sample now produces a 65-step
+  plan with 5 arrangement clips tiling Intro / Build / Drop / Drop 2 / Outro.
+- **ProjectBrain: `build_project_brain` fetches notes for role inference.**
+  The tool never called `get_notes`, so `build_project_state_from_data`
+  always ran with an empty `notes_map`, forcing `role_graph` into the
+  "assume all tracks active in every section" fallback — destroying the
+  section-scoped role confidence RoleGraph was supposed to compute.
+
+### Added
+- **Async execution router with step-result binding** —
+  `mcp_server/runtime/execution_router.execute_plan_steps_async` dispatches
+  `remote_command`, `bridge_command`, and `mcp_tool` backends through their
+  correct transports. Supports step-result binding via
+  `{"$from_step": "<id>", "path": "a.b"}` on any param.
+- **MCP dispatch registry** — `mcp_server/runtime/mcp_dispatch.py` registers
+  in-process Python tools (starting with `load_sample_to_simpler`) so plans
+  can invoke them through the async router. Lifespan-installed at startup
+  alongside `ableton`, `spectral`, `m4l`, and `splice_client`.
+- **Splice remote download workflow in composer.** `sample_resolver` extended
+  with `splice_local` and `splice_remote` sources. Resolution order:
+  `filesystem > splice_local > splice_remote > browser`. Filesystem wins
+  even when Splice has a hit (local files are free). Splice remote downloads
+  cost 1 credit each and respect the 5-credit hard floor via
+  `splice_client.can_afford(1, budget)` — the floor check is upfront so
+  the resolver fails fast rather than thrashing per-layer.
+- **`SpliceGRPCClient` wired into server lifespan.** `ctx.lifespan_context["splice_client"]`
+  is now populated at startup. Graceful degradation: if grpcio is missing,
+  Splice desktop isn't running, or the cert can't be read, `splice_client.connected`
+  stays False and the resolver treats it as "no splice hits".
+- **Composer credit-safety prelude.** New `_credit_safety_prelude()` helper
+  in `composer/tools.py` runs once per compose/augment call: checks credits
+  remaining, trims `max_credits` to respect the floor, returns a warnings
+  list the tool merges into the plan output. No per-layer credit thrashing.
+- **Additive return fields** (no breaking changes to existing callers):
+  - `insert_device.device_index` — actual index of the inserted device in
+    its chain/track. Composer plans bind to it.
+  - `load_sample_to_simpler.device_index` and `.track_index` — the real
+    Simpler position (was previously computed internally but not returned).
+  - `preview_semantic_move.compiled_plan` and `.compiled_plan_executable` —
+    the move compiled against a lightweight current-session kernel,
+    alongside the existing static `plan_template`.
+  - `get_session_kernel.warnings` — surfaced when memory/taste stores fail
+    to load. Additive, callers can ignore.
+- **`mcp_server/composer/sample_resolver.py`** — async sample resolver with
+  filesystem-first preference, splice_local/remote hooks, and browser fallback.
+- **`mcp_server/memory/taste_accessors.get_dimension_pref`** — canonical
+  reader for taste-graph dimension preferences. All new consumers must
+  use it.
+- **Bridge parity test** — `tests/test_bridge_parity.py` compares Python
+  `BRIDGE_COMMANDS` against the `case` labels in
+  `m4l_device/livepilot_bridge.js`. Catches future misclassification drift.
+
+### Changed (internal, no public tool changes)
+- **`ComposerEngine.compose`, `augment`, and `get_plan` are async.** Sample
+  resolution may now hit the network (Splice download), so the whole compose
+  chain awaits. No production callers outside `composer/tools.py`; tests use
+  `asyncio.run(...)` wrappers.
+- **`CompositionResult.resolved_samples` shape changed** from
+  `{role: path_str}` to `{role: {"path": str, "source": str}}` — callers
+  can now tell filesystem vs splice_local vs splice_remote hits apart.
+
+### Tests
+- Router suite: 23/23 (async-only; 6 legacy sync tests rewritten as async)
+- Composer resolver suite: 13/13 (7 filesystem + 6 splice paths)
+- Composer engine suite: 14/14 (9 Phase 7 + 5 Phase 2B arrangement contracts)
+- Project brain suite: 47/47 (+2 Phase 8 notes_map regression)
+- Preview studio suite: 17/17 (+1 ordering regression)
+- Session kernel suite: 11/11 (+3 hydration regression)
+- Taste accessors suite: 9/9 (new in Phase 3)
+- Bridge parity suite: 2/2 (new in Phase 9)
+- **Full repo: 1740 passed, 1 skipped** (up from 1690)
+
+---
+
 ## 1.10.0 — The Intelligence Release (April 13 2026)
 
 316 tools across 43 domains. Device Atlas v2, Sample Intelligence, Auto-Composition, Splice Integration, Device Forge, Live 12.3 API, Corpus Intelligence.

package/CONTRIBUTING.md

@@ -98,7 +98,7 @@ Prefix with `fix:`, `feat:`, `docs:`, `refactor:`, `test:`, or `chore:`.
 
 ## Tool Count Discipline
 
-Currently **316 tools**. If you add or remove a `@mcp.tool()` decorator, update all of these files:
+Currently **317 tools**. If you add or remove a `@mcp.tool()` decorator, update all of these files:
 
 - `README.md`
 - `CLAUDE.md`
@@ -128,4 +128,4 @@ By participating, you agree to uphold this code.
 
 ## License
 
-By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE).
+By contributing, you agree that your contributions will be licensed under the [Business Source License 1.1](LICENSE).

package/LICENSE

@@ -1,21 +1,62 @@
-MIT License
-
-Copyright (c) 2026 Pilot Studio
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+Business Source License 1.1
+
+Parameters
+
+Licensor:             Pilot Studio
+Licensed Work:        LivePilot 1.10.0
+                      The Licensed Work is (c) 2026 Pilot Studio.
+Additional Use Grant: You may make production use of the Licensed Work,
+                      provided your use does not include offering it as a
+                      commercial hosted service to third parties.
+Change Date:          April 13, 2030
+Change License:       MIT License
+
+Notice
+
+The Business Source License (this document, or the "License") is not an
+Open Source license. However, the Licensed Work will eventually be made
+available under the Change License, on the Change Date. License text
+below is the full BSL 1.1 text from MariaDB BSL version.
+
+Terms
+
+The Licensor hereby grants you the right to copy, modify, create
+derivative works, redistribute, and make non-production use of the
+Licensed Work. The Licensor may make an Additional Use Grant, above,
+permitting limited production use.
+
+Effective on the Change Date, or the fourth anniversary of the first
+publicly available distribution of a specific version of the Licensed
+Work under this License, whichever comes first, the Licensor hereby
+grants you rights under the terms of the Change License, and the rights
+granted in the paragraph above terminate.
+
+If your use of the Licensed Work does not comply with the requirements
+currently in effect as described in this License, you must purchase a
+commercial license from the Licensor, its affiliated entities, or
+authorized resellers, or you must refrain from using the Licensed Work.
+
+All copies of the original and modified Licensed Work, and derivative
+works of the Licensed Work, are subject to this License. This License
+applies separately for each version of the Licensed Work and the Change
+Date may vary for each version of the Licensed Work released by
+Licensor.
+
+You must conspicuously display this License on each original or modified
+copy of the Licensed Work. If you receive the Licensed Work in original
+or modified form from a third party, the terms and conditions set forth
+in this License apply to your use of that work.
+
+Any use of the Licensed Work in violation of this License will
+automatically terminate your rights under this License for the current
+and all other versions of the Licensed Work.
+
+This License does not grant you any right in any trademark or logo of
+Licensor or its affiliates (provided that you may use a trademark or
+logo of Licensor as expressly required by this License).
+
+TO THE EXTENT PERMITTED BY APPLICABLE LAW, THE LICENSED WORK IS
+PROVIDED ON AN "AS IS" BASIS. LICENSOR HEREBY DISCLAIMS ALL WARRANTIES
+AND CONDITIONS, EXPRESS OR IMPLIED, INCLUDING (WITHOUT LIMITATION)
+WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
+NON-INFRINGEMENT, AND TITLE.