syncro: record that the public API has NO remote device-control/exec endpoint (GUI-only; execution goes through GuruRMM)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

.claude/standards/syncro/test-findings.md

@@ -5,6 +5,17 @@ Verified behaviors/gotchas discovered while testing `/syncro` against the live t
 Each entry is a rule the skill must not re-learn. Critical ones are also folded into
 `syncro.md` (operating manual) and `api-reference.md` (breadth reference).
 
+## 2026-07-10 — Syncro API has NO remote device-control endpoint
+
+**You cannot run commands / control an endpoint through the Syncro public API.** Searched all
+116 paths for `script|command|execute|run|reboot|remote|action|task|shutdown|terminal` — none
+exist. Syncro's live device control (Run Script, Reboot, Live Terminal, background tools) is
+**GUI-only**. The `script.execute` token scope governs Syncro's *internal* scripting library
+(GUI/policy/automated-remediation triggered), NOT an on-demand API command runner. For an
+enrolled asset the API gives **read + manage only** (detail, patches, installed_applications,
+rmm_alerts, rename/serial/policy-folder move) — no execution. **Execution goes through GuruRMM
+(`/rmm`), not `/syncro`.** Do NOT probe guessed exec endpoints (junk-record risk).
+
 ## 2026-07-10 — Phase 2 (deploy-agent + asset/RMM on a REAL device)
 
 **`deploy-agent` VERIFIED end-to-end on RMM-TEST-MACHINE.** Read the vaulted Howard Test MSI URL