dsh UI improvement

README.md

@@ -29,6 +29,45 @@ $env:PYTHONPATH = "D:\repo\orisys-app\shared\src;D:\repo\orisys-app\apps\custome
 python D:\repo\orisys-app\apps\customer\run.py
 ```
 
+### Local `orisys` SDK
+
+`orisys_app_shared.force` imports `orisys.calibration` at module scope, so the
+customer app cannot start against an SDK build that predates that module
+(the published 0.5.1 wheel does not include it). When working from a repo
+checkout, install the SDK from source instead of from an index:
+
+```powershell
+python -m pip install .\..\orisys-sdk          # same checkout that built this app
+```
+
+If a pip build is blocked by the environment, the equivalent manual install is
+to copy `orisys-sdk/src/orisys/**/*.py` over `site-packages/orisys/` and delete
+the stale `__init__.cp310-win_amd64.pyd` (an extension module shadows the
+package `__init__.py`, which hides sibling modules such as `calibration.py`).
+
+### Verifying UI changes
+
+Both tools render the real main window with the offscreen Qt platform — no
+display, camera or sensor hardware required:
+
+```powershell
+python .\apps\customer\tools\ui_check.py                      # layout/theme assertions
+python .\apps\customer\tools\ui_snapshot.py --theme light --demo `
+    --sensor finger --panels cal,3d --size 1600x900 --out shot.png
+```
+
+`ui_check.py` needs only the runtime dependencies. The `pytest` suite in
+`shared/tests` and `apps/customer/tests` covers the same ground plus locale and
+preference-schema parity:
+
+```powershell
+pip install pytest
+python -m pytest
+```
+
+On Windows the offscreen platform finds no fonts unless `QT_QPA_FONTDIR` points
+at `C:\Windows\Fonts`; both tools set it automatically.
+
 ## Branding
 
 Window / EXE icon: `shared/resources/branding/logo.png`