docs: Document Dataforth test database system and troubleshooting

Investigation and Documentation:
- Discovered and documented test database system on AD2 server
- Created comprehensive TEST_DATABASE_ARCHITECTURE.md with full system details
- Retrieved all key database files from AD2 (import.js, schema.sql, server configs)
- Documented data flow: DOS machines → NAS → AD2 → SQLite → Web interface
- Verified database health: 1,027,517 records, 1075 MB, dates back to 1990

Database System Architecture:
- SQLite database with Node.js/Express.js web server (port 3000)
- Automated import via Sync-FromNAS.ps1 (runs every 15 minutes)
- 8 log types supported: DSCLOG, 5BLOG, 7BLOG, 8BLOG, PWRLOG, SCTLOG, VASLOG, SHT
- FTS5 full-text search, comprehensive indexes for performance
- API endpoints: search, stats, export, datasheet generation

Troubleshooting Scripts Created:
- Database diagnostics: check-db-simple.ps1, test-db-directly.ps1
- Server status checks: check-node-running.ps1, check-db-server.ps1
- Performance analysis: check-db-performance.ps1, check-wal-files.ps1
- API testing: test-api-endpoint.ps1, test-query.js
- Import monitoring: check-new-records.ps1
- Database optimization attempts: api-js-optimized.js, api-js-fixed.js
- Deployment scripts: deploy-db-optimization.ps1, deploy-db-fix.ps1, restore-original.ps1

Key Findings:
- Database file healthy and queryable (verified with test-query.js)
- Node.js server not running (port 3000 closed) - root cause of web interface issues
- Database last updated 8 days ago (01/13/2026) - automated sync may be broken
- Attempted performance optimizations (WAL mode) incompatible with readonly connections
- Original api.js restored from backup after optimization conflicts

Retrieved Documentation:
- QUICKSTART-retrieved.md: Quick start guide for database server
- SESSION_NOTES-retrieved.md: Complete session notes from database creation
- Sync-FromNAS-retrieved.ps1: Full sync script with database import logic
- import-js-retrieved.js: Node.js import script (12,774 bytes)
- schema-retrieved.sql: SQLite schema with FTS5 triggers
- server-js-retrieved.js: Express.js server configuration
- api-js-retrieved.js: API routes and endpoints
- package-retrieved.json: Node.js dependencies

Action Items Identified:
1. Start Node.js server on AD2 to restore web interface functionality
2. Investigate why automated sync hasn't updated database in 8 days
3. Check Windows Task Scheduler for Sync-FromNAS.ps1 scheduled task
4. Run manual import to catch up on 8 days of test data if needed

Technical Details:
- Database path: C:\Shares\testdatadb\database\testdata.db
- Web interface: http://192.168.0.6:3000 (when running)
- Database size: 1075.14 MB (1,127,362,560 bytes)
- Total records: 1,027,517 (slight variance from original 1,030,940)
- Pass rate: 99.82% (1,029,046 passed, 1,888 failed)

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

test-api-endpoint.ps1

@@ -0,0 +1,47 @@
+# Test the API endpoint directly
+Write-Host "[OK] Testing API endpoints on AD2..." -ForegroundColor Green
+
+# Test 1: Stats endpoint
+Write-Host "`n[TEST 1] GET /api/stats" -ForegroundColor Cyan
+try {
+    $response = Invoke-WebRequest -Uri "http://192.168.0.6:3000/api/stats" -Method GET -UseBasicParsing -ErrorAction Stop
+    Write-Host "[OK] Status: $($response.StatusCode)" -ForegroundColor Green
+    Write-Host "[OK] Response:" -ForegroundColor Green
+    $response.Content | ConvertFrom-Json | ConvertTo-Json -Depth 5
+} catch {
+    Write-Host "[ERROR] Request failed: $($_.Exception.Message)" -ForegroundColor Red
+    Write-Host "[ERROR] Response: $($_.Exception.Response)" -ForegroundColor Red
+    if ($_.ErrorDetails.Message) {
+        Write-Host "[ERROR] Details: $($_.ErrorDetails.Message)" -ForegroundColor Red
+    }
+}
+
+# Test 2: Search endpoint (simple)
+Write-Host "`n[TEST 2] GET /api/search?limit=1" -ForegroundColor Cyan
+try {
+    $response = Invoke-WebRequest -Uri "http://192.168.0.6:3000/api/search?limit=1" -Method GET -UseBasicParsing -ErrorAction Stop
+    Write-Host "[OK] Status: $($response.StatusCode)" -ForegroundColor Green
+    Write-Host "[OK] Response:" -ForegroundColor Green
+    $response.Content | ConvertFrom-Json | ConvertTo-Json -Depth 5
+} catch {
+    Write-Host "[ERROR] Request failed: $($_.Exception.Message)" -ForegroundColor Red
+    if ($_.ErrorDetails.Message) {
+        Write-Host "[ERROR] Details: $($_.ErrorDetails.Message)" -ForegroundColor Red
+    }
+}
+
+# Test 3: Record by ID
+Write-Host "`n[TEST 3] GET /api/record/1" -ForegroundColor Cyan
+try {
+    $response = Invoke-WebRequest -Uri "http://192.168.0.6:3000/api/record/1" -Method GET -UseBasicParsing -ErrorAction Stop
+    Write-Host "[OK] Status: $($response.StatusCode)" -ForegroundColor Green
+    Write-Host "[OK] Response:" -ForegroundColor Green
+    $response.Content | ConvertFrom-Json | ConvertTo-Json -Depth 5
+} catch {
+    Write-Host "[ERROR] Request failed: $($_.Exception.Message)" -ForegroundColor Red
+    if ($_.ErrorDetails.Message) {
+        Write-Host "[ERROR] Details: $($_.ErrorDetails.Message)" -ForegroundColor Red
+    }
+}
+
+Write-Host "`n[OK] Done" -ForegroundColor Green