security: reconstruct exact connection-count values on current pool-policy stack

[seonghobae]

Purpose

Reconstruct issue #120's unique primitive connection-count integrity boundary on the current pool-policy candidate #182. Historical #152 evidence is not transferred.

Exact stack identity

• current predecessor / base security: reconstruct exact connection-pool policy boundary on current timeout head #182 head: 2cce1de4a153b8b844b4dfd80de868f0667b7cae;
• exact current head: dd8bc0e044fac96d355f3c46b57b4fc3f12bb1ae;
• current state: open / Draft / mergeable after stack reconciliation.

TDD / validation

The focused regression rejects int subclasses while preserving exact built-in integers and reviewed ASCII decimal strings. Exact current local Python 3.14 evidence: 944 tests passed; production statement/branch coverage is 100% (1704/1704, 576/576); Ruff, hourly product-guard self-test, and compileall pass.

Keep Draft behind #182 until the predecessor is accepted/integrated. 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]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: cd204322-0035-4d8f-a5b6-e75eccd17c4d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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]

Exact-current-head review evidence for the ready current-stack reconstruction:

• head 826db8d549ee34d04c387bf538fb0ebfbbe7cfb3, base security: reconstruct exact connection-pool policy boundary on current timeout head #182 head 53d0731862549b3d94d436526243a308b5d7b071;
• local focused pool-count/policy tests: 40 passed; full suite: 901 passed; production statement and branch coverage: 100% (1704/1704 statements, 576/576 branches); Ruff, hourly product guard self-test, and compileall passed;
• exact-head SARIF has 0 alerts and no unresolved current review threads;
• because this PR is stacked on security: reconstruct exact connection-pool policy boundary on current timeout head #182, hosted review/security workflows that are disabled for non-default base branches are not acceptance evidence. Keep the accepted predecessor chain and the real central dependency-review gate before integration.

[seonghobae]

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

[seonghobae]

Superseded by #222, which reconstructs the exact built-in connection-count value boundary on the current policy stack with hosted RED evidence, the minimal exact-int GREEN change, migration documentation, and exact-head 1,042-test / 100% statement-and-branch verification. Historical checks, reviews, base identity, and mergeability from this stale branch are intentionally not transferred.