# Real Pi cold-resume comparison

Environment on both sides: Linux, T3 web dev client in Chromium, 1280×800 CSS viewport (2560×1600 capture), light appearance, Pi 1.5.2, anthropic/claude-haiku-5-5. Separate synthetic projects and checkout-local T3 databases; no production data.

The scenario runner was deliberately not used: replay ACP cannot exercise Pi's extension/session lifecycle.

## Seed and instruments

seed.py is a portable form of the setup used. Run it with a checkout and a NEW run directory. Start that checkout's dev server with the printed environment, then seed the initial turn with --seed-thread. The initial turn uses the real T3 CLI/RPC; the two continuations use the web composer. The explicit extension is trusted by --approve. The transparent pi-probe launcher forwards the real Pi RPC byte stream unchanged and records only command types, response success flags, and launch arguments. probe.ts records factory/session_start events and publishes its per-process factory count through Pi's actual status UI.

Discovery spawns with --no-session are present in the full protocol logs. They are not thread sessions and are excluded from the summary counts. Public logs replace local paths with $PROOF, $BASE_CHECKOUT, and $HEAD_CHECKOUT. Public recordings redact the environment-name strip above the probe status; the status and composer are unmasked. The unrelated failed thread visible in the sidebar is a setup attempt with a model no longer routed by the provider; it is not the evidence thread.

## Matching browser steps

1. Pair with the dev server, then navigate directly to /<environmentId>/<URL-encoded-threadId> for the seed's returned thread. Close thread details so no machine details appear.
2. Start the recording with the completed initial turn and probe count 1 visible.
3. Stop the retained dev terminal using Ctrl+C and restart `vp run dev` with the SAME PI_PROOF_LOG, T3CODE_DEV_SEED=0, checkout and .t3. Keep the same browser thread open through reconnect.
4. In `[contenteditable="true"]`, type `What codeword did I ask you to remember? Reply only with that word.` Click `button[aria-label="Submit message"]`. Wait for the turn to finish. Read the probe status and the RPC log.
5. Repeat the full server stop/restart. Type `Again, what is the codeword? Reply only with that word.` and submit. Wait for completion.
6. Blur the composer. Take two screenshots at least 500 ms apart and verify identical pixels; retain one. Stop recording.

## Observed

Base c0561c5c3d75f5fa2017d4ba9d75124ad63fe897: each of two resumes starts without --session, sends switch_session once, initializes the probe factory twice, and first announces a throwaway session before the saved session. UI says `Resume probe: factory loads 2`.

Head 87101fd43d321e5f0afb56105b4de56a55e37626: each of two resumes starts with --session <saved file>, sends no switch_session, and initializes the probe factory once. UI says `Resume probe: factory loads 1`.

Both sides answer ORCHID on both continuations. This proves redundant session replacement/extension reloading, not the historical intermittent stale-context error. Genuine different-file session switching and missing-file fresh-session recovery were not exercised.
