Current verification scope
Verified on 2026-10-18 using JavaScript 7.2.0.
| Target | Result |
|---|---|
| React, Svelte, Vanilla, CDN, WebRTC | Five production builds passed |
| Four chat apps | Each passed two-client bidirectional messaging and reconnect tests |
| WebRTC | Five local browser integration tests passed |
| Documentation JS examples | Korean/English server, client, direct-topic, and subscription checks |
| Workbench app | Three protocol tests, build, and one UI test passed |
| Arduino upload and physical control | Not tested in this pass |
| Real capture devices, Safari/iOS, different internet networks, TURN | Not tested in this pass |
Chat tests used local IOSignal servers. WebRTC used Chrome on one computer with simulated capture devices. These results do not establish public-service availability or physical-board operation.
Physical-device checklist
- Check installed Arduino library/core versions and the sketch's GPIO assignments.
- Compile, upload, and confirm the real device's ready state and CID.
- Match server, tag, and home-channel group between controller and board.
- Send a command and verify both the physical output and reported state.
- Check retained state and initial outputs after reconnecting and restarting power.
Use troubleshooting and connection environments. TX or a self-echo alone is not confirmation of device execution.