diff --git a/documentation/README-SECTION-3-cli-commands.md b/documentation/README-SECTION-3-cli-commands.md index 8c8052b7e..eed1d03e1 100644 --- a/documentation/README-SECTION-3-cli-commands.md +++ b/documentation/README-SECTION-3-cli-commands.md @@ -201,7 +201,7 @@ the correct markup, repeatably and in CI. What is *not*: that WordPress renders that the block editor registers it, or that a browser executes the result. Those still need a real WP install (`wp-env start` — see `deployment/wordpress/doxa-maps-embed/HOW-TO-TEST.md`). -### 5. Desktop — Tauri *(built + contract-proven; no binary emitted)* +### 5. Desktop — Tauri *(built, not shot — a binary and a `.deb` ARE emitted; only the GUI launch is unverified)* **Install:** Bun ALONE for the contract check. For the binary: the Rust toolchain (`rustup`), the Tauri CLI (`cargo install tauri-cli`), and the platform's system webview libs. @@ -211,6 +211,13 @@ bun run check:tauri # CONTRACT check — needs NO Rust, NO Tauri CLI cargo tauri build # the binary — needs the toolchain above ``` +**What "built, not shot" means here, measured rather than asserted.** `cargo tauri build` has been run +and its outputs are on disk: `deployment/src-tauri/target/release/doxa-maps-desktop` is a 67 MB ELF +64-bit executable, and `target/release/bundle/deb/` holds a 60 MB `.deb`. Eight source files are +git-tracked under `deployment/src-tauri/`. What has *not* happened is a window opening: this build box +is headless with no Xvfb, so nothing has confirmed the app paints rather than launching to a blank +frame. Say "built, not shot" — not "proven", and not "aspirational". + `deployment/src-tauri/tauri.conf.json` + the `deployment/src-tauri/` Rust crate wrap the **same `public/` tree** Capacitor and the CDN serve — `build.frontendDist` is `../public`, the desktop counterpart of Capacitor's `webDir`. One `bun run build` now feeds four consumers: CDN, Capacitor, local diff --git a/documentation/develop-a-plugin-and-see-it-live.md b/documentation/develop-a-plugin-and-see-it-live.md index 8d5ffe25f..f672b7e28 100644 --- a/documentation/develop-a-plugin-and-see-it-live.md +++ b/documentation/develop-a-plugin-and-see-it-live.md @@ -176,7 +176,12 @@ Your one element deploys five ways (only an element supports all five — a page | 4 | **WordPress plugin** | the `deployment/wordpress/doxa-maps-embed/` PHP wrapper emits the embed snippet | 🔶 built, not shot | | 5 | **desktop (Tauri)** | `bun run tauri:build` → a real binary + `.deb` wrapping the same `public/` tree | 🔶 built, not shot | -Say "proven" ONLY for 1 & 3 (2, 4 and 5 are scaffolded but no binary/install has been shot). Verify at `https:///plugin-assets/doxa-maps///index.html`. +Say "proven" ONLY for 1 & 3. For 2, 4 and 5 say "built, not shot" — each is scaffolded and +contract-checked, and what is missing differs per method: 2 has no APK (no Android SDK here), 4 has +no capture of a live WordPress install, and 5 **does** emit artifacts — a 67 MB binary and a 60 MB +`.deb` are on disk — but no window has been opened, because this box is headless. "Not shot" means +nobody has watched it run, which is not the same as "nothing was produced". Verify at +`https:///plugin-assets/doxa-maps///index.html`. **Done = the live site shows it, not a green build.** ## Step 6 — Surface it (make it discoverable)