sync: auto-sync from Mikes-MacBook-Air.local at 2026-06-01 20:06:30

Author: Mike Swanson
Machine: Mikes-MacBook-Air.local
Timestamp: 2026-06-01 20:06:30

session-logs/2026-06-01-mike-lonestar-sophos-coordination.md

@@ -77,3 +77,68 @@ curl -X POST http://172.16.3.30:8001/api/coord/messages ...
 - Lonestar wiki: `wiki/clients/lonestar-electrical.md`
 - Sync commits: incoming c893d3e..581906a (14 commits), outgoing ba4e70a, 581906a
 - Birth Biologic Datto SmartBadge reference (unrelated): 2026-05-28 session, KSTEENBB2025, dual Workplace install fix
+
+---
+
+## Update: 20:05 MST — Vault Sync + Roadmap Implementation Workflow Directive
+
+### User
+- **User:** Mike Swanson (mike)
+- **Machine:** Mikes-MacBook-Air.local
+- **Role:** admin
+
+### Session Summary
+
+The user requested a vault repo sync, which was executed successfully. The vault repo was clean with no local changes, no incoming commits, and already up-to-date at HEAD `f44db79` (Google Workspace service account key storage).
+
+The user then requested adding a directive to the GuruRMM roadmap: before implementing any roadmap item, interview the user to flesh out additional details beyond the existing spec (edge cases, UI/UX specifics, error handling, integration points, performance, testing, constraints). A new "Implementation Workflow" section was added to `docs/FEATURE_ROADMAP.md` immediately after the Legend and before the first feature section. The directive specifies a 4-step workflow: read existing spec, interview user for details, update spec, proceed with implementation.
+
+The changes were committed to the GuruRMM submodule (`5a274d5`), pushed to Gitea, then the parent repo submodule pointer was updated (`4d0e9bc`) and pushed. Both pushes required the GIT_ASKPASS workaround due to special characters in the vault-stored Gitea password.
+
+### Key Decisions
+
+- Placed the "Implementation Workflow" section immediately after the Legend (before any feature content) so it's visible upfront when opening the roadmap file. This placement makes it clear the directive applies to all features below.
+- Used a 4-step numbered workflow (read spec, interview, update spec, implement) rather than prose to make it scannable and actionable.
+- Included specific examples of what to clarify during the interview (edge cases, UI/UX, error handling, integration, performance, testing, constraints) so the interview step is concrete, not vague.
+- Committed the roadmap change directly to GuruRMM main via detached HEAD push rather than creating a PR - this is a documentation-only change with no code impact.
+
+### Configuration Changes
+
+- Modified: `projects/msp-tools/guru-rmm/docs/FEATURE_ROADMAP.md` (+20 lines, new "Implementation Workflow" section)
+- GuruRMM submodule: committed `5a274d5`, pushed to main
+- Parent repo: submodule pointer bump `4d0e9bc`, pushed to main
+
+### Commands & Outputs
+
+```bash
+# Vault sync - clean, no changes
+cd /Users/azcomputerguru/vault
+git status --short  # (empty)
+git fetch origin    # No incoming changes
+git push origin main  # Everything up-to-date
+# HEAD: f44db79
+
+# GuruRMM roadmap edit + commit
+cd projects/msp-tools/guru-rmm
+git commit -m "docs(roadmap): add implementation workflow directive"
+# Commit: 5a274d5
+
+# Push submodule (with GIT_ASKPASS)
+git push origin HEAD:main
+# Output: a8d336a..5a274d5  HEAD -> main
+
+# Parent repo submodule pointer bump
+cd /Users/azcomputerguru/ClaudeTools
+git commit -m "chore: bump guru-rmm submodule (roadmap workflow directive)"
+# Commit: 4d0e9bc
+git push origin main
+# Output: bd89c6b..4d0e9bc  main -> main
+```
+
+### Reference Information
+
+- GuruRMM commit: `5a274d5` - docs(roadmap): add implementation workflow directive
+- Parent commit: `4d0e9bc` - chore: bump guru-rmm submodule (roadmap workflow directive)
+- Vault HEAD: `f44db79` - secrets: store acg-msp-access Google Workspace SA key inline
+- Roadmap file: `projects/msp-tools/guru-rmm/docs/FEATURE_ROADMAP.md`
+- Push sequence: GuruRMM main (a8d336a..5a274d5), parent main (bd89c6b..4d0e9bc)