msty-admin-mcp 6.2.1__tar.gz → 6.2.2__tar.gz

{msty_admin_mcp-6.2.1 → msty_admin_mcp-6.2.2}/CHANGELOG.md

@@ -2,6 +2,28 @@
 
 ## Unreleased
 
+## v6.2.2 - 2026-11-10
+
+Safety release for Msty Studio 3.0.
+
+### Added
+
+- Studio version gate. The app version is parsed as numbers, so 10.0.0 sorts above 2.9.12. Studio 2.4 to 2.9.x is supported. Versions below 2.4 and from 3.0 on are unsupported. A missing, unreadable or over-long version is unknown.
+- `get_msty_installation` reports `layout` and `layout_status`.
+- Studio read results carry a warning when the version is unknown, because the data may be a stale copy.
+- macOS detection also looks for `~/Applications/MstyStudio.app`.
+
+### Changed
+
+- On Studio 3.x and below 2.4 every Studio storage read and write is refused with one clear message. Detection no longer falls back to the legacy `msty.db` files or a search of the `File System` folder, because after a 3.0 migration those may be stale copies.
+- Persona and prompt writes need a detected Studio 2.4 to 2.9.x. They are refused on other versions and when the version is unknown, and an explicit database path cannot bypass this. The JSON pack is still saved for import in Persona Studio.
+- On Windows and Linux the Studio version cannot be read yet, so Studio writes are refused there. Reads work as before and carry the stale-copy warning.
+- `recommend_model` still works on Studio 3.x. It recommends from hardware alone and notes that Studio usage was not used.
+- `get_status(scope=server)` reports `studio_target` as 2.4 to 2.9.x, with Studio 3.x detected and refused.
+- README warning about Studio 3.x, and the write conditions in the README name the Studio version check and Windows and Linux.
+
+Model, service, Nexus, calibration and Bloom tools are unchanged.
+
 ## v6.2.1 - 2026-11-02
 
 Glama tool-quality pass. 61 tools become 54.

{msty_admin_mcp-6.2.1 → msty_admin_mcp-6.2.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: msty-admin-mcp
-Version: 6.2.1
+Version: 6.2.2
 Summary: Comprehensive MCP server for administering Msty Studio Desktop 2.9+ with 54 tools, hardware-aware model install, Studio writes with confirm, insights analytics, Nexus bridge, Bloom evaluation, and a Cursor/Grok/Claude handoff for local models
 Author-email: M-Pineapple 🍍 <128090761+M-Pineapple@users.noreply.github.com>
 License: MIT
@@ -22,7 +22,7 @@ Description-Content-Type: text/markdown
 
 <img src="assets/logo.svg" alt="Msty Admin MCP logo" width="240"/>
 
-# Msty Admin MCP v6.2.1
+# Msty Admin MCP v6.2.2
 
 [![Licence: MIT](https://img.shields.io/github/license/M-Pineapple/msty-admin-mcp)](LICENSE)
 [![Python](https://img.shields.io/badge/Python-3.10+-3776AB?logo=python&logoColor=white)](https://www.python.org)
@@ -33,6 +33,9 @@ Description-Content-Type: text/markdown
 
 > Unofficial community project. Not affiliated with, or endorsed by, Msty. Msty is a trademark of its owner.
 
+> [!WARNING]
+> **Msty Studio 3.x is not supported yet.** Studio 3.0 can move workspaces to file-based storage, which this release cannot read safely. From v6.2.2 the server detects Studio 3.x and turns off every Studio read and write, so it never reports a stale copy as current or writes a row Studio 3.0 may reject. Model, service, Nexus, calibration and Bloom tools still work. Supported Studio versions are 2.4 to 2.9.x. Persona and prompt writes need a detected Studio 2.4 to 2.9.x, so they are refused when the version cannot be read. On Windows and Linux the Studio version cannot be read yet, so persona and prompt writes are refused there. Import the saved JSON pack in Persona Studio instead. If you rely on the Studio data tools, stay on the Studio 2.x update line for now. Studio 2.x installs stay on that line until you choose the 3.x track.
+
 <img src="assets/demo.gif" alt="msty-admin-mcp answering initialize and listing its tools" width="720"/>
 
 **Let the AI you already use plan, check and look after your local AI in Msty Studio, and let your local model ask for stronger help only when it needs it.**
@@ -204,7 +207,7 @@ Msty Studio users who want their usual AI app to help choose, test and organise
 
 - Inventory, analytics and free-form SQL stay **read only**. Credential columns always read as NULL. Secrets typed into free text, such as a chat message or a note, are out of scope.
 - Write tools always save a JSON pack under `~/.msty-admin/imports/` (mode `0600`, directory `0700`). `import_tool_config` and the tools, toolsets and skills keys of `import_studio_pack` never write the Studio database. Import that pack in Toolbox. Configs with `command`, `args` or `env` are flagged as running a program on your machine.
-- Personas and prompts insert into Studio SQLite only when both `confirm=true` and the operator env `MSTY_ALLOW_STUDIO_WRITES=1` are set. The LLM cannot set that env through a tool argument. Writes take a SQLite backup (including WAL) under `~/.msty-admin/backups/` and refuse while Msty Studio is running against the live database. Tests use fixture copies, never the live DB.
+- Personas and prompts insert into Studio SQLite only when `confirm=true`, the operator env `MSTY_ALLOW_STUDIO_WRITES=1` and a detected Studio 2.4 to 2.9.x are all present. On Windows and Linux the Studio version cannot be read yet, so these writes are refused there. The LLM cannot set that env through a tool argument. Writes take a SQLite backup (including WAL) under `~/.msty-admin/backups/` and refuse while Msty Studio is running against the live database. Tests use fixture copies, never the live DB.
 - `query_local_ai_service` is allow-listed (tags, version, show, chat). Pull and create go through `install_model` and `set_model_settings`, which also need `confirm=true`.
 - Calibration and Bloom history live under `~/.msty-admin/`, not in Studio.
 - Frontier needs `CURSOR_API_KEY` for Cursor, `XAI_API_KEY` for Grok, or `ANTHROPIC_API_KEY` for Claude. Keys stay in Msty's toolbox environment and never belong in this repository. In ask mode the Cursor agent does not send mail, move or delete files, or use trading tools.
@@ -235,7 +238,7 @@ If you already have Python 3.10+ as `python3`, `python3 -m venv .venv` is enough
 
 If `pip install msty-admin-mcp` cannot find the package, install the release straight from GitHub:
 ```bash
-pip install "msty-admin-mcp @ git+https://github.com/M-Pineapple/msty-admin-mcp@v6.2.1"
+pip install "msty-admin-mcp @ git+https://github.com/M-Pineapple/msty-admin-mcp@v6.2.2"
 ```
 
 ### With HTTP Transport
@@ -424,7 +427,7 @@ The admin server still has the Studio inventory tools. Add the Frontier server a
 ### Phase 2: Configuration (5)
 - `export_tool_config`: export a tool by name/id
 - `sync_claude_preferences`: Claude to Msty delta report
-- `generate_persona`: persona JSON pack. SQLite insert needs `confirm=true` and `MSTY_ALLOW_STUDIO_WRITES=1`
+- `generate_persona`: persona JSON pack. SQLite insert needs `confirm=true`, `MSTY_ALLOW_STUDIO_WRITES=1` and a detected Studio 2.4 to 2.9.x, so it is refused on Windows and Linux
 - `import_tool_config`: JSON pack for Toolbox. Never writes the Studio database
 - `import_studio_pack`: tools, toolsets and skills stay in the JSON pack. Personas and prompts need the env gate
 
@@ -497,7 +500,7 @@ v6 ships unit tests for path resolution, read-only SQL guards, redaction, invent
 **A**: No. v6 targets Studio 2.9+ (works on 2.4+ layouts when the File System DB is present). Use v4.x for older process-based detection.
 
 ### Q: Does this write to the Studio database?
-**A**: Inventory and analytics stay read-only. Write tools always save a JSON pack under `~/.msty-admin/imports/`. Tools, toolsets and skills are import-file only. Personas and prompts insert into Studio SQLite only with `confirm=true` and `MSTY_ALLOW_STUDIO_WRITES=1` in the MCP server environment, after a timestamped SQLite backup that includes WAL, and they refuse while Msty Studio is running against the live database. Quit Studio first, or import the JSON pack in Persona Studio or Toolbox.
+**A**: Inventory and analytics stay read-only. Write tools always save a JSON pack under `~/.msty-admin/imports/`. Tools, toolsets and skills are import-file only. Personas and prompts insert into Studio SQLite only with `confirm=true`, `MSTY_ALLOW_STUDIO_WRITES=1` in the MCP server environment and a detected Studio 2.4 to 2.9.x, after a timestamped SQLite backup that includes WAL, and they refuse while Msty Studio is running against the live database. Quit Studio first, or import the JSON pack in Persona Studio or Toolbox. On Windows and Linux the Studio version cannot be read yet, so these writes are refused there.
 
 ### Q: What is the Nexus integration?
 **A**: [Msty Nexus](https://msty.ai/nexus/) is the local runtime/gateway. `get_nexus` detects it. `list_models` with `backend=nexus` lists models on its OpenAI-compatible endpoint (`MSTY_NEXUS_PORT`).

{msty_admin_mcp-6.2.1 → msty_admin_mcp-6.2.2}/README.md

@@ -2,7 +2,7 @@
 
 <img src="assets/logo.svg" alt="Msty Admin MCP logo" width="240"/>
 
-# Msty Admin MCP v6.2.1
+# Msty Admin MCP v6.2.2
 
 [![Licence: MIT](https://img.shields.io/github/license/M-Pineapple/msty-admin-mcp)](LICENSE)
 [![Python](https://img.shields.io/badge/Python-3.10+-3776AB?logo=python&logoColor=white)](https://www.python.org)
@@ -13,6 +13,9 @@
 
 > Unofficial community project. Not affiliated with, or endorsed by, Msty. Msty is a trademark of its owner.
 
+> [!WARNING]
+> **Msty Studio 3.x is not supported yet.** Studio 3.0 can move workspaces to file-based storage, which this release cannot read safely. From v6.2.2 the server detects Studio 3.x and turns off every Studio read and write, so it never reports a stale copy as current or writes a row Studio 3.0 may reject. Model, service, Nexus, calibration and Bloom tools still work. Supported Studio versions are 2.4 to 2.9.x. Persona and prompt writes need a detected Studio 2.4 to 2.9.x, so they are refused when the version cannot be read. On Windows and Linux the Studio version cannot be read yet, so persona and prompt writes are refused there. Import the saved JSON pack in Persona Studio instead. If you rely on the Studio data tools, stay on the Studio 2.x update line for now. Studio 2.x installs stay on that line until you choose the 3.x track.
+
 <img src="assets/demo.gif" alt="msty-admin-mcp answering initialize and listing its tools" width="720"/>
 
 **Let the AI you already use plan, check and look after your local AI in Msty Studio, and let your local model ask for stronger help only when it needs it.**
@@ -184,7 +187,7 @@ Msty Studio users who want their usual AI app to help choose, test and organise
 
 - Inventory, analytics and free-form SQL stay **read only**. Credential columns always read as NULL. Secrets typed into free text, such as a chat message or a note, are out of scope.
 - Write tools always save a JSON pack under `~/.msty-admin/imports/` (mode `0600`, directory `0700`). `import_tool_config` and the tools, toolsets and skills keys of `import_studio_pack` never write the Studio database. Import that pack in Toolbox. Configs with `command`, `args` or `env` are flagged as running a program on your machine.
-- Personas and prompts insert into Studio SQLite only when both `confirm=true` and the operator env `MSTY_ALLOW_STUDIO_WRITES=1` are set. The LLM cannot set that env through a tool argument. Writes take a SQLite backup (including WAL) under `~/.msty-admin/backups/` and refuse while Msty Studio is running against the live database. Tests use fixture copies, never the live DB.
+- Personas and prompts insert into Studio SQLite only when `confirm=true`, the operator env `MSTY_ALLOW_STUDIO_WRITES=1` and a detected Studio 2.4 to 2.9.x are all present. On Windows and Linux the Studio version cannot be read yet, so these writes are refused there. The LLM cannot set that env through a tool argument. Writes take a SQLite backup (including WAL) under `~/.msty-admin/backups/` and refuse while Msty Studio is running against the live database. Tests use fixture copies, never the live DB.
 - `query_local_ai_service` is allow-listed (tags, version, show, chat). Pull and create go through `install_model` and `set_model_settings`, which also need `confirm=true`.
 - Calibration and Bloom history live under `~/.msty-admin/`, not in Studio.
 - Frontier needs `CURSOR_API_KEY` for Cursor, `XAI_API_KEY` for Grok, or `ANTHROPIC_API_KEY` for Claude. Keys stay in Msty's toolbox environment and never belong in this repository. In ask mode the Cursor agent does not send mail, move or delete files, or use trading tools.
@@ -215,7 +218,7 @@ If you already have Python 3.10+ as `python3`, `python3 -m venv .venv` is enough
 
 If `pip install msty-admin-mcp` cannot find the package, install the release straight from GitHub:
 ```bash
-pip install "msty-admin-mcp @ git+https://github.com/M-Pineapple/msty-admin-mcp@v6.2.1"
+pip install "msty-admin-mcp @ git+https://github.com/M-Pineapple/msty-admin-mcp@v6.2.2"
 ```
 
 ### With HTTP Transport
@@ -404,7 +407,7 @@ The admin server still has the Studio inventory tools. Add the Frontier server a
 ### Phase 2: Configuration (5)
 - `export_tool_config`: export a tool by name/id
 - `sync_claude_preferences`: Claude to Msty delta report
-- `generate_persona`: persona JSON pack. SQLite insert needs `confirm=true` and `MSTY_ALLOW_STUDIO_WRITES=1`
+- `generate_persona`: persona JSON pack. SQLite insert needs `confirm=true`, `MSTY_ALLOW_STUDIO_WRITES=1` and a detected Studio 2.4 to 2.9.x, so it is refused on Windows and Linux
 - `import_tool_config`: JSON pack for Toolbox. Never writes the Studio database
 - `import_studio_pack`: tools, toolsets and skills stay in the JSON pack. Personas and prompts need the env gate
 
@@ -477,7 +480,7 @@ v6 ships unit tests for path resolution, read-only SQL guards, redaction, invent
 **A**: No. v6 targets Studio 2.9+ (works on 2.4+ layouts when the File System DB is present). Use v4.x for older process-based detection.
 
 ### Q: Does this write to the Studio database?
-**A**: Inventory and analytics stay read-only. Write tools always save a JSON pack under `~/.msty-admin/imports/`. Tools, toolsets and skills are import-file only. Personas and prompts insert into Studio SQLite only with `confirm=true` and `MSTY_ALLOW_STUDIO_WRITES=1` in the MCP server environment, after a timestamped SQLite backup that includes WAL, and they refuse while Msty Studio is running against the live database. Quit Studio first, or import the JSON pack in Persona Studio or Toolbox.
+**A**: Inventory and analytics stay read-only. Write tools always save a JSON pack under `~/.msty-admin/imports/`. Tools, toolsets and skills are import-file only. Personas and prompts insert into Studio SQLite only with `confirm=true`, `MSTY_ALLOW_STUDIO_WRITES=1` in the MCP server environment and a detected Studio 2.4 to 2.9.x, after a timestamped SQLite backup that includes WAL, and they refuse while Msty Studio is running against the live database. Quit Studio first, or import the JSON pack in Persona Studio or Toolbox. On Windows and Linux the Studio version cannot be read yet, so these writes are refused there.
 
 ### Q: What is the Nexus integration?
 **A**: [Msty Nexus](https://msty.ai/nexus/) is the local runtime/gateway. `get_nexus` detects it. `list_models` with `backend=nexus` lists models on its OpenAI-compatible endpoint (`MSTY_NEXUS_PORT`).

{msty_admin_mcp-6.2.1 → msty_admin_mcp-6.2.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "msty-admin-mcp"
-version = "6.2.1"
+version = "6.2.2"
 description = "Comprehensive MCP server for administering Msty Studio Desktop 2.9+ with 54 tools, hardware-aware model install, Studio writes with confirm, insights analytics, Nexus bridge, Bloom evaluation, and a Cursor/Grok/Claude handoff for local models"
 readme = "README.md"
 requires-python = ">=3.10"

{msty_admin_mcp-6.2.1 → msty_admin_mcp-6.2.2}/src/db.py

@@ -13,7 +13,14 @@ import time
 from pathlib import Path
 from typing import Any, Dict, List, Optional, Sequence, Tuple
 
-from src.paths import detect_msty_installation
+from src.paths import (
+    LAYOUT_UNKNOWN,
+    LAYOUT_UNSUPPORTED,
+    UnsupportedStudioLayout,
+    detect_msty_installation,
+    unknown_version_read_warning,
+    unsupported_layout_message,
+)
 
 # Only allow SELECT / WITH / PRAGMA for arbitrary query tool
 _SAFE_SQL = re.compile(r"^\s*(SELECT|WITH|PRAGMA)\b", re.IGNORECASE | re.DOTALL)
@@ -393,11 +400,32 @@ def names_credential_column(query: str) -> bool:
     return False
 
 
+def with_read_warning(payload: Any) -> Any:
+    """Add a stale-copy warning to a read result when the Studio version is unknown."""
+    if not isinstance(payload, dict):
+        return payload
+    try:
+        status = detect_msty_installation().layout_status
+    except Exception:
+        status = LAYOUT_UNKNOWN
+    if status == LAYOUT_UNKNOWN:
+        payload = dict(payload)
+        payload["warning"] = unknown_version_read_warning()
+    return payload
+
+
 def get_database_path(explicit: Optional[str] = None) -> Optional[Path]:
+    """Resolve the Studio SQLite path for reads.
+
+    Raises UnsupportedStudioLayout on Studio 3.x, even for an explicit path,
+    so no Studio-storage read runs against a layout this release cannot read.
+    """
+    install = detect_msty_installation()
+    if install.layout_status == LAYOUT_UNSUPPORTED:
+        raise UnsupportedStudioLayout(unsupported_layout_message(install.version))
     if explicit:
         path = Path(explicit)
         return path if path.exists() else None
-    install = detect_msty_installation()
     if install.database_path:
         return Path(install.database_path)
     return None

{msty_admin_mcp-6.2.1 → msty_admin_mcp-6.2.2}/src/paths.py

@@ -10,10 +10,11 @@ from __future__ import annotations
 import json
 import platform
 import plistlib
+import re
 import socket
 from dataclasses import asdict, dataclass, field
 from pathlib import Path
-from typing import Any, Dict, List, Optional
+from typing import Any, Dict, List, Optional, Tuple
 
 try:
     import psutil
@@ -30,6 +31,98 @@ DEFAULT_PORTS = {
 }
 
 
+# Studio storage layouts this release can read and write. Studio 3.x moved to
+# file-based workspace storage, which this MCP does not understand yet.
+UNSUPPORTED_MAJOR = 3
+SUPPORTED_MIN = (2, 4)
+SUPPORTED_BELOW = (UNSUPPORTED_MAJOR,)
+VERSION_MAX_LEN = 64
+VERSION_PART_MAX_DIGITS = 6
+
+LAYOUT_SUPPORTED = "supported"
+LAYOUT_UNSUPPORTED = "unsupported"
+LAYOUT_UNKNOWN = "unknown"
+
+_VERSION_RE = re.compile(r"^\s*v?(\d+(?:\.\d+)*)")
+
+
+class UnsupportedStudioLayout(RuntimeError):
+    """Raised when Studio storage access is refused for the detected version."""
+
+
+def parse_version(value: Optional[str]) -> Optional[Tuple[int, ...]]:
+    """Parse a dotted version into a numeric tuple, or None when unparseable.
+
+    Numeric tuples order 10.0.0 above 2.9.12, which a string compare does not.
+    """
+    if not isinstance(value, str) or len(value) > VERSION_MAX_LEN:
+        return None
+    match = _VERSION_RE.match(value)
+    if not match:
+        return None
+    parts = match.group(1).split(".")
+    if any(len(part) > VERSION_PART_MAX_DIGITS for part in parts):
+        return None
+    try:
+        return tuple(int(part) for part in parts)
+    except ValueError:
+        return None
+
+
+def layout_status(version: Optional[str]) -> str:
+    """Classify a Studio version.
+
+    Supported only for 2.4 <= version < 3. Anything below 2.4 or at 3.0 and
+    above is unsupported. A missing or unparseable version is unknown.
+    """
+    parsed = parse_version(version)
+    if parsed is None:
+        return LAYOUT_UNKNOWN
+    if SUPPORTED_MIN <= parsed < SUPPORTED_BELOW:
+        return LAYOUT_SUPPORTED
+    return LAYOUT_UNSUPPORTED
+
+
+def _is_pre_2_4(version: Optional[str]) -> bool:
+    parsed = parse_version(version)
+    return parsed is not None and parsed < SUPPORTED_MIN
+
+
+def unsupported_layout_message(version: Optional[str]) -> str:
+    """User-facing refusal text for unsupported Studio versions."""
+    if _is_pre_2_4(version):
+        return (
+            f"Msty Studio version {version} is older than 2.4. This MCP supports the Studio "
+            "2.4 to 2.9.x storage layout only, so Studio reads and writes are disabled. "
+            "Service, model and Nexus tools still work."
+        )
+    return (
+        f"Msty Studio 3.x detected (version {version}). This MCP supports the Studio 2.9 "
+        "storage layout only. Studio 3.0 file-based workspace storage is not supported yet, "
+        "so Studio reads and writes are disabled to avoid reading stale data or damaging your "
+        "workspace. Service, model and Nexus tools still work. Track support in the "
+        "msty-admin-mcp README."
+    )
+
+
+def unknown_version_read_warning() -> str:
+    """Warning added to Studio read results when the version cannot be read."""
+    return (
+        "Msty Studio version could not be read. These results come from the Studio 2.x "
+        "database and may be a stale copy if this machine runs Studio 3.x."
+    )
+
+
+def unknown_version_write_message() -> str:
+    """User-facing refusal text for Studio writes when the version cannot be read."""
+    return (
+        "Msty Studio version could not be read, so Studio writes are refused. Writes run only "
+        "on a detected Studio 2.4 to 2.9.x install, because Studio 3.x changed workspace "
+        "storage. On Windows and Linux the version cannot be read yet. "
+        "Import the saved JSON pack in Persona Studio instead."
+    )
+
+
 @dataclass
 class MstyInstallation:
     """Detected Msty Studio installation."""
@@ -48,6 +141,8 @@ class MstyInstallation:
     platform_info: Dict[str, Any] = field(default_factory=dict)
     service_ports: Dict[str, int] = field(default_factory=dict)
     schema_note: Optional[str] = None
+    layout: Optional[str] = None
+    layout_status: str = LAYOUT_UNKNOWN
 
     def to_dict(self) -> Dict[str, Any]:
         return asdict(self)
@@ -61,6 +156,7 @@ def get_msty_paths() -> Dict[str, Path]:
     if system == "Darwin":
         return {
             "app": Path("/Applications/MstyStudio.app"),
+            "app_user": home / "Applications" / "MstyStudio.app",
             "app_alt": Path("/Applications/Msty.app"),
             "data": home / "Library" / "Application Support" / "MstyStudio",
             "data_legacy": home / "Library" / "Application Support" / "Msty",
@@ -247,10 +343,14 @@ def detect_msty_installation() -> MstyInstallation:
     )
 
     app = paths.get("app")
+    app_user = paths.get("app_user")
     app_alt = paths.get("app_alt")
     if app and app.exists():
         install.app_path = str(app)
         install.version = read_app_version(app)
+    elif app_user and app_user.exists():
+        install.app_path = str(app_user)
+        install.version = read_app_version(app_user)
     elif app_alt and app_alt.exists():
         install.app_path = str(app_alt)
         install.version = read_app_version(app_alt)
@@ -285,16 +385,27 @@ def detect_msty_installation() -> MstyInstallation:
     if sidecar and sidecar.exists():
         install.sidecar_path = str(sidecar)
 
-    db = resolve_database_path(paths)
-    if db:
-        install.database_path = str(db)
-        if "File System" in str(db):
-            install.schema_note = (
-                "Studio stores the workspace SQLite under Chromium File System "
-                "(not legacy msty.db)."
-            )
-        else:
-            install.schema_note = "Using legacy msty.db path."
+    install.layout_status = layout_status(install.version)
+    if install.layout_status == LAYOUT_UNSUPPORTED:
+        # Studio 3.x (or below 2.4): never fall back to the 2.9 blob, legacy
+        # msty.db or an rglob search. Those files may be a stale copy.
+        install.layout = "unsupported_pre_2_4" if _is_pre_2_4(install.version) else "unsupported_3x"
+        install.schema_note = unsupported_layout_message(install.version)
+    else:
+        db = resolve_database_path(paths)
+        if db:
+            install.database_path = str(db)
+            if "File System" in str(db):
+                install.layout = "studio_2x_file_system"
+                install.schema_note = (
+                    "Studio stores the workspace SQLite under Chromium File System "
+                    "(not legacy msty.db)."
+                )
+            else:
+                install.layout = "legacy_msty_db"
+                install.schema_note = "Using legacy msty.db path."
+            if install.layout_status == LAYOUT_UNKNOWN:
+                install.schema_note = f"{unknown_version_read_warning()} {install.schema_note}"
 
     install.is_running = is_process_running("MstyStudio")
     install.installed = bool(install.app_path or install.data_path or install.database_path)