Tauri 2 shell: verified Linux build and native window

README.md

@@ -6,6 +6,8 @@ This repository is **P1a**: the engine, the wire, the descent, and the material
 
 ![The quarry](preview-p1-quarry.png)
 
+![The Tauri window](preview-tauri.png)
+
 ## What is real
 
 - **Rust engine.** `cpal` output at 48 kHz, five veins, a sixteen-step phrase, a fixed voice pool, per-vein levels and gains, a bar clock. Procedural voices for empty pattern rows; real sample voices for rows with a face. No Web Audio.
@@ -16,7 +18,7 @@ This repository is **P1a**: the engine, the wire, the descent, and the material
 - **Surface.** A Svelte 5 descent whose terrain, eye, city, road, stones and playhead react to the five levels and the master; a real wire log; engine facts; cilia; a master signal trace; vein gains; transport; keyboard.
 - **Verification.** Rust unit tests, a live wire test, a material import test, a browser quarry test and the P0 regression smoke, plus `svelte-check` and a production build.
 
-The Tauri 2 shell is scaffolded in [`app`](app), but **it has not been built on this machine**: the system is missing the GTK/WebKit/dbus development packages and `sudo` requires a password. The exact blocker and the install command are in [`docs/P0.md`](docs/P0.md). The browser surface is the working path.
+The Tauri 2 shell is **built and running**: a native window loading the same surface, connected to the daemon. It is built with Tauri 2.12.5 / CLI 2.12.4 against WebKitGTK 2.54.2, GTK 3.24.52 and dbus 1.16.2. The binary is `app/src-tauri/target/release/zhila-app` (13 MB); installers are a later step.
 
 ## Quick start
 
@@ -43,6 +45,17 @@ npm --prefix ui run dev
 4. `space` plays the loop; the bass row now triggers the sample while the other veins keep their procedural voices. Edit steps in the pattern; each edit goes to the engine and the journal.
 5. Go back to **nave** to see the pattern on the road and the levels in the room.
 
+### Tauri
+
+```bash
+npm --prefix ui run build
+cd app
+./node_modules/.bin/tauri build --no-bundle
+./src-tauri/target/release/zhila-app
+```
+
+The built window embeds the surface and connects to the daemon at `ws://127.0.0.1:4317`; start the daemon first. `tauri dev` uses the Vite server at `127.0.0.1:5173`. The engine is still the separate daemon in this phase.
+
 Controls: `space` play/stop · `s` strike the selected face in the quarry or the selected vein in the nave · `1`–`5` select a vein (nave) or a pattern row (quarry) · click a face to select, double-click to strike · tempo `−` / `+`.
 
 The daemon prints the audio device, rate, buffer and session id. Use `--no-audio` for UI/protocol tests, `--port` to change the port, and `ZHILA_TOKEN` or `--token` to change the dev token. The surface reads `VITE_ZHILA_WS` and `VITE_ZHILA_TOKEN` at build time.
@@ -57,7 +70,7 @@ crates/zhila-material   decode, onset analysis, sixteen faces, peaks
 crates/zhila-daemon     WebSocket daemon, auth, binary import
 ui                      Svelte 5 surface: descent + quarry
 fixtures                a small click track for the smoke tests
-app                     Tauri 2 shell (scaffolded; system deps missing)
+app                     Tauri 2 shell (built; engine remains the daemon)
 docs                    plan, protocol, P0/P1 notes
 reference/demo          the earlier design demo
 ```
@@ -82,6 +95,6 @@ npm --prefix ui run quarry-smoke      # daemon + Vite: import, assign, play, scr
 - One fixed two-bar phrase and five veins; pattern rows are veins, one face per row, no per-step face or pitch.
 - Formats depend on symphonia; WAV is the tested path. AIFF, multi-channel files and very long files are not specifically handled.
 - No agent/MCP in this phase.
-- The Tauri shell is not verified; see the blocker.
+- The Tauri shell now builds and runs; the engine is still the separate daemon (embedding is next).
 
 The next slice is P1b: a project file and SQLite journal, an asset archive, autosave and reload, undo for pattern edits, recording, and waveform trimming. Then the arrangement and the agent. The plan is in [`docs/PLAN.md`](docs/PLAN.md); the P1a notes are in [`docs/P1.md`](docs/P1.md).