docs(claude): spell out the issue priority order

[cristim]

Summary

Step 1 of CLAUDE.md's "Issue assignment" section (added in #421) said only "Take the highest-priority open issue that nobody owns, oldest first within a priority". It now spells out the full order:

Take the highest-priority open issue that nobody owns: priority/p0 through p3, then no priority label. Within a level, prefer higher urgency/, then higher impact/, then issues that unblock others, then smaller effort/*. Break remaining ties oldest first. Skip status/blocked, status/needs-info, status/wontdo, and anything assigned, claimed or already covered by an open PR.

The gh query blocks below it are unchanged. This matches LeanerCloud/cloud-commitments-platform#947 and LeanerCloud/cloud-commitments-mcp#75.

No closing issue (owner request), so label mirroring does not apply.

Docs-only; the commit and pre-push hooks pass, including markdownlint.

🤖 Generated with Claude Code

[cristim]

@coderabbitai review

[coderabbitai]

Warning

Review limit reached

• Run on-demand review

_{This review includes 1 billable file and costs up to $0.25.}

• Ask an admin to make reviews automatic

Open in CodeRabbit

Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing.

Or wait 49 minutes for your next included review.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available. Your 72 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Repository: LeanerCloud/cloud-commitments-go/.coderabbit.yaml
• Review profile: CHILL
• Plan: Essentials
• Run ID: adcb2dbf-eadd-4952-91b6-794747bacaa3

📥 Commits

Reviewing files that changed from the base of the PR and between 9afa2d5 and adb8f29.

📒 Files selected for processing: 1

• CLAUDE.md

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[cristim]

Independent review: CLEAN at 991257972b6db13c87e41a8e3151f752d5c487b7. Reviewer: claude-go-pr-merge-4 (merge driver, not the author).

Docs-only, CLAUDE.md +5/-2. The new step 1 states the full selection order:

• priority p0 to p3, then unlabelled;
• within a level, urgency, then impact, then unblocks-others, then smaller effort;
• remaining ties oldest first.

The skip list adds "assigned, claimed or already covered by an open PR". The status/blocked, status/needs-info and status/wontdo labels it names exist in this repo. The gh query blocks below are unchanged, and no em-dashes are introduced.

Non-blocking nit: the sentence before the query block used to end with a colon introducing it, and now ends with a full stop.

No closing issue (owner request), so label mirroring does not apply. CodeRabbit is quota-limited. If that holds at merge time: CR waived: quota, adversarial review + local verification + green CI.

[cristim]

Updated onto main 9afa2d5 (after #504) using server-side update-branch. New head adb8f2980c4c599825583cde05270db27526a566. git range-diff shows 9912579 = adb8f29, identical, so the CLEAN verdict carries over. CI had passed on 9912579 and is re-running.

[cristim]

Merged by squash at reviewed head adb8f2980c4c599825583cde05270db27526a566 as 03752158. The gates were met on that SHA:

• independent review CLEAN, posted above (carried across rebases by identical git range-diff)
• local verification posted above
• CI green on adb8f298
• labels mirrored; no unresolved threads

CR waived: quota, adversarial review + local verification + green CI. A retrospective CodeRabbit review will run when quota returns. No closing issue (owner request).