verify-preview

Run a structured QA pass: reset the preview environment, capture the relevant runtime view, drive one interaction, check logs for errors, and report verdicts backed by captures. Each expectation should be confirmed with an image or a quoted log line.

Use CaptureRuntimeViewTool with object-framed mode (uniqueIds and isolate) to inspect a specific object, or scene mode for overall composition. Re-capture after any change, since stale image files are not valid evidence.

The unknown_command error means the Lens lacks AgentInteractScript; the MCP layer auto-installs only the inspect side. This is an infrastructure setup gap, not a feature failure, and is resolved through the preview interaction setup.

A visually empty scene is often a script crash rather than a rendering issue, so check runtime logs with RunAndCollectLogsTool first. Also reset the preview environment, since stale interactions or leftover spawned objects can poison the evidence.

No, animated content can be misleading in a single frame. Capture at two or more timestamps before judging motion, and prefer object-framed captures when checking one object since scene-wide shots hide small defects.