docs(session): 2026-05-27 — RMM Phase 2 deploy, Autotask integration, Tohono DoIT #32328

- Root log: GuruRMM Phase 2 authz/IDOR deployed (v0.3.31); Autotask creds verified + vaulted; /autotask scaffolded (kept local)
- Client log (new): Tohono O'odham DoIT — Starlink static IP / site-to-site research, ticket #32328
- Memory: Syncro is default PSA, Autotask opt-in (feedback_psa_default_syncro.md)

Note: .claude/commands/autotask.md intentionally left local/uncommitted per Mike.

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

.claude/memory/feedback_psa_default_syncro.md

@@ -0,0 +1,12 @@
+---
+name: feedback-psa-default-syncro
+description: Syncro is the default PSA for ticketing/billing/customers/scheduling; Autotask (/autotask) is opt-in, only on an explicit request
+metadata:
+  type: feedback
+---
+
+**Syncro is the default PSA.** All ticketing, billing, customers, and scheduling go through Syncro (`/syncro`) unless the user explicitly says to do something in Autotask. Only invoke `/autotask` on an explicit "in Autotask" / "autotask" request — never route generic ticket/billing/customer work to it by default.
+
+**Why:** ACG runs both PSAs, but Syncro is the primary day-to-day system. The Autotask integration exists (creds verified, `/autotask` skill built 2026-05-27) but is secondary. Mike confirmed: "Syncro is the default for ticketing and such; [Autotask] would only be called if there was a 'do a thing in autotask' request."
+
+**How to apply:** When a request mentions tickets/billing/customers/appointments without naming the system, assume Syncro and use `/syncro`. Reach for `/autotask` only when the user names Autotask explicitly. The `/autotask` skill is intentionally kept local/undistributed for now (not synced to other machines), reinforcing that it's opt-in. See [[feedback-syncro-timer-first]] for Syncro billing specifics.