mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-04 21:17:30 +00:00
A segment boundary is the only safe point to hand capture a fresh browser, which is what makes the long-render failure class survivable: the session restarts every N segments, and a Chrome target loss mid-segment re-captures that segment once on a new session instead of failing the render. Retry is deliberately narrow. Encoder and authoring errors reproduce on a fresh browser, so retrying them doubles the time to the same failure — all three guards (retry exists, retry is classified, cadence boundary) are mutation-checked. The partial segment file is deleted before the retry so a later resume cannot see it, and onSegmentComplete still fires only after a successful close, so the manifest never records a partial segment. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>