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 lab helper provides that preparation. It does not launch OMP or import its SDK.

Milestone: Copy fiction into an owned lab

Need. Maya wants to practice the real command surfaces.

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

First discover the helper’s supported operations, then create a lab.

Terminal shell — fixture preparation, from extracted examples/:

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 ok: false. Read it before continuing.

Each successful create makes a new temporary root containing:

• Dedicated home, agent/config, temporary, and XDG directories.
• A project containing the fictional today.txt.
• Yesterday’s copied journal, 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:

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 must identify the intended installed executable. Stop if it is empty. If your shell reports an alias or function rather than an absolute executable path, 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; this jq composition supplies the documented inspection request:

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

Inspection validates the lab marker and canonical root. It does not inspect a running OMP process.

Understand the generated environment

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

The lab settings disable memory, autolearn, advisors, skills, secrets, marketplace auto-update, and automatic resume.

Use the whole printed command. Do not shorten it to a bare omp --resume ….

This is data separation, not an operating-system sandbox. In particular:

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

What changes? The helper creates new fictional files under one owned temporary root.

What does not change? It does not open or rewrite ordinary session history, launch OMP, or submit a model request.

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

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

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

Self-check. Does a successful create receipt prove that OMP resumed yesterday?

Answer: No. It proves fixture preparation succeeded. Native execution and identity inspection are separate observations.