feat: Add timeout diagnostics and outdated-runner hint to pause-point CLI errors

[hatayama]

Summary

• A HitCount=0 await-pause-point timeout now suggests pausing PlayMode before scenario setup, not just re-triggering the code path.
• An unrecognized flag on await-pause-point/pause-point-status now names an outdated installed project runner as a likely cause, alongside the existing typo/help pointer.

User Impact

• Previously, a timeout with no hits only advised re-triggering the code path, which does not help when a self-progressing game (timers, gravity, spawners) consumed the scenario before the marker could fire. The hint now also points at control-play-mode --action Pause as the preventive fix for next time.
• Previously, an unrecognized flag read as a plain typo, even when the actual cause was an installed project runner older than the flag's documentation. The error now suggests checking uloop --version and updating the CLI as an alternative explanation.

Changes

• Extended the existing HitCount=0 timeout hint in pausePointTimeoutHint with one additional sentence; no other diagnostic fields changed.
• Added a shared pausePointUnknownOptionError helper used by both await-pause-point and pause-point-status option parsing, replacing their near-duplicate inline error construction.
• No IPC or response-shape changes; both errors are CLI-side argument/diagnostic text only.

Verification

• scripts/check-go-cli.sh: all packages pass (fmt/vet/lint/test/build)
• dist/darwin-arm64/uloop await-pause-point --id jump --bogus-flag value: confirmed the new hint text in the response

[coderabbitai]

Warning

Review limit reached

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

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

Plan: Pro

Run ID: ae99b368-678b-4b75-893e-c82283a01416

📥 Commits

Reviewing files that changed from the base of the PR and between dfd8d00 and 67588c5.

📒 Files selected for processing (4)

• cli/project-runner/internal/projectrunner/native_command_help.go
• cli/project-runner/internal/projectrunner/pause_point_errors.go
• cli/project-runner/internal/projectrunner/pause_point_wait.go
• cli/project-runner/internal/projectrunner/pause_point_wait_test.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/pause-point-await-timeout-diagnostics

---

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