sync: auto-sync from GURU-BEAST-ROG at 2026-05-27 16:30:02

Author: Mike Swanson
Machine: GURU-BEAST-ROG
Timestamp: 2026-05-27 16:30:02

session-logs/2026-05-27-session.md

@@ -423,3 +423,72 @@ POST /api/v1/tickets/111265518/add_line_item
 - **Product 26184:** Labor - Emergency or After Hours Business | $262.50/hr
 - **Billing skill doc:** `.claude/commands/syncro-emergency-billing.md`
 - **Vault path accessed:** `msp-tools/syncro.sops.yaml`
+
+---
+
+## Update: 16:29 PT — Discord Bot: Emergency Test Ticket + Syncro Skill Fix
+
+## User
+- **User:** Mike Swanson (mike)
+- **Machine:** GURU-BEAST-ROG
+- **Role:** admin
+
+## Session Summary
+
+Mike requested a 1.5hr emergency ticket on the ACG internal test client (Arizona Computer Guru, customer_id 15353550) via the Discord bot, with fabricated description and solution. The ticket was created as a simulated after-hours RMM server outage scenario.
+
+During the billing preview, the bot incorrectly assumed the delivery channel was Remote without being told. Mike flagged this as a gap in the skill — "emergency" is a billing modifier, not a delivery channel, and Remote vs Onsite vs In-Shop cannot be guessed since they carry different price_retail values ($225 vs $262.50). Mike confirmed the correct channel was Onsite before billing proceeded.
+
+Before executing the ticket, Mike directed that the fix be baked into the syncro skill itself rather than relying on MEMORY.md. Two targeted edits were made to `.claude/commands/syncro.md`: one to the Hard Rules section and one to the Billing workflow Step 1 gather prompt. The change was committed and pushed so all machines pick it up via sync.
+
+After the skill fix was committed and synced, the ticket was created and fully billed: Syncro ticket #32336 created for Arizona Computer Guru, resolution comment posted, emergency onsite line item added (26184, 1.5 hrs @ $262.50 = $393.75), invoice generated, ticket marked Invoiced, and bot alert posted to #bot-alerts.
+
+## Key Decisions
+
+- **Delivery channel must be asked, not inferred for emergency billing:** The existing rule said "ask for labor type" but did not distinguish between billing type (emergency/regular) and delivery channel (remote/onsite/in-shop). Since these map to different price_retail values and Syncro line items, the channel must always be confirmed explicitly.
+- **Fix goes in the skill, not MEMORY.md:** Mike's explicit direction — MEMORY.md is per-machine ephemeral context; the skill file is the durable, cross-machine source of truth for billing rules.
+- **Two edit points in syncro.md:** The Hard Rules section (authoritative rules) and the Billing workflow Step 1 gather prompt (operational checklist) both needed updating to ensure the rule is encountered at the right point during execution.
+
+## Problems Encountered
+
+- **Bot guessed delivery channel:** Bot assumed Remote for an emergency ticket without being told. Caught by Mike before any API call was made. Corrected by asking, then updating the skill.
+
+## Configuration Changes
+
+- `.claude/commands/syncro.md` — updated Hard Rules billing rule and Billing workflow Step 1 to explicitly require delivery channel confirmation for emergency billing (commit 58d424e)
+
+## Credentials & Secrets
+
+None accessed beyond standard Syncro API key (Mike's key, already in skill).
+
+## Infrastructure & Servers
+
+- Syncro: computerguru.syncromsp.com
+- ACG internal test customer_id: 15353550
+
+## Commands & Outputs
+
+```
+# Ticket created
+Ticket ID: 111266587 | Number: 32336
+
+# Invoice
+Invoice ID: 1650438933 | Total: 393.75
+
+# Bot alert
+[OK] post-bot-alert: posted to #bot-alerts (message_id=1509337603525316671)
+
+# Commit
+58d424e  syncro: require delivery channel for emergency billing
+```
+
+## Pending / Incomplete Tasks
+
+None.
+
+## Reference Information
+
+- Syncro ticket #32336: https://computerguru.syncromsp.com/tickets/111266587
+- Invoice #1650438933: $393.75
+- Commit: 58d424e (main, pushed to Gitea)
+- syncro.md edited: `.claude/commands/syncro.md`