fix: wait for Project v2 readback in live QA

[v-Kaefer]

Linked Issue

• Closes fix: tolerate Project v2 read-after-write delay in live PR Sync QA #69

Milestone

• Mock Milestone

Related PRs

• <optional related pull request numbers; none for this implementation PR>

Summary

• Makes the live structured PR Sync verification tolerate bounded Project v2 read-after-write delay.
• Keeps production PR Sync behavior unchanged.
• Polls until both the linked task and In review status are visible, then fails if the state does not converge within 20 seconds.

How to test

• Test type: automated + live follow-up
• Steps: run Repository quality; promote to Q.A and verify test: verify Q.A live metadata and cleanup after bootstrap #65 Live QA reaches project_v2_task_status=passed and pr_sync_cleanup=passed.

Evidence

• Previous live run proved Project field reconciliation and PR metadata mutations succeeded
• Failure was limited to immediate Project list readback
• Fresh live run passes after promotion

Known risks

• Live QA may wait up to 20 seconds when GitHub Project reads are delayed.

DoD checklist

• Scope implemented as defined
• Production sync behavior unchanged
• Verification remains fail-closed after timeout
• No permission expansion

[coderabbitai]

Warning

Review limit reached

@v-Kaefer, 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: 187b51ab-5354-40c5-a5a9-aa5d403c327b

📥 Commits

Reviewing files that changed from the base of the PR and between 10749f0 and da6eee0.

📒 Files selected for processing (1)

• tests/qa/live_pr_sync.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.}

[github-actions]

PR Sync

• Linked task: fix: tolerate Project v2 read-after-write delay in live PR Sync QA #69
• PR lifecycle target: Done
• Project v2: skipped because PROJECT_SETUP_PROJECT_NUMBER is not configured.
• Parent/sub-issue: no parent reference found.
• PR: fix: wait for Project v2 readback in live QA #70

[github-actions]

Promotion linkage

• State: merged
• Stage: Q.A
• Promotion PR: fix: promote Project v2 readback tolerance to Q.A #71

[github-actions]

Promotion linkage

• State: planned
• Stage: main
• Promotion PR: test: verify Q.A live metadata and cleanup after bootstrap #65