Rename LabDAQ → LabUI and overhaul plugin system

Branding:
- Rename app, window title, file extension (.labdaq → .labui), user data
  dirs (~/.labui/), spec file (labdaq.spec → labui.spec), and APP_NAME
  throughout all source, docs, and config files

Plugin system:
- Plugins no longer bundled in the PyInstaller build — installed at
  runtime by users via Settings → Plugins → Install Plugin (zip)
- PluginManager now takes user_dir + extra_scan_dirs; user plugins live
  in ~/.labui/plugins/, dev scan additionally covers project plugins/
- install_from_zip / uninstall / is_user_installed added to PluginManager
- vendor/ dir inside plugin zips: prepended to sys.path at load time so
  plugins can ship their own deps without requiring pip on end-user machine
- source_url field in manifest.json: shown as Download button in the
  missing-plugins dialog when a profile requires an absent plugin
- Frozen-app pip install now targets ~/.labui/plugin_packages/ using a
  real system Python (sys.executable is the exe in frozen builds)

Profile loading:
- Profile now stores plugins_manifest snapshot (id, name, version,
  source_url) alongside plugins_enabled
- On load, missing or dep-broken plugins trigger MissingPluginsDialog
  before the rest of the profile is applied; user can install from zip
  or download via source_url in-dialog, or cancel the load
- Plugin reconciliation only enables installed plugins — missing ones
  are not written to enabled.json

UI:
- Version label added to status bar (bottom-right, muted colour)
- Settings → Plugins tab: Install Plugin… button, per-plugin Remove
  button for user-installed plugins, live list refresh after install/remove

Docs:
- New docs/building.md covers the full release pipeline
- docs/plugin-development.md updated for new install flow, vendoring,
  source_url, profile behaviour, and distribution instructions

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

3 files changed, 10 insertions, 10 deletions

diff --git a/scripts/release/README.md b/scripts/release/README.md
index 6707ca1..54c9086 100644
--- a/scripts/release/README.md
+++ b/scripts/release/README.md
@@ -18,16 +18,16 @@ root/targets/snapshot/timestamp TUF roles) and `scripts/release/repository/`
 repo.** Losing the root key means you can never publish a trusted update to
 existing installs again — they'd all need a fresh, non-updating reinstall.
 
-Rebuild once more (`pyinstaller labdaq.spec`) after this step, so the
+Rebuild once more (`pyinstaller labui.spec`) after this step, so the
 freshly-generated `root.json` gets bundled into the app (see the `.spec`
 file's `_root_json` check — it only bundles the file if it already exists).
 
 ## Every release
 
 1. Bump `__version__` in `core/version.py`.
-2. `pyinstaller labdaq.spec` → produces `dist/LabDAQ/`.
+2. `pyinstaller labui.spec` → produces `dist/LabUI/`.
 3. `python scripts/release/repo_release.py` → creates+signs
-   `scripts/release/repository/targets/labdaq-<version>.tar.gz` and updates
+   `scripts/release/repository/targets/labui-<version>.tar.gz` and updates
    the metadata files in `scripts/release/repository/metadata/`.
 4. Create (first time) or reuse the GitHub Release tagged **`updates`** on
    this repo, and upload every file from `scripts/release/repository/metadata/`
diff --git a/scripts/release/repo_init.py b/scripts/release/repo_init.py
index 04c3579..ccbfe17 100644
--- a/scripts/release/repo_init.py
+++ b/scripts/release/repo_init.py
@@ -3,7 +3,7 @@ scripts/release/repo_init.py
 
 Run ONCE, ever, by the maintainer, locally. Generates the TUF signing keys
 and the initial repository metadata (including root.json, which later gets
-bundled into the app via labdaq.spec).
+bundled into the app via labui.spec).
 
 Running this again after the repo already exists is safe (tufup skips
 re-creating keys/roles that already exist) but there is normally no reason
@@ -24,7 +24,7 @@ from tufup.repo import Repository, RolesDict
 # directory, so invocation location must be consistent every time.
 os.chdir(Path(__file__).resolve().parent)
 
-APP_NAME = "labdaq"
+APP_NAME = "labui"
 
 # tufup-example's 1-day timestamp / 7-day snapshot defaults assume an
 # automated CI worker re-signs on a schedule. We're signing manually
diff --git a/scripts/release/repo_release.py b/scripts/release/repo_release.py
index a3c8d03..d50e458 100644
--- a/scripts/release/repo_release.py
+++ b/scripts/release/repo_release.py
@@ -1,14 +1,14 @@
 """
 scripts/release/repo_release.py
 
-Run after every `pyinstaller labdaq.spec` build, from anywhere (paths are
+Run after every `pyinstaller labui.spec` build, from anywhere (paths are
 made absolute below before the working directory changes). Packages the
-freshly built dist/LabDAQ bundle as a new signed tufup target.
+freshly built dist/LabUI bundle as a new signed tufup target.
 
 Prerequisites:
   - repo_init.py has been run once already (./repository and ./keystore exist)
   - core/version.py has been bumped to the new version
-  - dist/LabDAQ/ exists (pyinstaller labdaq.spec has just been run)
+  - dist/LabUI/ exists (pyinstaller labui.spec has just been run)
 
 After this completes, see README.md in this directory for how to publish
 the updated ./repository/metadata and ./repository/targets files to the
@@ -21,7 +21,7 @@ from pathlib import Path
 
 _THIS_DIR   = Path(__file__).resolve().parent
 _REPO_ROOT  = _THIS_DIR.parent.parent
-_DIST_DIR   = _REPO_ROOT / "dist" / "LabDAQ"
+_DIST_DIR   = _REPO_ROOT / "dist" / "LabUI"
 
 # Import core.version before changing cwd — needs the repo root on sys.path,
 # which won't be true anymore once we chdir into scripts/release below.
@@ -38,7 +38,7 @@ os.chdir(_THIS_DIR)
 def main():
     if not _DIST_DIR.is_dir():
         raise SystemExit(
-            f"{_DIST_DIR} not found — run `pyinstaller labdaq.spec` from the "
+            f"{_DIST_DIR} not found — run `pyinstaller labui.spec` from the "
             f"repo root first."
         )