sync: auto-sync from HOWARD-HOME at 2026-04-22 11:48:29

Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-04-22 11:48:29

.claude/messages/for-mike.md

@@ -4,6 +4,26 @@ Check this file at sync. Delete items after you've addressed them.
 
 ---
 
+## From Howard, 2026-04-22 — Per-user Syncro keys (attribution fix)
+
+I hit the issue that my Syncro comments/line items on ticket #32179 were getting logged as you (user_id 1735) because we share your API key. Fixed it with per-user tokens:
+
+- Generated my own Syncro API token (Custom, admin, indefinite) → `user_id 1750`
+- Added vault entry: `msp-tools/syncro-howard.sops.yaml`
+- Patched `.claude/commands/syncro.md` to pick the key from `identity.json`'s `user` field, falls back to the shared `msp-tools/syncro.sops.yaml` if no per-user file exists
+- Verified `/me` now returns Howard Enos on my machine
+
+**When you get a chance** (after Valleywide settles), do the same for yourself so the shared key can be retired:
+
+1. Syncro → Admin → API Tokens → New (integration or custom, full scopes)
+2. `cat > $VAULT_ROOT/msp-tools/syncro-mike.sops.yaml <<YAML ... YAML` (template in the patched syncro.md)
+3. `cd $VAULT_ROOT && sops --encrypt --in-place msp-tools/syncro-mike.sops.yaml`
+4. Commit + push vault. The skill will pick it up automatically on your next sync.
+
+After your key is in place we can delete `msp-tools/syncro.sops.yaml` (shared). Until then the skill warns on stderr when it falls back to the shared key.
+
+---
+
 ## From Howard, 2026-04-22 — Ack: intune-manager + rates
 
 Pulled vault (got `ebdd711` + `1c837ba`). intune-manager vault file loads fine now. Tried a token against grabblaw.com — returns `AADSTS700016` (app not consented in that tenant). Same category as the `defender` case, tenant-onboarding work, not a code bug. No action needed from you.