Runtime Observation Workbench¶

This lab is a bounded consumer proof for runtime observations, owner-qualified commands, and embedded terminal presentation. It is not a general browser terminal and it does not admit Ratatui as a permanent Tokimu provider.

What This Proves¶

browser semantic control or terminal input
                    ↓
one Rust/WASM observation-shell session
                    ↓
Tokimu runtime scenario and command routing
                    ↓
semantic control result + Ratatui terminal projection
                    ↓
Tokimu rasterization to RGBA
                    ↓
browser canvas blit

The semantic toolbar and the terminal are two projections of the same retained Rust/WASM WasmObservationShellSession. Selecting a presentation target or advancing playback through the toolbar changes the same runtime state that the Ratatui terminal renders. Terminal commands use that same session as well.

TypeScript owns browser focus, normalized event forwarding, resize observation, and whole-frame canvas blitting. It does not parse commands, keep another runtime, position terminal glyphs, or interpret Ratatui styles.

Runtime observation / shared-session evidence / on demand

Inspect one retained runtime session

Open a bounded runtime scenario. Use the semantic controls, then focus the terminal canvas and enter HELP, STATUS, or CLEAR. Both surfaces observe the same Rust/WASM session.

This is consumer evidence only. It does not claim native/browser session handoff, full terminal emulation, or permanent Ratatui admission.

Idle No runtime observation session loaded

Boundary¶

Rust/WASM owns the runtime fixture, observations, command catalog, command validation, prompt, transcript, history, and Ratatui composition.
Ratatui owns terminal layout and style composition inside its bounded region.
Tokimu owns the retained terminal surface and font rasterization.
The browser owns only the containing island, canvas focus, input forwarding, resize notifications, and RGBA frame presentation.

The iframe document loading is not runtime-readiness evidence. The child reports loading, ready, or error only after Rust/WASM initialization. Startup failures remain visible inside the consumer and propagate to the containing island instead of leaving a blank terminal beneath a false ready state.

AR-0013 remains incubating. The still-open questions are shared live sessions across standalone/native and embedded hosts, host-level viewport parity, and permanent provider admission.