Files
hyperframes/packages
Vance IngallsandClaude Opus 5 7d214e96ec feat(producer): recycle the browser between segments and retry target loss once
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>
2026-09-18 20:53:05 -07:00
..
2026-09-18 19:41:06 -07:00
2026-09-18 19:41:06 -07:00
2026-09-18 19:41:06 -07:00
2026-09-18 19:41:06 -07:00
2026-09-18 19:41:06 -07:00
2026-09-18 19:41:06 -07:00