fix: Device Simulator support for screenshot and mouse flow

[hatayama]

Refs: MasaVault 2026-07-14_シミュレーターモードでのマウスシミュレート調査.md (final PR / To-Do 15)

Summary

Umbrella PR for Device Simulator support. Merges stacked work from feature/simulator-view-support:

• fix: capture Device Simulator rendering via PlayModeView #1766 — GameViewBridge reads PlayModeView.m_TargetTexture via GetMainPlayModeView() so rendering screenshots work under Device Simulator
• fix: fall back window screenshots to Device Simulator #1767 — --capture-mode window falls back from default Game to Simulator when the Game tab is absent
• docs: add Device Simulator guidance to mouse/screenshot skills #1768 — Skill docs: prefer rendering capture; simulate/raycast work under Simulator

Goal verification

Condition	Result
Simulator view + Play Mode: screenshot --capture-mode rendering --annotate-elements → simulate-mouse-ui Click hits button	Pass — PNG returned (e.g. 2048×1536), annotate coords hit ClickButton1, [Demo] Clicked 'ClickButton1' in logs
Normal Game View: same annotate → click flow still works (no regression)	Pass — rendering capture + annotate + click succeeded after switching main play view back to GameView

Additional Simulator checks (Fit to Screen / Scale / portrait rotation / Safe Area ON): annotate → click still hit. Fit/Scale/Safe Area are chrome-only; re-annotate after rotation.

User Impact

• Agents can use the standard screenshot-annotate-click loop while the Game tab is Device Simulator.
• Default window screenshots no longer return 0 results when only Simulator is open.

Test plan

• Local: compile 0/0; GameViewBridge + ScreenshotWindowNameResolver unit tests
• Local device: Simulator + Game View acceptance flows above
• CI green on this PR (v3-beta base — full GHA applies)

Made with Cursor

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 49 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: 95edaa6c-41fd-47fa-ae7d-e81bb12b31c3

📥 Commits

Reviewing files that changed from the base of the PR and between 625282d and f4f2188.

⛔ Files ignored due to path filters (5)

• Assets/Tests/Editor/GameViewBridgeTests.cs.meta is excluded by none and included by none
• Assets/Tests/Editor/ScreenshotWindowNameResolverTests.cs.meta is excluded by none and included by none
• Assets/Tests/Editor/UnityCLILoop.Tests.Editor.asmdef is excluded by none and included by none
• Packages/src/Editor/FirstPartyTools/Screenshot/ScreenshotWindowNameResolver.cs.meta is excluded by none and included by none
• Packages/src/Editor/InternalAPIBridge/AssemblyInfo.cs.meta is excluded by none and included by none

📒 Files selected for processing (25)

• .agents/skills/uloop-raycast/SKILL.md
• .agents/skills/uloop-screenshot/SKILL.md
• .agents/skills/uloop-screenshot/references/annotated-elements.md
• .agents/skills/uloop-simulate-mouse-input/SKILL.md
• .agents/skills/uloop-simulate-mouse-ui/SKILL.md
• .claude/skills/uloop-raycast/SKILL.md
• .claude/skills/uloop-screenshot/SKILL.md
• .claude/skills/uloop-screenshot/references/annotated-elements.md
• .claude/skills/uloop-simulate-mouse-input/SKILL.md
• .claude/skills/uloop-simulate-mouse-ui/SKILL.md
• Assets/Tests/Editor/GameViewBridgeTests.cs
• Assets/Tests/Editor/ScreenshotWindowNameResolverTests.cs
• Packages/src/Editor/FirstPartyTools/Raycast/Skill/SKILL.md
• Packages/src/Editor/FirstPartyTools/Screenshot/EditorWindowCaptureUtility.cs
• Packages/src/Editor/FirstPartyTools/Screenshot/ScreenshotUseCase.cs
• Packages/src/Editor/FirstPartyTools/Screenshot/ScreenshotWindowNameResolver.cs
• Packages/src/Editor/FirstPartyTools/Screenshot/Skill/SKILL.md
• Packages/src/Editor/FirstPartyTools/Screenshot/Skill/references/annotated-elements.md
• Packages/src/Editor/FirstPartyTools/Screenshot/UIElementAnnotator.cs
• Packages/src/Editor/FirstPartyTools/SimulateMouseInput/Skill/SKILL.md
• Packages/src/Editor/FirstPartyTools/SimulateMouseUi/Skill/SKILL.md
• Packages/src/Editor/InternalAPIBridge/AssemblyInfo.cs
• Packages/src/Editor/InternalAPIBridge/GameViewBridge.cs
• Packages/src/Editor/ToolContracts/ScreenshotSchema.cs
• Packages/src/Editor/ToolContracts/UnityCliLoopConstants.cs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/simulator-view-support

---

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