test(privacy): preserve token diagnostic confidentiality

[seonghobae]

Protected-main evidence completion for #131

Protected main now contains the bounded production repair from #150: generic PostgreSQL token-counting failures emit only the fixed package-owned PostgreSQL token counting failed category and no longer render lower-layer exception text. The separate UndefinedFunction warning and PostgreSQL-only/no-fallback authority remain unchanged.

This PR preserves the focused sentinel regression and APA 7 doctoring from the superseded #87 line on the exact current protected-main result. It changes no production code, schema, migration, provider protocol, credential, model, workflow, or release authority.

The regression injects a unique prompt/secret-like sentinel through the lower-layer token-counting exception, asserts the sentinel cannot enter package-owned logs, confirms the fixed finite diagnostic category remains observable, and confirms token counting still fails closed.

Merge only if the unchanged exact head passes current Python 3.10/3.12/3.14, exact coverage/docstrings/package, security/SAST, central required workflows, has zero valid unresolved findings, and satisfies live rules. After protected integration, issue #131 can be closed on protected-main evidence; no #87 predecessor checks or reviews transfer.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 2 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: de739625-e090-4552-abbd-d597020c0871

📥 Commits

Reviewing files that changed from the base of the PR and between 2d35f70 and c57515a.

📒 Files selected for processing (2)

• docs/doctoring/token-counting-diagnostic-confidentiality.md
• tests/test_token_counter_diagnostic_confidentiality.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.}