chore: Document pause-point behaviors surfaced by round-3 usage feedback

[hatayama]

Summary

• Documents five pause-point behaviors that agent-driven verification runs discovered but the skill never explained, so agents no longer have to rediscover them by trial and error.

User Impact

• Agents using an id-only marker (UloopPausePoint.Pause(id)) previously had no way to know it captures nothing; the skill now says so up front and points to alternatives.
• The skill now states the snapshot is taken before the target line runs (pre-line), matching IDE breakpoint semantics, right where the first-time workflow reads captured variables.
• TryGetCapturedValue guidance now clarifies it only returns data for file:line marker hits, not id-only markers.
• Timeout troubleshooting now cross-references JIT inlining as a cause of HitCount=0, instead of leaving that note only under Requirements & Safety.
• Adds a warning that writing to transform/Rigidbody2D fields while paused can silently fail to take effect until the next simulation step, with a way to verify it did.
• Clarifies that continuous capture mode or multiple simultaneously-armed markers can replace repeated enable/await/clear cycles for multi-step verification.

Changes

• Updated Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/SKILL.md (source of truth).
• Regenerated the synced copies under .claude/skills/uloop-pause-point/SKILL.md and .agents/skills/uloop-pause-point/SKILL.md via uloop skills install --claude --agents.

Verification

• diff confirms all three SKILL.md copies are byte-identical after regeneration.
• Docs-only change; no compile or test suite affected.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 41 seconds

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: d49471a2-493b-402a-9e90-68069beb057e

📥 Commits

Reviewing files that changed from the base of the PR and between 6bf4f76 and 0bcc0a0.

📒 Files selected for processing (3)

• .agents/skills/uloop-pause-point/SKILL.md
• .claude/skills/uloop-pause-point/SKILL.md
• Packages/src/Editor/CliOnlyTools~/PausePoint/Skill/SKILL.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/skill-md-round3-gaps

---

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