Integration guide

Where the pieces run

A developer preview of the web workbench uses mock data, the packaged browser workbench uses HTTP, and the embedded desktop uses WebView2 messages. A mock or demo page is not a live connection to equipment.

An arbitrary static web server is not a Windows gateway and does not supply /api. There is no separately identified standalone Windows Gateway package. The Windows gateway function is the task service plus the desktop/pipe adapter and its permitted HTTP and MCP entry points; see Permissions, security and data for the local and remote access modes. The browser relay's gateway module is a different research component.

Tests and hardware boundaries

Software and fixture tests are separate from hardware and external-integration tests. The hardware and external-integration categories are excluded by default, and so are Windows-only and worker-process groups in a portable run. Excluded tests are not passes.

SDK probes and real-camera verification are not routine checks, and some probe modes can change acquisition settings. For any SDK acceptance session, agree the exact executable, mode, device, backup/baseline and output destination in advance. The snapshot exporter is a metadata summary, not a connectivity or acceptance test.

Do not run hardware test categories or probe modes against production equipment merely to try the software.

Before connecting other systems

Read Permissions, security and data for access modes and Deployment, backup and operations for release readiness. Treat results from one environment as belonging to that environment: a Browser Lab result, a Windows offline run and a camera job are different things, as described in Jobs and inspection results.