Issue 7090, round 2 runtime reproduction
Commit: 6490a9e874 (origin/main fetched 2026-10-21)
Worktree: /home/ubuntu/wt/issue-7090
Command: PATH="$PWD/node_modules/.bin:$HOME/.bun/bin:$PATH" vp run dev
Dev runner: serverPort=16188 webPort=8148 baseDir=/home/ubuntu/wt/issue-7090/.t3
Browser: T3 collaborative Browser panel, Chromium, 1280x800, /usage, Tokens, 30 days.
Fixture: isolated Codex home configured via providerInstances.codex.config.homePath.
a.jsonl: session_meta issue7090-a, turn_context gpt-5.5, token_count input=100 output=20.
b.jsonl: session_meta issue7090-b, turn_context gpt-5.5, token_count input=300 output=60.
Both events timestamped 2026-10-21 at fixture creation.
Attempt 1: both files in sessions/. Usage Codex: 2 sessions, 480 tokens.
Action: mv .t3/issue-7090-codex/sessions/b.jsonl .t3/issue-7090-codex/archived_sessions/b.jsonl
Click Refresh usage. Usage Codex: 2 sessions, 480 tokens. Warm cache retains previously scanned usage; immediate disappearance NOT reproduced.
Attempt 2: cp -r .t3/issue-7090-codex .t3/issue-7090-cold
Set providerInstances.codex.config.homePath to the new isolated home (identical JSONL bytes, uncached paths), Refresh usage.
Usage: 1 session, 120 tokens (100 uncached input, 20 output). Archived 360 tokens absent.
Conclusion: archived transcripts absent from cold scans on current main; previously cached transcripts mask this omission. No credentials were required or accessed for the fixture.