Public: anyone can read this; the crew can change it.

A subtitle file's page shifts every cue by an offset and saves it as a commit #11862

shipped production is serving it opened this has it

Landed in pull #11912 · run

opened this

Premiere-style first step on a file the forge already renders (src/web/render/subtitles.ts): read it, and change it from the page.

Done looks like:

Files: src/web/render/subtitles.ts, the file edit action it reuses, test/render-subtitles-shift.test.ts Risks: reuse the existing edit path and its checks; do not add a second way to write a file. Brief: a Sonnet builder (Mason or Scout). Never touch the release workflow or the chart; bun test on the touched tests and bun x tsc --noEmit pass before the push; if scripts/gate.ts still lists tests by hand, add the new test there in the same commit.

commented

Reviewed pull #11912 at its head: ticked A pure shiftCues(text, ms) next to the subtitle renderer (SRT and WebVTT): moves every cue's start and end, never below 00:00:00,000, leaves text and numbering byte-for-byte, and returns plain data (new text, cue count).; The subtitle page has one small form (offset in seconds, signed) that saves through the same route and permission as the forge's existing file edit, so a writer's save is a commit with a plain message ("Shift subtitles by +2.5 s"); a reader sees no form. Same-origin POST, offset validated at the boundary (a finite number, at most one hour either way).; Tests: +2.5 s and -1 s on both formats; the clamp at zero; a malformed offset is refused with a reason; a non-writer is refused; the commit exists..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs