Say what the Tauri build actually produced, because it produced something

Two docs understated deploy method 5. README-SECTION-3 headed the section "built
+ contract-proven; no binary emitted", and develop-a-plugin closed its table
with "2, 4 and 5 are scaffolded but no binary/install has been shot".

Measured: `cargo tauri build` has run and its outputs are on disk.
deployment/src-tauri/target/release/doxa-maps-desktop is a 67,379,880-byte ELF
64-bit LSB pie executable, and target/release/bundle/deb/ holds a 60,554,898-byte
.deb. Eight source files are git-tracked under deployment/src-tauri/, and
check:tauri exits 0.

So "no binary emitted" is false. What is true is narrower and worth stating
precisely: no window has been opened, because this build box is headless with no
Xvfb, so nothing has confirmed the app paints rather than launching to a blank
frame — the exact soft failure the section below already warns about. "Not shot"
means nobody has watched it run; it does not mean nothing was produced. The
closing sentence now separates the three built-not-shot methods, because what is
missing differs for each: no APK for mobile, no captured install for WordPress,
and for Tauri artifacts that exist but have never been launched.

The bodies of both sections were already accurate and are untouched. Only the
status labels were wrong, which is the part a reader skims.

Found while reconciling the ideation sources. The 5-cap spec
(01-ideation-research/coolest-ideation/5-cap-5-deploy.md, 2026-09-22) is CURRENT
and correct on all five rows — verified each: 43 embed.iframe entries in the
manifest, 19 SRI hashes, capacitor.config.json with check:mobile green, the
WordPress PHP with check:wp-embed green, and the Tauri artifacts above.

The /plugin-designer skill is now the stale one, and the direction of the error
has reversed. It says method 5 is "ASPIRATIONAL — not scaffolded. No Tauri
config/dir exists in the repo", and instructs the reader not to repeat the
spec's claim. That catch was CORRECT when written: the spec then said "proven
POC", which was unbacked. The spec has since self-corrected, carrying a dated
2026-09-22 block reading "BUILT, not shot ... only the window LAUNCH is
unverified", which matches the files. The skill's correction froze at the old
reading and over-swung from overclaimed to nonexistent.

That is a hazard worth naming: a correction record — "document X is wrong about
Y" — becomes wrong itself the moment X is fixed, and nothing re-reads it.
Correction notes need the same staleness discipline as the claims they correct.
The skill lives in the session config directory with no git repo, so the fix is
surfaced on BUILD-PLUGIN-DESIGNER-SKILL-MEANS-REAL-WORK as a single precise edit
rather than made here.

Seven gates pass, including check:tauri, check:capability-citations,
check:capability-exemplars, check:doc-scripts and check:quoted-scripts.

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

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://<platform>/plugin-assets/doxa-maps/<plugin>/<plugin>/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://<platform>/plugin-assets/doxa-maps/<plugin>/<plugin>/index.html`.
 **Done = the live site shows it, not a green build.**
 
 ## Step 6 — Surface it (make it discoverable)