docs(perception): record Rerun projection acceptance

docs/09_OBSERVATION_SESSIONS.md

@@ -4,10 +4,11 @@ Status: implemented for native K1 point/pose evidence and host-side camera
 archival. Valid K1 `ModelingReport` scan time, distance and speed are also
 materialized as recorded Rerun time series. Recorded spatial playback is exposed
 in the Mission Core observation workspace. The camera archive/player contract
-is implemented and covered by tests, but all retained real K1 sessions predate
-canonical camera archival. Physical shared-timeline playback of one selected
-camera plus point cloud therefore remains an open acceptance gate; historical
-sessions contain no recoverable video.
+is implemented and covered by tests. TEST007 physically accepted shared-timeline
+playback of the saved cameras and point cloud. It also carries the first optional
+external-perception result projected into the same Rerun recording; older
+sessions without canonical camera evidence or an admitted compute result remain
+fully usable with only their available modalities.
 
 ## Operator path
 
@@ -19,8 +20,8 @@ sessions contain no recoverable video.
 3. Stop acquisition normally, or allow the local service to recover an
    unexpected interruption on its next start. Session recording is automatic;
    the disk action is not required.
-4. Open **Сохранённые сессии** in the observation header. The menu shows the
-   three most recent indexed runs, their date, duration, state, modalities and
+4. Open **Сохранённые сессии** in the observation header. The menu shows up to
+   100 indexed runs, their date, duration, state, modalities and
    background preparation state.
 5. Choose a replayable run. Opening a replay never performs conversion in the
    request. A ready recording opens immediately; otherwise the client receives
@@ -35,7 +36,11 @@ sessions contain no recoverable video.
 7. Use **Воспроизвести / Пауза**, the scrubber, **К началу** and **К концу** on
    the right half of the bottom timeline. The left half changes point-cloud
    accumulation. The recorded timeline is zero-based `session_time`.
-8. Use the first disk button to save the current workspace layout. The next
+8. If a validated derived camera result exists, **Распознавание** appears in the
+   scene toolbar. It switches the active native Rerun view to camera frames and
+   boxes; **Облако точек** returns to the 3D view. No button is shown for an
+   absent or rejected result, and the base recording remains usable.
+9. Use the first disk button to save the current workspace layout. The next
    opening restores display settings and dynamic sensor-source window
    positions. The transient **Движок / Слои / Отображение** tool windows are
    scoped to the mounted spatial workspace and are never persisted. This action
@@ -137,11 +142,13 @@ checkout:
 │           │       ├── mqtt.timeline.session-<sha256>.json # sealed generation
 │           │       └── mqtt.summary.json # atomic active-envelope pointer
 │           └── media/                  # canonical camera archives
-└── recordings/
+├── recordings/
     ├── .export.lock                     # cross-process conversion/eviction lock
     └── <opaque-session-id>/
         ├── scene.rrd
         └── scene.rrd.cache.json
+└── perception-overlays/
+    └── <opaque-session-id>/<result-id>/<recording-id>.rrd
 ```
 
 `MISSIONCORE_DATA_DIR` relocates the catalog and derived cache. Unless it is
@@ -177,6 +184,9 @@ camera epoch there by preserving its valid segment prefix and writing an
 
 Never add `.runtime/`, `sessions/`, raw captures, RRD files or camera media to
 Git. They can contain mapped interiors, trajectories and identifiable images.
+The recorded perception importer reads repo-local ignored
+`.runtime/compute-jobs` and `.runtime/compute-results`; those derived handoff
+artifacts are likewise private and never become browser paths or Git inputs.
 
 ## Session source of record