security: reconstruct exact TLS configuration boundary on current main

[seonghobae]

Superseded by current integrated-main reconstruction

This historical current-main reconstruction is closed without merge because protected main advanced from its base d3498ec9455bfd3f3bb7df78c914de0a5d1120fc to dd0324c0d7edb6effc74737039d1e754af09f5aa after the candidate was built.

Ready PR #157 preserves the unique TLS boundary, regression tests, operator/research guidance, documentation contract, and [Unreleased] history on that exact integrated base. Its current exact head is 1db2a43cc367f15fb0eab6b3dfd682ca5ae44919; CI 31445002331 and SAST 31445002332 are green with exact 100% owned production statement/branch coverage. Security Scan 31445002376 still has the actual pinned Dependency review step skipped, so #157 is not merge-ready until the read-only central fail-closed dependency-review repair is integrated and the unchanged head is revalidated.

Historical RED/GREEN evidence in this PR remains useful audit history; no check, review, approval, base identity, or mergeability from this PR transfers to #157.

[coderabbitai]

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 35 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d319f33f-80bd-4bc0-8ec1-e09e3a5aea7b

📥 Commits

Reviewing files that changed from the base of the PR and between d3498ec and b5834a8.

📒 Files selected for processing (5)

• CHANGELOG.md
• docs/research/tls-configuration.md
• src/egressweave/tls.py
• tests/test_tls_configuration_exact_type.py
• tests/test_tls_configuration_exact_type_documentation.py

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[seonghobae]

@coderabbitai review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.