security: reconstruct exact connection-pool policy boundary on current timeout head

[seonghobae]

Purpose

Replace stale stacked PR #169 with the exact current connection-pool policy candidate on the current timeout-policy head. Historical checks, reviews, approvals, mergeability, and base identity are not transferred.

Exact current identity

• current predecessor security: reconstruct exact request-timeout policy boundary on integrated main #158 head/base: 496d81709ad63be6b921510c447e7d2393daed96;
• exact current head: 2cce1de4a153b8b844b4dfd80de868f0667b7cae;
• current base/head state: open / Draft / mergeable after reconciliation;
• reconciliation preserved the exact timeout-policy boundary and added the connection-pool exact-type boundary.

TDD / validation

The focused regression requires both public policy constructors to reject an EgressConnectionPoolPolicy subclass before subclass-controlled pool capacity can replace reviewed finite limits. Exact current local Python 3.14 evidence: 939 tests passed; production statement/branch coverage is 100% (1704/1704, 576/576); Ruff, hourly product-guard self-test, and compileall pass.

Keep Draft while predecessor #158 is unintegrated. Aggregate Security Scan success is not dependency-review acceptance while the actual pinned Dependency review action is skipped; .github#897 remains the central prerequisite. No self-approval, Admin merge, bypass, or auto-merge.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 39 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: 88db1bee-4962-49f5-b5b5-79fc4fc2dacb

📥 Commits

Reviewing files that changed from the base of the PR and between 496d817 and 2cce1de.

📒 Files selected for processing (5)

• CHANGELOG.md
• docs/research/connection-pool-resource-limits.md
• src/egressweave/policy.py
• tests/test_connection_pool_policy_type_boundary.py
• tests/test_connection_pool_policy_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 full review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

---

Your included review limit is currently reached under our Fair Usage Limits Policy. This review may still proceed through usage-based billing if eligible. Your next included review will be available in 20 minutes.

[seonghobae]

Exact-head reconciliation complete: predecessor #158 moved to 496d81709ad63be6b921510c447e7d2393daed96, and this PR is now 2cce1de4a153b8b844b4dfd80de868f0667b7cae. Local Python 3.14 validation on the reconciled tree: 939 passed, 100% production statement/branch coverage (1704/1704, 576/576), Ruff, product-guard self-test, and compileall all pass. It remains Draft behind #158; no historical evidence transfer and no merge until independent review plus accepted central dependency-review execution.

[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]

Superseded by #221, which reconstructs the exact EgressConnectionPoolPolicy type boundary on the current method/timeout stack with hosted RED evidence, minimal GREEN implementation, migration documentation, and exact-head 100% statement/branch coverage. Historical checks, reviews, base identity, and mergeability from this stale branch are not acceptance evidence and are intentionally not transferred.