You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit eb82dbf
Browse filesBrowse the repository at this point in the historyBrowse files
#1435 landed on main and solves replay deduplication the same problem
this branch addressed, but from a better angle: it matches a forked
session's leading events against the immutable parent stream instead of
inferring the boundary from the child log alone.
Resolution takes main's replay implementation wholesale and keeps only
this branch's speed-tier work, which main does not have:
- parser: main's CodexReplayState and replay_prefix plumbing, with
recorded service tiers threaded back through the session entry visitor
- aggregate: main's CodexAggregateRun and CodexReplayPlan wiring, with
the recorded-tier dedupe records and bucket attribution kept
- loader: main's replay plan threading, with tier reconciliation kept
The branch's own replay work is dropped as superseded. That also retires
the subagent turn-marker heuristic, its CLI-version gate, and the marker
tests, which is a real improvement: the gate read session_meta
cli_version, a field that resume rewrites from the original session, and
a missing marker discarded a whole rollout. Matching against the parent
stream depends on neither. main's replay tests are carried over intact.
Codex totals are byte-identical to main on real rollouts, and recorded
tiers still classify usage that config fallback would otherwise cover.
0 commit comments