Debian trixie-based build-compile-deploy workflow

README.md

@@ -24,14 +24,15 @@ smart-serow/
 │   └── ui/               # Flutter app (elinux target)
 │       ├── lib/main.dart
 │       ├── pubspec.yaml
-│       └── elinux/       # Platform-specific build config
+│       └── elinux/       # Generated by flutter-elinux (gitignored)
 ├── scripts/
 │   ├── build.sh          # Cross-compile for ARM64
 │   ├── deploy.sh         # Push to Pi via rsync
 │   ├── deploy_target.json
 │   ├── pi_setup.sh       # One-time Pi setup
 │   └── smartserow-ui.service
-└── pi_sysroot/           # Pi libraries for cross-linking (gitignored)
+├── pi_sysroot/           # Pi libraries for cross-linking (gitignored)
+└── LICENSE               # MIT
 ```
 
 ---
@@ -145,11 +146,10 @@ Flutter-elinux supports multiple backends. We use **GBM** (DRM/KMS direct).
 | `x11` | Debug | Needs X server, mouse/keyboard friendly |
 | `wayland` | - | Requires compositor, more dependencies |
 
-The service runs with `-b drm`. For X11 debugging on Pi:
-```bash
-startx &
-./smartserow_ui -b x11
-```
+The backend is compiled in (we build with `--target-backend-type=gbm`).
+The `-b` flag is for bundle path, not backend selection.
+
+For X11 debugging, you'd need to rebuild with `--target-backend-type=x11`.
 
 ---