fix(config): rebuild typed configuration normalization on current main

[seonghobae]

Controlled current-main replacement for #86

PR #86 contains valid typed-configuration hardening but is now conflicted after substantial protected-main movement. Fresh path comparison shows protected main has not changed pg_llm_batch/config.py or #86's focused configuration tests/doctoring since #86's merge base; only CHANGELOG.md overlaps. This replacement therefore starts from exact protected main 3e029d8d38032eaffa60bd95026b7a05839691fa and reacquires evidence rather than transferring stale checks.

RED-first boundary

Head a6e0eec1f02b699878c82daf2e46f0be1499c51f adds only one focused regression: malformed persisted boolean text must fall back to the declared false default rather than becoming truthy. Production behavior is intentionally unchanged at this head so exact-source CI can prove the defect.

After RED is observed, the smallest configuration fix will follow on this same branch. Further #86 semantics—write normalization, JSON collection type safety, cache defensive copies, and mutable-default isolation—will be added only through subsequent test-first cycles. CHANGELOG.md will be composed from current protected content rather than copied from the stale branch.

No #86 check/review/approval evidence transfers. No force-push, destructive rebase, gate weakening, release action, or overlap with active tenant/health branches is introduced.

Merge boundary

Keep Draft until RED → GREEN cycles complete, exact-current-head CI/security/coverage/review evidence is terminal-success, review threads are resolved, and live rules are satisfied. Close #86 as superseded only after replacement equivalence and unique-work preservation are proven.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 8 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: b5a79ad8-7a0f-4b04-9319-e48ddeca94f7

📥 Commits

Reviewing files that changed from the base of the PR and between 0125722 and 8420d77.

📒 Files selected for processing (3)

• pg_llm_batch/config.py
• tests/test_config_boolean_fallback.py
• tests/test_config_collection_type_fallback.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.}