chore: add PROJECT_STATE.md to all active projects and clients
Establishes inter-session coordination for 29 projects/clients: - Full lock/component format for active projects (dataforth-dos, radio-show, cascades-tucson, valleywide, instrumental-music-center, lens-auto-brokerage, msp-audit-scripts) - Light format for complete/stalled/planning (msp-pricing, pavon, wrightstown-*, gururmm-agent, community-forum, glaztech, etc.) - Onboarding stubs for recently added clients Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
25
projects/msp-tools/guru-connect/PROJECT_STATE.md
Normal file
25
projects/msp-tools/guru-connect/PROJECT_STATE.md
Normal file
@@ -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
|
||||
20
projects/msp-tools/howard-bootstrap/PROJECT_STATE.md
Normal file
20
projects/msp-tools/howard-bootstrap/PROJECT_STATE.md
Normal file
@@ -0,0 +1,20 @@
|
||||
# Howard Bootstrap — Project State
|
||||
|
||||
> Last updated: 2026-04-20
|
||||
|
||||
**Status:** STALLED
|
||||
**Last Activity:** 2026-04-16
|
||||
|
||||
Bootstrap/onboarding setup for Howard's workstation and ClaudeTools integration. The directory contains only a README.txt, keys.txt, and setup.bat — minimal scaffolding. No substantive development has occurred.
|
||||
|
||||
## What Was Done
|
||||
|
||||
- Basic directory structure created
|
||||
- setup.bat and keys.txt staged for Howard's initial machine setup
|
||||
- No session logs recorded
|
||||
|
||||
## If Resuming
|
||||
|
||||
- Check `README.txt` for any setup instructions captured
|
||||
- Determine what Howard still needs configured (vault access, git config, identity.json on his machine)
|
||||
- Follow ONBOARDING.md process in `.claude/` for any new-machine setup steps
|
||||
51
projects/msp-tools/msp-audit-scripts/PROJECT_STATE.md
Normal file
51
projects/msp-tools/msp-audit-scripts/PROJECT_STATE.md
Normal file
@@ -0,0 +1,51 @@
|
||||
# MSP Audit Scripts — Project State
|
||||
|
||||
> READ THIS before starting work on this project.
|
||||
> UPDATE THIS when you begin work (claim a lock) and when you finish (release lock + log changes).
|
||||
> Last updated: 2026-04-20
|
||||
|
||||
---
|
||||
|
||||
## Active Session Locks
|
||||
|
||||
| Session | Working On | Status | Started |
|
||||
|---------|-----------|--------|---------|
|
||||
| _(none active)_ | | | |
|
||||
|
||||
**How to claim a lock:** Add a row before starting work. Remove it when done. Locks older than 2 hours with no update are considered stale.
|
||||
|
||||
---
|
||||
|
||||
## Current State
|
||||
|
||||
**Status:** MAINTENANCE
|
||||
**Last Activity:** 2026-04-17 (estimated from directory contents)
|
||||
|
||||
PowerShell audit scripts for MSP client environments. Two scripts: `server_audit.ps1` (server-side audit) and `workstation_audit.ps1` (workstation audit). Used ad-hoc during client engagements. No active development — maintained as stable reference scripts.
|
||||
|
||||
---
|
||||
|
||||
## Infrastructure / Access
|
||||
|
||||
No dedicated infrastructure. Scripts run against client environments via SSH or remote PowerShell. Credentials come from vault per-client.
|
||||
|
||||
---
|
||||
|
||||
## Pending / Next Up
|
||||
|
||||
- [ ] No active items — scripts are stable
|
||||
|
||||
---
|
||||
|
||||
## Recent Changes
|
||||
|
||||
| Date | By | Change | Status |
|
||||
|------|-----|--------|--------|
|
||||
| (no logged changes) | | | |
|
||||
|
||||
---
|
||||
|
||||
## How to Update
|
||||
|
||||
**When starting:** Add your session to Active Session Locks.
|
||||
**When finishing:** Remove your lock row, add entries to Recent Changes.
|
||||
Reference in New Issue
Block a user