sync: auto-sync from HOWARD-HOME at 2026-07-07 20:31:16

Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-07-07 20:31:16

.claude/commands/syncro.md

@@ -613,6 +613,27 @@ COMMENT_ID=$(echo "$COMMENT_RESP" | jq -r '.comment.id')
 - Do NOT wrap the payload in `{"comment": {...}}` — returns 422.
 - **If `COMMENT_ID` is null:** GET `/tickets/{id}` and check `.ticket.comments[]` by subject before doing anything else. Comments cannot be deleted via API — duplicates require manual GUI removal.
 
+#### Customer Assets (retire / archive — API GAP)
+
+**Retiring a device in Syncro = "Archive" (UI ONLY — no REST API).** Verified against
+Syncro's own docs 2026-07-08 (`docs.syncrosecure.com/assets-rmm/archive-assets`): archiving
+is done in the web UI only — asset Details page → **Actions → Archive**, or bulk via the
+Assets table checkboxes → **Bulk Actions → Archive**. There is **no** archive endpoint and
+**no** `archived` field on `PUT /customer_assets/{id}`. Do NOT try to archive via API, and
+do NOT substitute `DELETE /customer_assets/{id}` — delete is destructive/irreversible and
+loses history + breaks ticket linkages (Archive keeps the asset visible on its tickets/alerts).
+
+- **To retire assets: hand the user the asset list + the Bulk-Actions-→-Archive steps.** We
+  cannot do it for them via API.
+- Asset READS are fine: `GET /customer_assets?customer_id=N[&query=<name>]` (list, 100/page,
+  `.assets[]`) and `GET /customer_assets/{id}` (detail; `.asset` — RMM data lives under
+  `.asset.properties.kabuto_information`). `updated_at` is NOT a reliable "last online" (bulk
+  account touches move it) — use the ScreenConnect `GuestInfoUpdateTime` or kabuto data for
+  real last-seen.
+- **[RESEARCH]** Re-check if Syncro ships an archive API (watch release notes). If/when it
+  does, wire it in here and add `--confirm` gating. Until then this is a "cannot be performed
+  via skill" function. (First hit: IMC retirement pass 2026-07-08.)
+
 #### Customers
 
 ```bash