Repository navigation
fix(video): preserve fallback transcripts as safe text content - #16635
Conversation
…y-16635-reconcile-20261015
|
Continued the owner-approved video closeout on this original PR. Published reconciliation commit Scoped evidence, using matching-lock borrowed dependencies (diagnostic, not clean-install certification):
Reviewed bounded fallback text conversion, client/unverified provenance, combined raw-input budgets, removal of transcript extension fields, caller-request immutability and retention shadows. No additional production code or timeout changes were made in this continuation. Outstanding: real translations of the changed video contract, reconciliation against the newer release |
CI Coverage Report
Coverage artifact was not available for this run. |
Summary
Reconcile Video Bridge's failed/skipped-video transcript fallback with the strict
OpenAI content-part field allowlist. This preserves skygunner's compatibility
fix in #16395; it does not widen or revert that allowlist.
transcript/audioTranscriptcues become supported text partswith explicit untrusted-client and unverified-media/timestamp warnings.
Request-provided provenance never becomes server-authenticated provenance.
carrier objects; retain capability-safe video/marker behavior.
retain original-field, pending/log/artifact and cache/Memory protection.
requests, settings defaults, promotion thresholds or operational-skill changes.
extension-field passthrough. Related to feat(backend): video-bridge #12150 P2 — remaining transcript-retention surfaces (raw snapshot, continuation, derived-prompt dispatches, response/semantic-cache) #12430 and feat(video-bridge): redact/retain-safe transcript data across logs, Memory and continuation #12150; not closing either.
Evidence
All tests executed on the designated VPS. HTTP RED reproduced lost top-level
transcripts and leaked nested extensions. GREEN initially passed the public
route/actual translator/SQLite retention matrix. Two-axis review then found a
duplicate-cue combined-budget bypass; new HTTP tests reproduced both count and
byte variants RED, then passed after correction. Native/disabled and Responses
controls also pass. Final focused HTTP result: 13 passing, zero failures/skips.
At exact clean head
fd62a801a7eeb535a7268ffeb2b3a137bb64d638, 52 scopedfiles / 482 tests PASS, zero failures/skips, including real FFmpeg and
strict translator tests. Docs-all, changed-file ESLint, core typecheck and
cycles ratchet (14 <= 14) PASS. Before/after SHA and cleanliness match.
File-size remains FAIL with four signatures reproduced byte-for-byte on exact
base
e369ffc633131ef0b1ddbee9d2b40475e63c0808: responseSanitizer 1216 > 1214,error.ts 1218 > 1217, translator-openai-responses-req.test.ts 1476 > 1470,
vscode-token-routes.test.ts 1268 > 1267. They are BASE-RED, not waived.
Strict translation drift FAIL on the new GUARDRAILS English source. It also
reports 396 stale locale records; warning-only reporting is not proof of fresh
translations. Overall scoped gate receipt is FAIL, not release-ready.
Static Spec and Standards rechecks report no remaining findings in the final
delta. Dependencies remain borrowed, not clean-lock certification.
Admission
the new English contract; ongoing older-source translations cannot certify it.
Required full gates, original campaign-PR integration, provider/corpus evidence
and deployment remain separate. Draft; no baseline weakening or admin merge.