Match each claim to the layer that was checked
This book contains implementation explanations, completed recorded checks, fictional expected outcomes, and browser-readable lesson state. The useful question is not whether something was tested in the abstract, but whether the named check reaches the effect being claimed.
Preserve the original proof boundaries
| Source | Recorded evidence retained here | Boundary that remains |
|---|---|---|
| Memory | Sanitized configuration inspection and source-grounded lifecycle and command explanations. | No memory-content audit, database-health check, or actual provider resolution was established. |
| Tan | Nine isolated runtime scenarios and a report of 136 passing focused tests. | Mock provider and recording UI; no physical keyboard proof, real task-quality result, or guaranteed restart rediscovery. |
| Extensions | 312 passing contract tests across 22 files, 1,039 assertions, strict checking of supplied example TypeScript, and 44 isolated example scenarios. | No live provider/OAuth, real elevated broker, full physical-terminal audit, or general cross-process coordination proof. |
| Continuity | 38 passing checks across Return Desk, Decision Desk, and Review Packet, plus a separate headless-browser report. | Read-only RPC startup, inert or synthetic seams where stated, intercepted sharing, and no physical TUI or real upload proof. |
These counts belong to different historical reports. They are not one newly executed unified suite. The original source and evidence chapters retain the narrower qualifications, including tests added during their own publication review.
A successful domain transition does not prove loader wiring. A loader scenario does not prove model tool choice. An RPC roundtrip does not prove a physical terminal’s key decoding. A controller test that intercepts an OS-open request does not prove a desktop viewer opened. The same discipline applies to a reader’s own observations.
The unified browser interface is a worked boundary, not an OMP connection
The reading-site contract names window.ompWorkbook, version 1, with tutorial-only scope. Its machine-readable contract and live discovery describe the loaded interface. They do not expose a session journal, provider, filesystem, or command runner.
| Operation | Reading use | Limit |
|---|---|---|
discover() | Obtain schemas, permissions, page/explorer scope, exact registered controls, and availability. | Do not infer a control from its visible label or from a pattern in another page. |
inspect() | Read the current document revision, page, explorer, checklist, clipboard, navigation, disclosures, and controls. | The result describes tutorial state only. |
query() | Search authored chapter titles and text across the book. | Results are excerpts, not proof that another chapter is visible or that OMP contains matching data. |
act() | Request a supported native click, disclosure state, or checkbox state using a fresh revision. | A navigation result is a request, not confirmed loading; a checked lesson is self-report. |
wait() | Observe a newer matching revision in the current document within a bounded deadline. | It cannot follow cross-document navigation or establish real work completion. |
diagnose() | Inspect tutorial runtime, storage, clipboard capability, and control integrity. | connectedToOMP is false and OMP health is not assessed. |
Query text is bounded to 240 characters, with a result limit from 1 to 10. The wait deadline is 0–5000 milliseconds, defaulting to 1500. Wait conditions can identify a page, story, or stage; a stage requires its owning story. Obtain actual IDs through discovery rather than inventing them.
Inspect immediately before an action and pass the opaque revision unchanged. Focus, scroll, viewport, disclosure, clipboard, and other native changes can invalidate it. On a stale revision, inspect and reassess. Hidden, disabled, detached, or closed-disclosure targets are not permission to bypass the interface by modifying the DOM.
After a native navigation request, inspect the destination document. New or restored documents issue their own revisions, and leaving the old document invalidates pending waits there. An unchanged idempotent action need not create a newer revision, so a timeout is not evidence that a requested transition happened.
Progress and copying remain local claims
Unified checklist reads, writes, and reset use only omp-workbook-checklist-v1. Storage can fail; a failed reset may leave an earlier record. Saved state is the last local observation, without multi-tab locking. Visiting a chapter or selecting an example milestone does not verify or automatically complete its exercise.
Clipboard confirmation requires the write promise to resolve before the contract’s 2500-millisecond deadline. Manual selection is not confirmed copying. Denial or timeout does not prove a late browser write is impossible, and copying never executes the snippet.
The Memory lab deliberately keeps its separate version-1 window.memoryTutorial interface and omp-memory-workbook:checklist:v1 storage. Its stage selection is fictional, not a successful retain or recall. If a page interface is unavailable, use the complete authored Markdown rather than inventing a network API.
Source trail: the supplied unified browser reading contract; the Memory lab HTML and browser-interface chapter; Extension verification levels; and each part’s complete evidence chapter. This editorial assembly adds no new browser, OMP, provider, or filesystem execution result.
Related chapters:
Connections and next steps · Unified editorial chapter; connects the recorded source material without rerunning it.