## Return Desk lab setup

The raw fixture is suitable for reading\. Native resume practice needs something more\: an existing project directory and an owned session collection\, without mixing the exercise into ordinary history\.

The supplied&#32;[lab helper](<https://present-sketch-tp94.here.now/examples/return-desk/lab.ts>)&#32;provides that preparation\.&#32;It does not launch OMP or import its SDK\.

### Milestone\:&#32;Copy fiction into an owned lab

**Need\.**&#32;Maya wants to practice the real command surfaces\.

**Obstacle\.**&#32;Placing a fixture in a normal session store would mix exercise data with personal history\.&#32;Opening the unre\-based fictional path would also confuse recorded cwd with a real project\.

First discover the helper’s supported operations\,&#32;then create a lab\.

**Terminal shell — fixture preparation\,&#32;from extracted&#32;`examples/`\:**

~~~sh
bun return-desk/lab.ts '{"version":1,"op":"discover"}'
RECEIPT=$(mktemp -t continuity-return-receipt)
bun return-desk/lab.ts '{"version":1,"op":"act","action":"create"}' | tee "$RECEIPT"
~~~

Stop if the receipt reports&#32;`ok: false`\.&#32;Read it before continuing\.

Each successful create makes a new temporary root containing\:

- Dedicated home\,&#32;agent\/config\,&#32;temporary\,&#32;and XDG directories\.
- A project containing the fictional&#32;`today.txt`\.
- Yesterday’s copied journal\,&#32;with its cwd rebased to that project\.
- A newer unrelated fictional note\.
- A lab marker and receipt\.
- Complete native commands with the correct paths\.

Keep the following variables in this same terminal\:

**Terminal shell — receipt values and executable selection\:**

~~~sh
LAB=$(jq -r '.root' "$RECEIPT")
SOURCE=$(jq -r '.yesterday' "$RECEIPT")
SESSIONS=$(jq -r '.sessions' "$RECEIPT")
PROJECT=$(jq -r '.cwd' "$RECEIPT")
OMP_BIN=$(command -v omp)
~~~

`OMP_BIN`&#32;must identify the intended installed executable\.&#32;Stop if it is empty\.&#32;If your shell reports an alias or function rather than an absolute executable path\,&#32;resolve that before using the generated commands\.

You can re\-inspect the existing lab through the helper’s supplied version\-1 inspection operation\:

**Terminal shell — read\-only lab inspection\;&#32;this&#32;`jq`&#32;composition supplies the documented inspection request\:**

~~~sh
bun return-desk/lab.ts "$(jq -c '{version:1,op:"inspect",root:.root}' "$RECEIPT")"
~~~

Inspection validates the lab marker and canonical root\.&#32;It does not inspect a running OMP process\.

### Understand the generated environment

The native commands begin with&#32;`env -i`\,&#32;retain&#32;`PATH`\,&#32;and supply dedicated home\/config\/session paths\.&#32;They also include explicit&#32;`--cwd`&#32;and&#32;`--session-dir`&#32;values and flags disabling extensions\,&#32;skills\,&#32;rules\,&#32;LSP\,&#32;tools\,&#32;and title generation for the recipe\.

The lab settings disable memory\,&#32;autolearn\,&#32;advisors\,&#32;skills\,&#32;secrets\,&#32;marketplace auto\-update\,&#32;and automatic resume\.

**Use the whole printed command\.&#32;Do not shorten it to a bare&#32;`omp --resume …`\.**

This is data separation\,&#32;not an operating\-system sandbox\.&#32;In particular\:

- Native OMP startup may discover providers or refresh metadata without a model prompt\.
- The helper’s synthetic&#32;`TMUX_PANE`&#32;is only a terminal\-identity fallback\.
- OMP prefers stdin’s actual TTY identity when available\.
- Resume and continue practice must use the&#32;**same actual terminal tab**&#32;and generated environment\.

**What changes\?**&#32;The helper creates new fictional files under one owned temporary root\.

**What does not change\?**&#32;It does not open or rewrite ordinary session history\,&#32;launch OMP\,&#32;or submit a model request\.

**Recorded checks\.**&#32;The public helper’s discover\,&#32;create\,&#32;and inspect operations completed successfully inside the isolated proof\.&#32;A separate source\-CLI check used the generated lab for resume\,&#32;continue\,&#32;and fork with read\-only RPC inspection\.

That CLI check added private disabled\-provider policy and a guarded transport\.&#32;It was not physical TUI interaction and does not make ordinary native startup network\-free\.

**Failure and recovery\.**&#32;If native startup requires setup or authentication\,&#32;stop\.&#32;Do not log in\,&#32;paste a key\,&#32;copy an auth database\,&#32;or send a prompt\.&#32;You can still inspect the fictional files and study the recorded results\;&#32;record native interaction as blocked\,&#32;not passed\.

**Self\-check\.**&#32;Does a successful create receipt prove that OMP resumed yesterday\?

**Answer\:**&#32;No\.&#32;It proves fixture preparation succeeded\.&#32;Native execution and identity inspection are separate observations\.