Skip to content

Qualify capture LF normalization to linked transcripts - #3097

Open
Chris0Jeky wants to merge 2 commits into
mainfrom
codex/2912-linked-transcript-line-endings
Open

Chris0Jeky wants to merge 2 commits into
mainfrom
codex/2912-linked-transcript-line-endings

Conversation

@Chris0Jeky

@Chris0Jeky Chris0Jeky commented Sep 15, 2026

Copy link
Copy Markdown
Owner

Summary

Close the final wording residual left after #2933. Capture reconciliation compares line endings without rewriting stored source text, but only linked-transcript correction normalizes the queue projection to LF. Ordinary suggestion edits preserve submitted bytes.

This change narrows both the helper comment and the public capture API guide to that actual boundary. It keeps the already-delivered durable/legacy export field contract and the six direct CaptureTextComparison cases unchanged.

Scope and behavior

  • No runtime, storage, export, reconciliation, allocation, endpoint, or schema behavior changes.
  • CaptureTextComparison.Equivalent remains byte-significant apart from line-ending normalization.
  • Initial creation may still retain submitted line endings in both representations.
  • Durable exports still use durableCapture.sourceAssets[].text; queue fallback remains legacySource.text only when no durable capture exists.
  • The branch is exactly two commits and two files ahead of main: the helper explanation and docs/api/CAPTURE.md.

Verification

Exact head: 5b70d1f5ca7a73d15538f882af48c70b831d2107.

  • Smart CI Self-Test run 34911547906: success.
  • CI Extended run 34911548088: success.
  • Main CI run 34911548083: all 18/18 jobs are terminal with no failure, queued, in-progress, or null-conclusion job. The GitHub Actions parent run still reports in_progress, which is a workflow-finalization/API lag rather than an executing or failed job.
  • Covered lanes include docs governance, release contract, secret scanning, dependency/security, SAST, architecture, source-launcher, frontend lint/typecheck/build/PWA, backend/API tests, and Windows helper validation.

No local execution result is claimed from this connector environment; the evidence above is the exact hosted head.

Closes #2912

@Chris0Jeky
Chris0Jeky marked this pull request as ready for review September 15, 2026 00:23
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 15, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-15T00:26:27.361050Z 5b70d1f Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Pending

Development

Successfully merging this pull request may close these issues.

Capture reconciliation: document RawText/export line-ending contract and unit-test CaptureTextComparison

1 participant