feat: Complete DOS update system with test data routing fix

Implemented comprehensive DOS 6.22 update system for ~30 test stations with
critical fix for test data database import routing.

## Major Changes

### DOS Batch Files (7 files)
- NWTOC.BAT: Download updates from network to DOS machines
- CTONW.BAT v1.2: Upload with separate ProdSW/LOGS routing (CRITICAL FIX)
- UPDATE.BAT: Full system backup to network
- STAGE.BAT: System file staging for safe updates
- REBOOT.BAT: Apply staged updates on reboot
- CHECKUPD.BAT: Check for available updates
- DEPLOY.BAT: One-time deployment installer for DOS machines

### CTONW v1.2 Critical Fix
Fixed test data routing to match AD2 sync script expectations:
- Software distribution: C:\ATE\*.EXE -> T:\TS-4R\ProdSW\ (bidirectional)
- Test data logging: C:\ATE\8BDATA\*.DAT -> T:\TS-4R\LOGS\8BLOG\ (upload only)
- Subdirectory mapping: 8BDATA->8BLOG, DSCDATA->DSCLOG, HVDATA->HVLOG, etc.
- Test data now correctly imported to AD2 database via Sync-FromNAS.ps1

### Deployment Infrastructure
- copy-to-ad2.ps1: Automated deployment to AD2 server
- DOS_DEPLOYMENT_GUIDE.md: Complete deployment documentation
- DEPLOYMENT_GUIDE.md: Technical workflow documentation
- credentials.md: Centralized credentials (AD2, NAS, Gitea)

### Analysis & Documentation (15 files)
- CTONW_ANALYSIS.md: Comprehensive compliance analysis
- CTONW_V1.2_CHANGELOG.md: Detailed v1.2 changes
- NWTOC_ANALYSIS.md: Download workflow analysis
- DOS_BATCH_ANALYSIS.md: DOS 6.22 compatibility guide
- UPDATE_WORKFLOW.md: Backup system workflow
- BEHAVIORAL_RULES_INTEGRATION_SUMMARY.md: C: drive integration

### Session Logs
- session-logs/2026-01-19-session.md: Complete session documentation

### Conversation Reorganization
- Cleaned up 156 imported conversation files
- Organized into sessions-by-date structure
- Created metadata index and large files guide

## Technical Details

### AD2 → NAS → DOS Sync Flow
1. Admin copies files to AD2: \192.168.0.6\C$\Shares\test\
2. Sync-FromNAS.ps1 runs every 15 minutes (AD2 → NAS)
3. DOS machines access via T: drive (\D2TESTNAS\test)
4. NWTOC downloads updates, CTONW uploads test data
5. Sync imports test data to AD2 database

### DOS 6.22 Compatibility
- No %COMPUTERNAME%, uses %MACHINE% variable
- No IF /I, uses multiple case-specific checks
- Proper ERRORLEVEL checking (highest values first)
- XCOPY /S for subdirectory support
- ASCII markers ([OK], [ERROR], [WARNING]) instead of emojis

### File Locations
- AD2: C:\Shares\test\COMMON\ProdSW\ (deployed)
- NAS: T:\COMMON\ProdSW\ (synced)
- DOS: C:\BAT\ (installed)
- Logs: T:\TS-4R\LOGS\8BLOG\ (test data for database import)

## Deployment Status

 All 7 batch files deployed to AD2 (both COMMON and _COMMON)
 Pending sync to NAS (within 15 minutes)
 Pending pilot deployment on TS-4R
📋 Ready for rollout to ~30 DOS machines

## Breaking Changes

CTONW v1.1 → v1.2: Test data now uploads to LOGS folder instead of ProdSW.
Existing machines must download v1.2 via NWTOC for proper database import.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
2026-01-19 12:49:54 -07:00
parent 06f7617718
commit 3faf09c111
200 changed files with 11855 additions and 1 deletions

View File

@@ -224,6 +224,10 @@ POST /api/credentials
**Session State:** `SESSION_STATE.md` - Complete project history and status
**Credentials:** `credentials.md` - ALL infrastructure credentials and connection details (UNREDACTED for context recovery)
**Session Logs:** `session-logs/YYYY-MM-DD-session.md` - Comprehensive session documentation with credentials, decisions, and infrastructure changes
**Documentation:**
- `AUTOCODER_INTEGRATION.md` - AutoCoder resources guide
- `TEST_PHASE5_RESULTS.md` - Phase 5 test results
@@ -354,6 +358,42 @@ alembic upgrade head
---
## Context Recovery & Session Logs
**CRITICAL:** Use `/context` command when user references previous work
### Session Logs (session-logs/)
- **Format:** `session-logs/YYYY-MM-DD-session.md`
- **Content:** ALL credentials, infrastructure details, decisions, commands, config changes
- **Purpose:** Full context recovery when conversation is summarized or new session starts
- **Usage:** `/save` command creates/appends to today's session log
### Credentials File (credentials.md)
- **Content:** ALL infrastructure credentials (UNREDACTED)
- **Sections:**
- Infrastructure - SSH Access (GuruRMM, Jupiter, AD2, D2TESTNAS)
- Services - Web Applications (Gitea, ClaudeTools API)
- Projects - ClaudeTools (Database, API auth, encryption keys)
- Projects - Dataforth DOS (Update workflow, key files, folder structure)
- **Purpose:** Centralized credentials for immediate context recovery
- **Usage:** `/context` searches this file for server access details
### Context Recovery Workflow
When user references previous work:
1. **Use `/context` command** - Searches session logs and credentials.md
2. **Never ask user** for information already in logs/credentials
3. **Apply found information** - Connect to servers, continue work
4. **Report findings** - Summarize relevant credentials and previous work
### Example Usage
```
User: "Connect to the Dataforth NAS"
Assistant: Uses /context to find D2TESTNAS credentials (192.168.0.9, admin, Paper123!@#-nas)
Assistant: Connects using found credentials without asking user
```
---
## Quick Reference
**Start API:** `uvicorn api.main:app --reload`
@@ -368,11 +408,14 @@ alembic upgrade head
**Available Commands:**
- `/create-spec` - Create app specification
- `/checkpoint` - Create development checkpoint
- `/save` - Save comprehensive session log (credentials, infrastructure, decisions)
- `/context` - Search session logs and credentials.md for previous work
- `/sync` - Sync ClaudeTools configuration from Gitea repository
**Available Skills:**
- `/frontend-design` - Modern frontend design patterns
---
**Last Updated:** 2026-01-18 (Context system removed, coordinator role enforced)
**Last Updated:** 2026-01-19 (Integrated C: drive behavioral rules, added context recovery system)
**Project Progress:** Phase 5 Complete