feat: ue_x3d_* MCP tools -- the harness on the wire (v0.4.0)

[JosephOIbrahim]

ue_x3d_* -- the harness on the wire

The v0.3.0 UE<->X3D harness (x3d_bridge) is now MCP tools: Claude can export a
live level to X3D, validate it, apply transform edits back, and preview it --
inside the editor. All four are CORE-tier (mounted by default); Epic's MCP
has no X3D surface.

Added

• ue_x3d_export -- serialize the current level to X3D (each actor's
  quaternion transform, static mesh, material, attach parent; UE Z-up-cm ->
  X3D Y-up-m). mesh_only by default.
• ue_x3d_validate -- the paper boundary as a tool: out-of-grammar nodes,
  dangling USE, wrong arity, non-X3D roots, NaN/inf -- rejected without
  touching the editor.
• ue_x3d_apply -- apply an X3D document's transforms back to the live level
  (validated, guids sanitized, emitted via ue_execute_python). Transforms in
  v0.4.0; spawn/material/reparent apply are follow-ups.
• ue_x3d_preview -- render X3D to a standalone X_ITE browser page.
• 14 async tests + exec-sim coverage for the codegen tools (stub extended with
  Quat/Transform/get_actor_transform). Tier table pinned at 60 tools / 22 CORE.

Notes

• Editor-independent and CI-green. The live round-trip against a real 5.8
  scene is gated on ue_preflight reading green (bAllowAnyRemoteFunctionCall
  applied). B stays analytic (not glTF-calibrated) -- round trip is
  basis-agnostic, so fidelity-only.

[coderabbitai]

Warning

Review limit reached

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

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

Review profile: CHILL

Plan: Pro

Run ID: 42abf228-0ef0-43da-8fe4-38452046c737

📥 Commits

Reviewing files that changed from the base of the PR and between f01c263 and 15d49de.

📒 Files selected for processing (8)

• CHANGELOG.md
• tests/exec_sim/registry.py
• tests/exec_sim/unreal_stub.py
• tests/test_registry_tiers.py
• tests/test_x3d_async.py
• ue_mcp/__version__.py
• ue_mcp/tools/__init__.py
• ue_mcp/tools/x3d.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/x3d-tools

---

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