Add opt-in Dream Machine virtual-view research adapter

[ruvnet]

Add an explicit, disabled-by-default RuView integration with the Dream Machine virtual-view research broker. It accepts calibrated virtual-view.v1 room-ENU snapshots; raw RF estimates and LiDAR packet schemas are not camera-grade manipulation geometry and are rejected.

The adapter checks bounded plain JSON before reading markers or invoking the trusted broker. This prevents top-level and nested getters or proxy traps from executing during validation. Structural depth, node, array, object, key and string limits are enforced; geometry, provenance and signing validation remain the companion broker's responsibility. The injected broker is trusted executable code, not a sandboxed plugin.

Adapter tests now run in the blocking JavaScript CI job. The README pins the reviewed companion revision 5707c825b2c065de44abed02594e1abf5eab95ea, already merged in ruvnet/dream-machine#162, and documents reproduction and research limits.

Validation:

• MEASURED: 55 JavaScript tests passed under Node 24.12.0, including 11 adapter boundary tests. Focused reproducer: node --test integrations/virtual-view/adapter.test.mjs.
• MEASURED: The nested-proxy reproduction executes zero traps and never reaches the broker; getter, malformed-input, budget and disabled-by-default cases are covered.
• SYNTHETIC: A 256-object scene passed through the pinned real broker, rendered with authority: none, and its signed receipt replayed successfully. This validates the software integration, not hardware performance.
• Independent review and git diff --check passed. Updated-head CI must pass before merge.

This is a research adapter outside the Rust production perception pipeline. Conceptual rendering does not establish robot-task gains, camera-grade RF geometry, real drift detection or end-to-end deployment latency. No hardware trials, actuator authority, model calls, paid services, or automatic enablement are introduced.