proofread-subtitleslisted

## Reference Ask author for domain-specific terms engine likely misrenders. Use that list as primary reference for errors. Proceed without list when author declines. Flag uncertain cues by number instead. ## Structure Keep timestamps, cue numbers, and blank line between cues unchanged. Keep each cue's boundaries exactly as in source. Break any line over 42 characters into two within same cue. Split at clause boundary, comma, or conjunction. Allow at most two text lines per cue. Shorten wording rather than add third line. ## Punctuation Add punctuation where spoken phrasing requires it. Follow source language's rules. Capitalize first word of every sentence and every proper noun. End every sentence with terminal mark. ## Corrections Fix obvious homophone and word misrecognitions when context is unambiguous. Preserve computer jargon in its conventional form. Use `API`, `CLI`, `Git`, `Docker`, `JSON`, `HTTP`, and `Kubernetes` as written. Fix typos and spacing errors without rewording sentence. ## Russian In Russian subtitles, write computer terms in English. Follow conventions of Russian tech speech. Write `pull request` instead of `пулл реквест`. Keep transliterations already standard in Russian. ## Preserve Preserve speaker's word choice and phrasing. Keep filler words like `uh`, `um`, `well`, `ну`, and `вот`. Delete them only when author requests filler-free transcript. Omit speaker labels and sound descriptions. Add bracketed annotations only where source already