feat(hygiene): sweep auto-adds non-WSC issues + bot auto-classify

[yakimoto]

Extends the daily sweep: known-bot issues (renovate[bot]/dependabot[bot]/socket-security[bot] -> Area=Substrate/Priority=P2, corridor-security[bot] -> Area=Identity/Priority=P1) get their board fields set directly instead of needs-triage-labeled. A new step auto-adds org open issues not yet on project #3, excluding wave-surfer-connect (double-guarded: search filter + explicit repo check in the loop). Capped at 200 adds and 20 pages per run, with a step-summary line reporting the count and cap status.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

---

Note

Medium Risk
The workflow bulk-writes org Project v2 fields and adds issues to the shared board; mistakes could mis-triage bot work or flood the board, though caps and a fixed bot allow-list limit blast radius.

Overview
Extends the daily ticket-hygiene sweep so under-fielded board items are handled differently for known automation authors, and open org issues can be pulled onto the WAVE project automatically.

During the Flag under-fielded items pass, the sweep now loads each item’s author and project item id. Issues from an allow-listed set of bots get Area and Priority set on the org project via GraphQL (using new workflow env AREA_FIELD_ID / PRIORITY_FIELD_ID) when those fields are still empty; everyone else still gets needs-triage. The step summary reports both flagged and auto-classified counts.

A new step Auto-add non-WSC issues to the board searches for open wave-av issues not already on project #3, excludes wave-surfer-connect in the query and again in the loop, and adds up to 200 items per run (max 20 search pages), with cap status in the summary.

^{Reviewed by Cursor Bugbot for commit 46a5e7d. Configure here.}

---

Summary by cubic

Auto-classifies known bot-authored issues and auto-adds open org issues to Project #3 to reduce triage noise and keep the board current. Adds caps, clear step-summary reporting, and a private repo exclusion via HYGIENE_EXCLUDE_REPOS.

• New Features
  • Bot auto-classify: sets Area and Priority directly for renovate[bot], dependabot[bot], socket-security[bot] (Substrate/P2) and corridor-security[bot] (Identity/P1) when missing, instead of labeling needs-triage.
  • Auto-add issues: adds open org:wave-av issues not on Project feat: add capabilities.json (platform-registry Phase D) #3, excluding the repo provided via HYGIENE_EXCLUDE_REPOS (double-guarded), up to 200 adds/run and 20 pages. Step summary reports added count, cap status, and bot-classified count.

^{Written for commit addb8af. Summary will update on new commits.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: addb8af

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_a07f7888-49d0-4c43-bf35-5a64405f0642)

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 40 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 85fc5994-d36e-46e2-8255-d700b5d6b3a6

📥 Commits

Reviewing files that changed from the base of the PR and between 14010fb and addb8af.

📒 Files selected for processing (1)

• .github/workflows/ticket-hygiene.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch sweep-autoadd-botclassify

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch sweep-autoadd-botclassify

---

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