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>

1 files changed, 3 insertions, 3 deletions

diff --git a/CLAUDE.md b/CLAUDE.md
index 0fa549d..b95d079 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -46,7 +46,7 @@ Control widgets (left panel) go other direction: UI → `ControlWidget._write()`
 
 **Backend switching at runtime** — `AnalogInputDevice` and `DigitalIODevice` both have `switch_backend(backend, simulate, ...)` — disconnects, reconfigures, reconnects without restart. Called from "Apply & Reconnect" in config dialog.
 
-**Profile persistence** — `core/profile.py` serialises full operator state (controls, plot layout, signal pipelines, derived channels) to `.labdaq` JSON files. `ProfileManager` handles save/load.
+**Profile persistence** — `core/profile.py` serialises full operator state (controls, plot layout, signal pipelines, derived channels) to `.labui` JSON files. `ProfileManager` handles save/load.
 
 ### Directory map
 
@@ -61,7 +61,7 @@ Control widgets (left panel) go other direction: UI → `ControlWidget._write()`
 | `devices/serial_device.py` | Generic UART device |
 | `core/acquisition.py` | `AcquisitionEngine` + `ChannelBuffer` |
 | `core/signal_processor.py` | Filter chain + derived/virtual channels |
-| `core/profile.py` | `.labdaq` profile save/load |
+| `core/profile.py` | `.labui` profile save/load |
 | `ui/main_window.py` | Top-level window, toolbar, demo device init, plugin lifecycle |
 | `ui/control_panel.py` | Left panel output widgets (`OnOffSwitch`, `MotorControl`, etc.) |
 | `ui/strip_chart.py` | Live pyqtgraph chart, config-driven by `LayoutConfig` |
@@ -110,7 +110,7 @@ Optional hooks a plugin can implement:
 - `get_filter_classes() → dict` — added to `SignalProcessor` filter registry
 - `get_toolbar_actions() → list[PluginAction]` — buttons inserted in main toolbar
 - `get_settings_widget() → QWidget` — shown in Settings → Plugins panel
-- `get_save_state() / apply_save_state(dict)` — persisted in `.labdaq` profiles
+- `get_save_state() / apply_save_state(dict)` — persisted in `.labui` profiles
 
 **Extending Add Device dialog from a plugin**: `ui/add_device_dialog._PANELS` is a module-level dict `{type_name: (PanelClass, id_prefix)}`. Plugins add/remove entries in `on_load`/`on_unload`. Each panel class needs a `build_device(device_id) → BaseDevice` method.