chore: sync repository to current working state

Brings azcomputerguru/guru-connect up to the authoritative working copy that
had been maintained in the claudetools monorepo: Phase 1 security and
infrastructure (middleware, metrics, utils, token blacklist, deployment
scripts, security audits) plus the native-remote-control integration spec.
Preserves the repo .gitignore, .cargo, and server/static/downloads.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

PROJECT_STATE.md

@@ -0,0 +1,25 @@
+# GuruConnect — Project State
+
+> Last updated: 2026-04-20
+
+**Status:** STALLED
+**Last Activity:** 2026-01-17 (planning), last session log 2025-12-29
+
+GuruConnect is an MSP remote desktop solution (ScreenConnect replacement) built in Rust/Axum with a PostgreSQL backend. 24 conversation log files exist. Phase 1 (Security & Infrastructure) was scoped in January 2026 but never started — the project has been stalled since initial planning.
+
+## What Was Done
+
+- Full architecture designed: Rust agent (Windows), Rust relay server (Linux), WebSocket protocol, protobuf wire format
+- Security gap analysis completed: 5 critical issues identified (JWT hardcoded, rate limiting, SQL injection, agent validation, session takeover)
+- Phase 1-4 roadmap created (26-week timeline)
+- CLAUDE.md, MASTER_ACTION_PLAN.md, GAP_ANALYSIS.md, CHECKLIST_STATE.json all written
+- Server deploys to 172.16.3.30:3002, proxied via NPM to connect.azcomputerguru.com
+- Codebase: Rust workspace with agent/ and server/ crates, proto/ for protobuf definitions
+
+## If Resuming
+
+1. Read `PHASE1_SECURITY_INFRASTRUCTURE.md` — 5 critical security fixes still outstanding
+2. Read `CHECKLIST_STATE.json` for current progress (0/147 Phase 1 items completed as of last update)
+3. Start with SEC-1 (JWT secret hardcoded) — highest priority blocker
+4. Server is at 172.16.3.30:3002; static dashboard files in `server/static/`
+5. Build: `cargo build -p guruconnect --release` (agent, Windows); cross-compile for Linux server