chore: add GuruRMM inter-session coordination system + PROJECT_STATE hook

- CONTEXT.md: static reference (infra, build pipeline, arch decisions, anti-patterns)
- PROJECT_STATE.md: live inter-session state tracker (locks, changelog, pending)
- CLAUDE.md: auto-read PROJECT_STATE.md alongside CONTEXT.md on GuruRMM context load
- Session log 2026-04-20: enrollment Option 3, installer Option B, no-TOML prohibition
- installer/gururmm-agent.wxs + README.txt committed in submodule

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

.claude/CLAUDE.md

@@ -137,7 +137,8 @@ If user mentions **GuruRMM**, **Dataforth**, **tunnel**, **VASLOG**, **AD2**, **
    - GuruRMM keywords → `projects/msp-tools/guru-rmm/CONTEXT.md`
    - Dataforth keywords → `projects/dataforth-dos/CONTEXT.md`
    - General → `CONTEXT.md` (root)
-2. Read ENTIRE file (infrastructure, current state, anti-patterns)
+2. **If a `PROJECT_STATE.md` exists alongside the CONTEXT.md, read it immediately after.** This file tracks live inter-session state: active locks (what other Claude instances are touching), architecture decisions that are locked, recent changes since the last session, and pending work. Check it for blocking conflicts before starting any task.
+3. Read ENTIRE file (infrastructure, current state, anti-patterns)
 3. Note recent session logs mentioned in CONTEXT.md
 4. THEN respond with full context