azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: convert guru-connect to submodule; integrate ADR-008 + 2026-05-29 session log

Browse Source 
guru-connect is now tracked as a submodule (azcomputerguru/guru-connect @ e3e95f8);
its working state was published to the GC repo first, so no content is lost. guru-rmm
advanced to include ADR-008 (GC integration boundary) replayed on top of the team's
Integrations Center / discovery advances. Includes the native-remote-control spec
(now inside the GC submodule), the versionable-products memory, and the session log.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Mike Swanson
2026-05-29 06:36:54 -07:00
parent 1dd88edba3
commit a00247bc74
138 changed files with 129 additions and 33995 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.claude/memory/MEMORY.md
View File

@@ -70,6 +70,7 @@
- [Mac gururmm setup pending](project_mac_gururmm_setup_pending.md) — ACTION REQUIRED: run `bash scripts/install-hooks.sh` in gururmm repo on Mikes-MacBook-Air before any RMM work
## Project
- [Only RMM & GC are versionable products](project_versionable_products.md) — GuruRMM + GuruConnect are the only products with own repos/submodules; everything else stays in the claudetools monorepo. Split only for independent pipeline OR versioned external consumer.
- [Quantum GoDaddy M365 tenant](project_quantum_godaddy_m365_tenant.md) — quantumwms.com parked in a GoDaddy-provisioned M365 tenant (id ddf3d2c9-b76c-40d9-a216-9f11a1a26f97, netorg18235235.onmicrosoft.com); blocks Pax8 migration until GoDaddy removed. Managed = no DNS takeover; need GoDaddy/GA access.
- [Cascades Migration Plan](project-cascades-migration-plan.md) — Active multi-day migration. Plan file: `C:\Users\Howard\.claude\plans\wise-discovering-panda.md`. Syncro ticket: #110680053. Resume: "resume the Cascades migration plan".
- [GuruRMM Development Principles](gururmm-development-principles.md) - MANDATORY: every feature needs full stack (backend, API, UI, docs, scalability). Product must work without AI agents (AI features are enhancements). Documented in guru-rmm/docs/DESIGN.md.

23
.claude/memory/project_versionable_products.md Normal file
View File

@@ -0,0 +1,23 @@
---
name: project_versionable_products
description: Only GuruRMM and GuruConnect are versionable products (own repos/submodules); everything else stays in the claudetools monorepo
metadata:
type: project
---
GuruRMM (`azcomputerguru/gururmm`) and GuruConnect (`azcomputerguru/guru-connect`) are the
**only** versionable products. Each has its own Gitea repo + CI/CD + release cadence and is tracked
as a git **submodule** under `projects/msp-tools/` (guru-rmm, guru-connect). Confirmed by Mike 2026-05-29.
Everything else — the ClaudeTools API itself, quote-wizard, dataforth-dos, radio-show, msp-tools
scripts, `.claude/`, `wiki/`, `session-logs/` — stays **in the claudetools monorepo**. Do not split
them into their own repos.
**Why:** Separate repos are only justified by an independent release/deploy pipeline OR an external
consumer that integrates via a versioned contract (see RMM↔GC boundary, ADR-008). Every extra repo
multiplies submodule-sync burden — and an un-pushed vendored copy drifts (GC's repo was 4 months
stale until 2026-05-29 because edits stayed in the monorepo and were never pushed).
**How to apply:** When asked "should X be its own repo?", default to NO unless X ships/deploys on its
own pipeline or is consumed elsewhere through a versioned interface. For the two products, never edit
the submodule's files without committing + pushing inside the submodule. Relates to [[feedback_gururmm_builds]].