docs: align application demo semantics

docs/desktop/install.md

@@ -120,11 +120,14 @@ only after the run reaches a safe paused or terminal state. The overlay reports
 runtime state; OpenAdapt never uses it as resolution or verification evidence.
 
 For published footage, OpenAdapt post-composes the status surface onto a
-derivative as **Guided view**; **Raw footage** remains unchanged. Exact target
-tracking appears only on a replay frame that carries a runtime-bound target
-rectangle. This presentation choice does not weaken the pointer, focus, or
-capture-exclusion boundary. [Watch the public demo](https://app.openadapt.ai/demo#footage)
-or review the exact released
+derivative as **Guided view**; **Raw footage** shows the immutable media. Guided
+target tracking appears only when the media digest, exact decoded frame,
+viewport mapping, and runtime-bound rectangle agree. The compact status capsule
+uses a bottom corner that does not cover the target or another protected region,
+and disappears if neither corner is safe. These presentation elements are not
+verification evidence and do not weaken the pointer, focus, or capture-exclusion
+boundary. [Watch the public demo](https://app.openadapt.ai/demo#footage) or
+review the exact released
 [control-overlay contract](https://github.com/OpenAdaptAI/openadapt-desktop/blob/desktop-v0.13.1/docs/CONTROL_OVERLAY.md).
 
 ## Where to go next

docs/get-started/what-works-today.md

@@ -32,11 +32,14 @@ deployment boundary.
 The [interactive status viewer](https://openadapt.ai/artifacts/json?source=%2Fstatus.json)
 presents the same release, availability, evidence, and deployment dimensions;
 the [raw JSON](https://openadapt.ai/status.json) remains available for tools.
-For a visual tour, the [public Cloud demo](https://app.openadapt.ai/demo#footage)
-shows recorded demonstrations, compiled replays, exact-frame guided overlays,
-VERIFIED outcomes, and fail-safe HALTED cases. Its evidence links open the
-corresponding manifests in the first-party JSON viewer instead of presenting
-media as proof by itself.
+For a visual tour, the [OpenAdapt website](https://openadapt.ai/how-it-works) and
+[public Cloud demo](https://app.openadapt.ai/demo#footage) share the same real
+application choices and presentation vocabulary: **Recorded demonstration**,
+outcome-bound **Verified replay**, exact retained **Fail-safe halt** footage
+where available, and **Guided view** versus immutable **Raw footage**. Guided
+targets are bound to an exact decoded frame rather than inferred by the viewer.
+Cloud then adds the openIMIS graph, contracts, six Standard-profile results, and
+byte-inventoried evidence links; media is never presented as proof by itself.
 The public managed runner executes approved browser workflows. Native desktop,
 RDP, and Citrix/VDI workflows execute locally or in a self-hosted or
 customer-controlled runtime connected to the same governance model.

docs/index.md

@@ -150,17 +150,32 @@ execution boundary.
 
 ## Measured, not claimed
 
-The [public Cloud demo](https://app.openadapt.ai/demo#footage) keeps the same
-visual contract used on the OpenAdapt website: switch between the **Recorded
-demonstration** and **Compiled replay**, then choose **Guided view** or **Raw
-footage**. Guided view adds the runtime presentation layer to a derivative;
-raw evidence media remains unchanged. A target outline appears only when the
-runtime bound that rectangle to the exact decoded replay frame. **VERIFIED**
-means the complete declared contract passed; **HALTED** means the run stopped
-rather than claim an outcome it could not prove.
-
-[Watch the real-application demo](https://app.openadapt.ai/demo#footage){ .md-button .md-button--primary }
-[Inspect the exact OpenEMR evidence](https://openadapt.ai/artifacts/json?source=%2Freference%2Fopenemr-patient-registration-standard-synthetic-v1%2Fmanifest.json){ .md-button }
+The [OpenAdapt website](https://openadapt.ai/how-it-works) and
+[public Cloud demo](https://app.openadapt.ai/demo#footage) share one viewer
+contract for real OpenEMR, Frappe Lending, and openIMIS footage:
+
+- **Recorded demonstration** is source capture and carries no execution outcome.
+- **Verified replay** appears only for exact replay media bound to a complete
+  passing outcome contract.
+- **Fail-safe halt** appears only when exact retained halt media exists. The
+  current openIMIS reference includes it; the viewer never invents a halt mode
+  for another application.
+
+**Guided view** adds the presentation layer to a derivative; **Raw footage**
+shows the immutable media. Guided target tracking appears only when the media
+digest, exact decoded frame, viewport mapping, and runtime target binding all
+agree. The status capsule uses a bottom corner that does not cover the target
+or another protected region, and disappears if neither corner is safe. Neither
+the target outline nor the capsule is verification evidence.
+
+Cloud uses the same application, mode, and view choices, then adds an openIMIS
+deep dive with the compiled graph, contracts, six retained Standard-profile
+results, and byte-inventoried evidence links. **VERIFIED** means the complete
+declared contract passed; **HALTED** means the run stopped rather than claim an
+outcome it could not prove.
+
+[Watch the shared real-application demo](https://openadapt.ai/how-it-works){ .md-button .md-button--primary }
+[Inspect the Cloud evidence deep dive](https://app.openadapt.ai/demo#footage){ .md-button }
 
 We publish the numbers and the failure modes. These two results run **both
 arms**, compiled replay against a computer-use agent, under the same