Skip to content

fix(transcript): claim fresh rollouts from exact proxy identity - #44

Merged
Juliusolsson05 merged 6 commits into
mainfrom
fix/proxy-rollout-identity
Aug 30, 2026
Merged

Juliusolsson05 merged 6 commits into
mainfrom
fix/proxy-rollout-identity

Conversation

@Juliusolsson05

Copy link
Copy Markdown
Owner

Summary

  • recover the exact Codex rollout id from bounded, forwarded Responses proxy metadata
  • prove filename and session metadata identity before using the existing lease and generation-bound tail
  • fail closed for malformed, oversized, ambiguous, subagent, and non-portable zstd frames
  • add recorded exact-identity, concurrency, packaging, and portable decoder contracts

Verification

  • npm run test:contract
  • npm run typecheck
  • focused recorded proxy tests on Node 20.19, 22.12, and 24
  • npm run test:package
  • standalone-clone full suite: 15 files, 177 tests passed before the final decoder-only regression; final focused decoder suite: 7 tests passed

A final full run in the shared local checkout had four unrelated 5-second rollout-test timeouts under CPU contention. The changed tests and typecheck stayed green; CI is the final clean-environment gate.

@Juliusolsson05
Juliusolsson05 merged commit 726667b into main Aug 30, 2026
6 checks passed
@Juliusolsson05
Juliusolsson05 deleted the fix/proxy-rollout-identity branch August 30, 2026 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant