# Issue 24790 runtime reproduction (2026-10-25, worktree at b76a110aa4)

Synthetic fixture only: T3_REPRO_SECRET=t3repro-synthetic-6f1c2a9e, set in the isolated
settings.json as a Codex provider-instance environment variable (sensitive: true).
The prompt runs only `printenv T3_REPRO_SECRET`, never the full environment.

1. Isolated server: `node apps/server/src/bin.ts start --bootstrap-fd 3 --base-dir <scratch>/home`
   (bootstrap `t3Home` alone did NOT isolate; without --base-dir the server targeted ~/.t3/userdata
   and refused only because the live server holds ownership).
2. Session: `node apps/server/src/bin.ts auth session issue --base-dir <scratch>/home --ttl 30m --token-only`
3. Driver: `TOK=... PORT=36971 PROJ=<fresh git dir> node repro.ts gpt-5.6-sol`
   (project.create -> websocket ticket -> orchestration.launchThread on instance `codex`).
4. Result: run completed; Codex ran `/bin/bash -lc 'printenv T3_REPRO_SECRET'`.
   orchestration.getThreadProjection omits command output (0 hits), but statev2.sqlite holds it:
     orchestration_events seq 93 turn-item.updated .output = 't3repro-synthetic-6f1c2a9e\n'
     orchestration_v2_projection_turn_items command_execution .output = same
     logs/provider/events.<first-thread-id>.log: 1 occurrence (provider NDJSON event log)
   See db-hits.txt.
5. Credential-name scan of evidence and logs: OPENAI_API_KEY=, ANTHROPIC_AUTH_TOKEN=, ANTHROPIC_API_KEY=,
   GH_TOKEN=, GITHUB_TOKEN=, AWS_SECRET_ACCESS_KEY=, CAFE_TOKEN= all 0; no sk-* tokens.