fix(storage): scope quarantine application lookup to this raw's own receipt

[Sinity]

Summary

Fix the next layer found while completing polylogue-zaiz's investigation: after PR #3371's fan-out scoping fix, the 3 real stuck sessions still failed inspection with "competing raw-revision application authority exists". This reveals the true final classification for these sessions.

Problem

raw_revision_applications is an append-only decision history, not a single-current-state table. Any session with more than one historical revision-authority decision accumulates multiple rows for the same logical_source_key. The lookup matched raw_id = ? OR accepted_raw_id = ?, additionally pulling in rows from OTHER raw_ids' own receipts that cite this raw as their superseded predecessor.

Solution

Scope the lookup to raw_id = ? AND logical_source_key = ? alone. New regression test seeds a legitimate prior superseded decision and confirms eligibility is unaffected; anti-vacuity confirmed by reverting.

Definitive finding

Applying this fix against the live archive (read-only) advances all 3 stuck sessions to their genuine final classification: accepted_frontier_kind='semantic', not 'byte'. These sessions were originally accepted under semantic equivalence, not a byte-proof — refine_quarantined_raw requires byte-frontier authority by design and cannot resolve them. This is not a bug; it's a real architectural boundary. Recorded on polylogue-zaiz as the definitive answer — resolving it needs a semantic-frontier-aware actuator (a separate feature) or fresh reacquisition, out of scope here.

Verification

• devtools test tests/unit/storage/test_quarantined_accepted_raw_repair.py tests/unit/storage/test_duplicate_raw_identity_repair.py tests/unit/storage/test_raw_authority_ledger.py → 53 passed
• mypy polylogue/storage/repair.py → clean
• devtools verify --quick → exit 0

Ref polylogue-zaiz, polylogue-ihc8

Co-Authored-By: Claude noreply@anthropic.com

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 39 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 3cd82703-c314-4266-899e-2d7d22cff8f2

📥 Commits

Reviewing files that changed from the base of the PR and between 45434fa and 4609951.

📒 Files selected for processing (2)

• polylogue/storage/repair.py
• tests/unit/storage/test_quarantined_accepted_raw_repair.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/quarantine-application-history-scoping-zaiz

---

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.}