ci: remind to sync the roadmap wiki when roadmap docs change

[OBenner]

What

Adds .github/workflows/wiki-roadmap-reminder.yml — a lightweight CI reminder that keeps the roadmap wiki in sync with the roadmap source docs.

Why

The wiki now hosts the consolidated roadmap/status pages (Home dashboard + one page per roadmap). Those pages restate what lives in docs/, so they drift the moment a roadmap-affecting PR lands. This workflow makes the drift visible instead of silent.

How it works

• Trigger: push to develop touching any roadmap source:
  • ROADMAP.md, docs/strategy/roadmap.md, docs/roadmap/**, docs/LANGUAGE_SUPPORT_ROADMAP.md, docs/DEVICE_GUI_VERIFICATION_ROADMAP.md
• Action: opens an issue titled 📋 Roadmap wiki needs updating (label wiki-sync), listing the changed files and the commit. If an open wiki-sync issue already exists, it comments on that one instead — so merges don't pile up duplicate issues.
• It never edits the wiki itself — updating the prose is a human step. The issue points at the pages to sync and closes when the wiki matches develop.

Permissions: issues: write only. Uses actions/github-script@v9 (matching the repo's existing workflows). YAML validated locally.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 38 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

Run ID: 1be59c17-b70e-42e6-9d51-a34824dc5bce

📥 Commits

Reviewing files that changed from the base of the PR and between d5ac1ee and 8a6e49a.

📒 Files selected for processing (1)

• .github/workflows/wiki-roadmap-reminder.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/wiki-roadmap-reminder

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud