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>

clients/dataforth/PROJECT_STATE.md

@@ -0,0 +1,59 @@
+# Dataforth (Client) — Project State
+
+> READ THIS before starting work on this client.
+> 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:** ACTIVE
+**Last Activity:** 2026-04-14
+
+Client relationship record for Dataforth Corporation (legacy DOS hardware manufacturer). This directory tracks client-facing work. The actual DOS test pipeline development lives in `projects/dataforth-dos/` — see that project's `PROJECT_STATE.md` for full infrastructure, active work, and anti-patterns.
+
+---
+
+## Infrastructure / Access
+
+See `projects/dataforth-dos/CONTEXT.md` and `projects/dataforth-dos/PROJECT_STATE.md` for full infrastructure details.
+
+Key access: AD2 (192.168.0.6), AD1 (192.168.0.27), FortiClient VPN required.
+Credentials: `bash D:/vault/scripts/vault.sh get-field clients/dataforth/ad2.sops.yaml credentials.password | sed 's/\\//g'`
+
+Session manager was being developed for SAGE-SQL deployment — see `clients/dataforth/session-manager/`.
+
+---
+
+## Pending / Next Up
+
+- [ ] Deploy session manager to SAGE-SQL
+- [ ] Ongoing support as new product families require pipeline extensions
+
+---
+
+## Recent Changes
+
+| Date | By | Change | Status |
+|------|-----|--------|--------|
+| 2026-04-14 | Mike | Session log: follow-up work on datasheet pipeline | COMPLETE |
+| 2026-04-13 | Mike | Session log: pipeline verification | COMPLETE |
+| 2026-04-12 | Mike | SCMVAS/SCMHVAS pipeline deployed to production | DEPLOYED |
+
+---
+
+## How to Update
+
+**When starting:** Add your session to Active Session Locks.
+**When finishing:** Remove your lock row, add entries to Recent Changes, update Current State if needed.