fix: reconcile Project v2 Status options

[v-Kaefer]

Linked Issue

• Closes fix: reconcile existing Project v2 single-select options #66

Milestone

• Mock Milestone

Related PRs

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

Summary

• Reconciles options for existing Project v2 single-select fields instead of skipping same-name fields.
• Fixes GitHub's built-in Status field (Todo, In Progress, Done) so GPA can apply its configured lifecycle options such as In review.
• Preserves existing option IDs when names match, avoiding unnecessary loss of existing item values.

How to test

• Test type: automated + live follow-up
• Steps: run repository quality and the new Project field reconciliation tests; then promote to Q.A so PR test: verify Q.A live metadata and cleanup after bootstrap #65 reruns the live structured PR Sync test.

Evidence

• Root cause reproduced by live QA on test: verify Q.A live metadata and cleanup after bootstrap #65
• Uses GitHub updateProjectV2Field for existing single-select options
• Unit coverage added for reconciliation and idempotency

Known risks

• Configured single-select options become declarative source of truth; options omitted from configuration will be removed on reconciliation.

DoD checklist

• Scope implemented as defined
• Tests added
• Failure mode addressed at Project provisioning layer
• 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: 14 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: 099f057a-3209-4d87-a630-47ed7e28e508

📥 Commits

Reviewing files that changed from the base of the PR and between 799208a and 139ef80.

📒 Files selected for processing (2)

• project_setup/project.py
• tests/test_project_field_reconciliation.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: reconcile existing Project v2 single-select options #66
• PR lifecycle target: Done
• Project v2: skipped because PROJECT_SETUP_PROJECT_NUMBER is not configured.
• Parent/sub-issue: no parent reference found.
• PR: fix: reconcile Project v2 Status options #67

[github-actions]

Promotion linkage

• State: merged
• Stage: Q.A
• Promotion PR: fix: promote Project v2 Status reconciliation to Q.A #68

[github-actions]

Promotion linkage

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