# Routine Sync — GURU-KALI

## User
- **User:** Mike Swanson (mike)
- **Machine:** GURU-KALI
- **Role:** admin

## Session Summary

Routine state-refresh session on GURU-KALI. The UserPromptSubmit hook surfaced one broadcast coord message from GURU-5070 (sent 2026-05-29T19:19:19) announcing that `.claude/scripts/post-bot-alert.sh` now routes RMM/Dev prefixes (`[RMM]`, `[DEPLOY]`, `[DEV]`, `[BUILD]`, `[GURURMM]`, `[SMARTBADGE-WATCH]`) to a new private `#dev-alerts` Slack channel while Syncro/general alerts continue to `#bot-alerts`. The broadcast's only action item was to run `/sync` to pull the update — no call-site changes required since routing is prefix-based.

The pull brought in 91 commits — most of them GuruConnect submodule advances from GURU-5070 covering the SPEC-003 through SPEC-009 sweep (machine inventory, stable identity + session lifecycle, machines list view, universal search, installer builder, valuable error messages, feature-rich documented API), the v2 dashboard pass 1 with Sessions / Support Codes / Users views and SPA serving wiring, plus a NULL-tags fix and a roadmap v2 re-baseline. GuruRMM submodule advanced through SPEC-018 (valuable error messages), SPEC-019 (feature-rich documented API), and SPEC-020 (CI/CD migration spec with a Phase 0 docs-only build guard recorded in memory). Bulk cleanup deleted 14 `temp/vwp_*` Vassallo-Wholesale-Plumbing investigation artifacts (~898k lines).

Wiki updates: 1 new client article (barbaragrygutis), 3 modified (clients/birth-biologic, systems/pluto, wiki/index). Two `.claude/commands/*.md` files refreshed into `~/.claude/commands/` automatically by `sync.sh` phase 5b: `gc-feature-request.md` and `rmm.md`. Two new memory entries landed: `memory/feedback_rmm_identify_by_ip.md` and the RMM webhook docs-only build guard note.

Vault pulled 3 commits: NPM admin password reset (services/npm.sops.yaml), new Rednour Law Offices GuruRMM site Main enrollment key vaulted at `clients/rednour/gururmm-site-main.sops.yaml` (key `GREEN-FALCON-7214`), and a new Cascades Tucson Lois Lane entry at `clients/cascades-tucson/lois-lane.sops.yaml`. No substantive work performed beyond these state refreshes — no agents delegated, no code authored, no client engagement.

## Key Decisions

- Did not propagate the alert-routing broadcast as inter-session messages; the broadcast was directed to all sessions and the update was self-applying via the pull, so no further action needed beyond running `/sync`.
- Namespaced this log as `2026-05-31-mike-guru-kali-sync.md` to keep GURU-KALI-specific sync activity searchable separately from any GURU-5070 or HOWARD-HOME session log that may land today.
- No agents spawned. Session scope (sync + log) was below the delegation threshold.

## Configuration Changes

None authored locally. Sync delivered:
- `.claude/scripts/post-bot-alert.sh` — alert routing logic split (RMM/Dev → `#dev-alerts`, Syncro/general → `#bot-alerts`)
- `.claude/commands/gc-feature-request.md` — new (GuruConnect feature-request command)
- `.claude/commands/rmm.md` — updated
- `~/.claude/commands/gc-feature-request.md`, `~/.claude/commands/rmm.md` — refreshed by sync.sh phase 5b
- `.claude/memory/feedback_rmm_identify_by_ip.md` — new
- Memory entry: RMM webhook docs-only build guard (SPEC-020 Phase 0)
- Wiki: `wiki/clients/barbaragrygutis.md` (new), `wiki/clients/birth-biologic.md`, `wiki/systems/pluto.md`, `wiki/index.md`
- 14 `temp/vwp_*` files removed (BEC/breach investigation artifacts for Vassallo Wholesale Plumbing — work concluded earlier, artifacts cleaned up)
- Submodule pointers: `projects/msp-tools/guru-rmm` (SPEC-018/019/020) and `projects/msp-tools/guru-connect` (SPEC-003 through SPEC-009 + v2 dashboard pass 1)

## Credentials & Secrets

Two new vault entries pulled (not created in this session):
- `clients/rednour/gururmm-site-main.sops.yaml` — GuruRMM enrollment key **GREEN-FALCON-7214** for Rednour Law Offices Main site
- `clients/cascades-tucson/lois-lane.sops.yaml` — new Cascades Tucson endpoint entry (Lois Lane)
- `services/npm.sops.yaml` — NPM admin password reset (mike@) after UI/API lockout

Access via: `bash $CLAUDETOOLS_ROOT/.claude/scripts/vault.sh get <path>`

## Infrastructure & Servers

None touched in this session.

Alert routing change (informational, applies fleet-wide once pulled):
- Slack `#dev-alerts` (private, Howard + Mike) — receives `[RMM]`, `[DEPLOY]`, `[DEV]`, `[BUILD]`, `[GURURMM]`, `[SMARTBADGE-WATCH]` prefixed alerts
- Slack `#bot-alerts` (existing) — receives Syncro and general prefixed alerts
- Routing logic: prefix-based in `.claude/scripts/post-bot-alert.sh`; existing call sites auto-route, no changes needed

## Commands & Outputs

```
bash .claude/scripts/sync.sh
# Pulled 91 commits (Mike: 73, Howard: 18)
# Vault: pulled 3 commits (Mike: 2, Howard: 1)
# Auto-commit dropped during rebase (submodule pointer patch already upstream)
# Global commands: 2 updated (gc-feature-request.md, rmm.md)
# Final HEAD: ec95e8e
```

Coord message check (post-sync):
```
curl -s "http://172.16.3.30:8001/api/coord/messages?to_session=GURU-KALI/claude-main&unread_only=true"
# {"total":0,"skip":0,"limit":100,"messages":[]}
```

The UserPromptSubmit hook auto-marks broadcasts read when it injects them into context, so no manual PUT to `/api/coord/messages/<id>/read` was needed.

## Pending / Incomplete Tasks

None opened or carried forward. No agent work delegated, no follow-ups generated.

## Reference Information

- HEAD at sync end: `ec95e8e` chore: bump guru-connect submodule (Tasks 3-5 review fixes)
- Pulled-commit authors: Mike Swanson (73), Howard Enos (18); span ~6 hours of mostly GURU-5070 activity
- Wiki summary: 1 added, 3 modified, 0 deleted
- Vault HEAD advanced: `f68d6e8..5dbb76c`
- Coord API base: `http://172.16.3.30:8001/api/coord`
- Broadcast message origin: `GURU-5070/claude-main` at `2026-05-29T19:19:19`
- Alert routing script: `.claude/scripts/post-bot-alert.sh`
- New GuruConnect SPECs pulled: SPEC-003 through SPEC-009 (machine inventory → feature-rich documented API)
- New GuruRMM SPECs pulled: SPEC-018, SPEC-019, SPEC-020
