livepilot 1.21.4 → 1.22.1

package/CHANGELOG.md

@@ -1,5 +1,176 @@
 # Changelog
 
+## 1.22.1 — Bundled enrichment coverage gate (April 25 2026)
+
+Closes the one item carried from v1.22.0's atlas-separation work: a
+visibility + soft-gate for the drift between the atlas file's
+self-reported enrichment count and the YAML files on disk.
+
+### What changed
+
+Two enrichment numbers now surface in `sync_metadata --check`:
+
+- **`enriched=N`** (existing) — YAML profiles authored in `mcp_server/atlas/enrichments/`. Measures "what's available for merge."
+- **`bundled_enriched=N`** (new) — `stats.enriched_devices` from the shipped `mcp_server/atlas/device_atlas.json`. Measures "what the last scan_full_library run actually applied at build time."
+
+These measure different things. YAML count is authoring effort; bundled
+count is runtime coverage as of the atlas's last regeneration. They
+drift naturally (someone adds a YAML without re-scanning) — but until
+v1.22.1 the drift was invisible to CI.
+
+### Soft gate
+
+Warns (doesn't fail) on two conditions:
+
+1. **`bundled_enriched == 0`** with YAMLs on disk — scanner never ran
+   or failed completely. Most likely the repo's bundled atlas got
+   accidentally emptied or mis-committed.
+2. **`bundled_enriched / yaml_count < 50%`** — scanner truncated or had
+   severe pack-coverage failures. Current shipped atlas is 87/120 = 72%
+   coverage (healthy — the 33 orphan gap is the miditool-domain YAMLs
+   that Live's browser scanner can't see).
+
+Why soft: the relationship `yaml >= bundled` is only true in
+single-pack-scan scenarios. Multi-category duplication (native +
+max_for_live + user_library for the same device_id) can push
+`bundled > yaml`. Strict equality would produce false alarms. The soft
+gate catches the two real failure modes while staying silent on healthy
+cases.
+
+### Output format
+
+```
+Source of truth: version=1.22.1, tools=430, domains=53, bridge_cmds=31,
+                 enriched=120, bundled_enriched=87, genres=4, moves=44,
+                 analyzer_tools=38, atlas_devices=5264
+```
+
+Warnings (if any) print above the fail/pass line with a ⚠️ header,
+separate from the issue list. The exit code is unchanged — warnings
+don't fail CI.
+
+### Tests
+
+7 new TDD tests in `tests/test_claim_consistency.py`. Full suite: 3143
+pass (3136 prior + 7 new), 1 skipped.
+
+### Why this is a patch, not a feature
+
+Pure CI-gate tightening. Zero user-visible runtime behavior change;
+the only observable delta is one additional field in the banner plus
+the possibility of a soft-warning line during `sync_metadata --check`.
+No new tools, no atlas behavior change. The v1.22.0 user/bundled split
+is the feature release; v1.22.1 is its mechanical follow-through.
+
+## 1.22.0 — User atlas separation: ~/.livepilot/atlas/ (April 25 2026)
+
+First v1.22 release. Splits the device atlas into two files that serve
+different roles — a long-standing ambiguity that finally bit hard enough
+to be worth fixing at minor-version scope.
+
+### What changed
+
+**New: `~/.livepilot/atlas/device_atlas.json`** — the **user atlas**.
+Written by `scan_full_library` on your machine. Reflects YOUR installed
+packs, User Library, and plugins. Lives in the user-data directory
+(same convention as `~/.livepilot/memory/`) so `npm install livepilot`
+upgrades can't blow it away.
+
+**Unchanged: `mcp_server/atlas/device_atlas.json`** — the **bundled
+baseline**. Ships with the package (still 5264 devices, 120 enriched
+— stock Ableton 12 Suite inventory). Gives fresh installs a functional
+atlas before any personalized scan has run.
+
+**Resolution** at load time: user atlas wins if present, else bundled
+baseline falls through. Writes **always** go to the user path; the
+bundled path is read-only from the scanner's perspective.
+
+### Why this matters
+
+Prior to v1.22.0, the single `mcp_server/atlas/device_atlas.json` file
+served three conflicting roles — repo seed, personal scan cache, and
+runtime index. Three bugs resulted:
+
+1. **`npm install livepilot` wiped personal scans.** Every package
+   update overwrote the installed atlas with the bundled baseline. Users
+   who had carefully scanned their library (30-90 seconds per scan) lost
+   that work on every upgrade with no warning.
+2. **Dev installs polluted the repo.** Contributors running
+   LivePilot from a git checkout would scan their library (to test atlas
+   tools against live Ableton) and accidentally commit their personal
+   scan — pack names, user-library previews — to the public repo. This
+   happened once in the v1.21.x cycle and was the proximate trigger for
+   v1.22.
+3. **The "enriched" count ambiguity.** A single atlas file couldn't
+   honestly answer "how many devices are enriched?" — the right number
+   differed depending on whether you meant the bundled baseline (87 per
+   the scanner's last truncated pass), YAML files authored on disk (120),
+   or runtime coverage including native/M4L duplicates (137+ on a
+   fully-scanned install). The user/bundled split clarifies this by
+   letting each file carry its own honest count.
+
+### Migration for existing users
+
+Users with a personalized scan in `mcp_server/atlas/device_atlas.json`
+(most dev-install contributors) can migrate in one command:
+
+```bash
+mkdir -p ~/.livepilot/atlas
+cp "$(python3 -c 'import mcp_server.atlas; print(mcp_server.atlas.BUNDLED_ATLAS_PATH)')" \
+   ~/.livepilot/atlas/device_atlas.json
+# Then optionally restore the bundled baseline to its shipped state:
+git -C $(python3 -c 'import mcp_server.atlas, pathlib; print(pathlib.Path(mcp_server.atlas.__file__).parents[2])') \
+    checkout mcp_server/atlas/device_atlas.json
+```
+
+Users on the npm-installed path (no personalized scan yet) need nothing
+— the next `scan_full_library` call will write to the new user path
+automatically.
+
+### Code changes
+
+- `mcp_server/atlas/__init__.py` — new module-level constants
+  `BUNDLED_ATLAS_PATH`, `USER_ATLAS_DIR`, `USER_ATLAS_PATH`, and
+  function `_resolve_atlas_path()`. Existing `ATLAS_PATH` kept as a
+  backward-compat alias pointing at the resolved value.
+- `mcp_server/atlas/tools.py::scan_full_library` — writes to
+  `USER_ATLAS_PATH` and creates the user-data directory on demand.
+  Enrichments still read from the bundled package (they're authored
+  in-repo under `mcp_server/atlas/enrichments/`).
+
+### Tests
+
+8 new TDD regression tests in `tests/test_atlas_user_override.py`:
+
+- `test_bundled_path_is_in_package_dir`
+- `test_user_path_is_in_home_dir`
+- `test_resolver_returns_user_path_when_present`
+- `test_resolver_falls_back_to_bundled_when_user_atlas_missing`
+- `test_atlas_manager_loads_from_user_path_when_present`
+- `test_atlas_manager_falls_back_to_bundled_when_user_atlas_missing`
+- `test_scan_full_library_writes_to_user_path`
+- `test_user_atlas_dir_created_if_missing`
+
+Full suite: 3136 pass (3128 prior + 8 new), 1 skipped.
+
+### Documentation
+
+- `docs/manual/getting-started.md` — new "Step 5 (optional): Personalize
+  the device atlas" section.
+- `docs/manual/dev-install.md` — new "3a. User atlas vs bundled atlas"
+  subsection, critical for contributors.
+- `docs/manual/device-atlas.md` — header callout on the two-file split.
+- `CLAUDE.md` + `README.md` — short pointers to the new resolver.
+
+### Carried to future releases
+
+The atlas schema-canonicalization originally deferred from the v1.21.2
+audit is now **partially closed**: the user/bundled split makes the
+"which number counts as enriched?" question honest per-file, but the
+sync_metadata gate for `stats.enriched_devices` vs YAML file count
+hasn't been added. Deferred to a future patch because it's orthogonal
+to the user-atlas split.
+
 ## 1.21.4 — v1.21.2 audit carry-over: slashed-compound filler + dev-install runbook (April 25 2026)
 
 Ships two items the v1.21.2 audit #2 deferred to v1.22 but that turned

package/README.md

@@ -105,7 +105,7 @@ Most MCP servers are tool collections — they execute commands. LivePilot is an
 
 **M4L Bridge** (`m4l_device/`) — Optional Max for Live Audio Effect on the master track. Provides deep LOM access through Max's LiveAPI that the ControlSurface API can't reach. UDP 9880 (M4L to server) carries spectral data and LiveAPI responses. OSC 9881 (server to M4L) sends commands. The 38 spectral/analyzer tools strictly require the bridge; device and sample tools that call the bridge also have graceful fallbacks, so core functionality works without it. Backed by 31 bridge commands for hidden parameters, Simpler internals, warp markers, display values, and Simpler warp / Compressor sidechain writes that live on child objects Python can't reach.
 
-**Device Atlas** (`mcp_server/atlas/`) — In-memory indexed JSON database. 5264 devices with browser URIs, 120 enriched with YAML sonic intelligence profiles (mood, genre, texture, recommended chains). 7 indexes: by_id, by_name, by_uri, by_category, by_tag, by_genre, by_pack. Reverse-index `device_techniques_index.json` powers `atlas_techniques_for_device` (146 cross-references across 58 devices). The AI never hallucinates a device name or preset — it always resolves against the atlas first.
+**Device Atlas** (`mcp_server/atlas/`) — In-memory indexed JSON database. 5264 devices with browser URIs (bundled baseline), 120 enriched with YAML sonic intelligence profiles (mood, genre, texture, recommended chains). 7 indexes: by_id, by_name, by_uri, by_category, by_tag, by_genre, by_pack. Reverse-index `device_techniques_index.json` powers `atlas_techniques_for_device` (146 cross-references across 58 devices). The AI never hallucinates a device name or preset — it always resolves against the atlas first. **v1.22.0+**: run `scan_full_library` after install to index YOUR packs + User Library + plugins into `~/.livepilot/atlas/device_atlas.json` — your personal atlas overrides the baseline and survives npm updates.
 
 **Sample Engine** (`mcp_server/sample_engine/`) — Searches three sources simultaneously: BrowserSource (Ableton's library), SpliceSource (local Splice catalog via SQLite), FilesystemSource (user directories). Every result passes through a 6-critic fitness battery (key, tempo, spectral, genre, mood, technical). 29 processing techniques (Surgeon precision vs. Alchemist experimentation). Builds complete sample processing plans with warp, slice, and effect recommendations.
 

package/mcp_server/__init__.py

@@ -1,2 +1,2 @@
 """LivePilot MCP Server — bridges MCP protocol to Ableton Live."""
-__version__ = "1.21.4"
+__version__ = "1.22.1"

package/mcp_server/atlas/__init__.py

@@ -519,28 +519,75 @@ class AtlasManager:
 from pathlib import Path
 from ..services.singletons import Singleton
 
-ATLAS_PATH = Path(__file__).parent / "device_atlas.json"
+# v1.22.0: the atlas now has TWO possible homes —
+#
+#   BUNDLED_ATLAS_PATH — mcp_server/atlas/device_atlas.json
+#     Ships with the package. Gives fresh installs a functional
+#     baseline device index before any personalized scan has run.
+#     Updated only when the repo's canonical baseline is regenerated.
+#
+#   USER_ATLAS_PATH — ~/.livepilot/atlas/device_atlas.json
+#     Written by scan_full_library on the user's machine. Reflects
+#     their actual installed packs, User Library, and plugins. Lives
+#     in the user-data directory (same convention as
+#     ~/.livepilot/memory/) so npm updates can't blow it away.
+#
+# Resolution order at load time: user atlas wins if present, else
+# bundled baseline. Written scans ALWAYS go to the user path — never
+# the bundled path — so the repo/npm package stays clean regardless of
+# where a user runs scan_full_library from. This split lands in v1.22.0
+# and solves three prior issues (see tests/test_atlas_user_override.py
+# for the full rationale).
+BUNDLED_ATLAS_PATH = Path(__file__).parent / "device_atlas.json"
+USER_ATLAS_DIR = Path.home() / ".livepilot" / "atlas"
+USER_ATLAS_PATH = USER_ATLAS_DIR / "device_atlas.json"
+
+
+def _resolve_atlas_path() -> Path:
+    """Return the effective atlas path — user if present, bundled if not.
+
+    Called from _build_atlas and get_atlas. Kept as a module-level
+    function (rather than inlined) so tests can monkeypatch HOME and
+    reimport the module to re-evaluate USER_ATLAS_PATH cleanly.
+    """
+    if USER_ATLAS_PATH.exists():
+        return USER_ATLAS_PATH
+    return BUNDLED_ATLAS_PATH
+
+
+# Backward-compat alias. External code that imported ATLAS_PATH before
+# v1.22.0 (e.g. pre-existing scripts outside this repo) gets the
+# resolved path. Internal code should call _resolve_atlas_path() so the
+# value is re-evaluated after the user first runs scan_full_library.
+ATLAS_PATH = _resolve_atlas_path()
 
 _atlas_instance: Optional[AtlasManager] = None  # kept for legacy imports
 
 
 def _build_atlas() -> AtlasManager:
-    return AtlasManager(str(ATLAS_PATH))
+    return AtlasManager(str(_resolve_atlas_path()))
 
 
 _atlas_holder = Singleton(_build_atlas)
 
 
 def get_atlas() -> AtlasManager:
-    """Thread-safe accessor. Re-reads device_atlas.json if its mtime advanced."""
+    """Thread-safe accessor. Re-reads the resolved atlas path if its
+    mtime advanced. Uses the resolver, so if the user's first
+    scan_full_library call runs mid-session, the next get_atlas()
+    picks up the new user path (via invalidate_atlas, which
+    scan_full_library already calls on success)."""
     global _atlas_instance
-    instance = _atlas_holder.get(reload_if_newer=ATLAS_PATH)
+    instance = _atlas_holder.get(reload_if_newer=_resolve_atlas_path())
     _atlas_instance = instance   # keep legacy attribute in sync
     return instance
 
 
 def invalidate_atlas() -> None:
-    """Force the next get_atlas() to re-read device_atlas.json from disk."""
+    """Force the next get_atlas() to re-read the resolved atlas path
+    from disk. Called by scan_full_library after writing a fresh
+    user atlas so subsequent tool calls see the new data without
+    an MCP server restart."""
     global _atlas_instance
     _atlas_holder.invalidate()
     _atlas_instance = None

package/mcp_server/atlas/tools.py

@@ -466,11 +466,17 @@ def scan_full_library(
     """
     from .scanner import normalize_scan_results
     from .enrichments import load_enrichments, merge_enrichments
-    from . import AtlasManager
+    from . import AtlasManager, USER_ATLAS_DIR, USER_ATLAS_PATH
 
+    # v1.22.0: scans always write to the user atlas path, never the
+    # bundled baseline. The user-data directory is created on demand
+    # so a brand-new install (no ~/.livepilot/ at all) still works.
+    # Enrichments are read from the bundled package (same as before —
+    # they're authored in-repo).
     atlas_dir = os.path.dirname(os.path.abspath(__file__))
-    atlas_path = os.path.join(atlas_dir, "device_atlas.json")
     enrichments_dir = os.path.join(atlas_dir, "enrichments")
+    USER_ATLAS_DIR.mkdir(parents=True, exist_ok=True)
+    atlas_path = str(USER_ATLAS_PATH)
 
     if not force and os.path.exists(atlas_path):
         age = time.time() - os.path.getmtime(atlas_path)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "livepilot",
-  "version": "1.21.4",
+  "version": "1.22.1",
   "mcpName": "io.github.dreamrec/livepilot",
   "description": "Agentic production system for Ableton Live 12 — 430 tools, 53 domains, 44 semantic moves. Device atlas (5264 devices, 120 enriched, 7 indexes), Splice intelligence (gRPC + GraphQL describe-a-sound + preview + collections + presets), 9-band spectral perception auto-loaded via ensure_analyzer_on_master, Creative Director skill, technique memory, 12 creative intelligence engines",
   "author": "Pilot Studio",

package/remote_script/LivePilot/__init__.py

@@ -5,7 +5,7 @@ Entry point for the ControlSurface. Ableton calls create_instance(c_instance)
 when this script is selected in Preferences > Link, Tempo & MIDI.
 """
 
-__version__ = "1.21.4"
+__version__ = "1.22.1"
 
 from _Framework.ControlSurface import ControlSurface
 from . import router

package/server.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/dreamrec/LivePilot",
     "source": "github"
   },
-  "version": "1.21.4",
+  "version": "1.22.1",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "livepilot",
-      "version": "1.21.4",
+      "version": "1.22.1",
       "transport": {
         "type": "stdio"
       }