Mike Swanson
551b0c860f
Deployed file is C:\Shares\testdatadb\templates\datasheet-exact.js; this
reconciles the repo copy + adds dsca-templates.json (STAGE 1 output).
What changed in generateExactDatasheet (DSCA family only; 5B/8B/7B/DSCT/SCMVAS
paths byte-unchanged):
- Load dsca-templates.json once at module top (126 per-model layouts).
- DSCA Final-Test now renders names + specs from the staged template rows, not
the single hardcoded DATA_LINES['DSCA'] + buildTSpecs DSCA branch.
- Value-bearing raw_data STATUS groups map positionally onto the spec-bearing
template rows; empty-spec rows (240VAC Withstand / Hi-Pot) render blank+PASS.
Removed the duplicate hardcoded 240VAC/Hi-Pot footer for DSCA (now rows).
- ACCURACY header uses the template accOut ("Output (V)"/"Output (mA)") with '-'
rule separators instead of "Vout (V)" + '='.
- Header/columns match the staged originals (Measured Value*, 25/15/19/6 rule).
Two real bugs fixed (both are the handoff's "lines drop" / wrong-value defect):
- formatMeasuredExact reads the value from index 4 so negative signs survive
("PASS-4.24..." -> "-4", not "4"); also decimal-code N -> toFixed(N) exactly
(DSCA differs from 5B/8B where code 2 means 1 decimal).
- parseRawData no longer consumes the first DSCA STATUS group as a bare
step-response line when that line is absent (dropped 3 rows on e.g. DSCA39-01).
Safety: when value count != spec-row count the positional zip is ambiguous
(subtype measures load points the template omits, e.g. DSCA49 5mA pair), so the
cert is SKIPPED (null) and left for STAGE 3 per-subtype mapping rather than
emitting misaligned data.
Validation: DSCA38-05 (SN 180224-1) Final-Test block byte-identical to its
staged original. 92/126 templated models render cleanly; 7 ambiguous + 27
no-spec skip. Remaining ACCURACY-block spacing diffs are the deferred cosmetic
gap. NOT YET LIVE: testdatadb service not restarted, nothing re-pushed to
Hoffman (STAGE 3 gate).
Coverage gap to resolve before publish: only 126/357 DSCA models in the DB have
a staged template (56,074 certs, 70.1%); 231 models / 23,866 certs have none and
now render null — needs a STAGE 1 extension (more staged originals).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ClaudeTools Active Projects
Directory: D:\ClaudeTools\projects\
Purpose: Active development projects and related conversation archives
Last Updated: 2026-01-17
Overview
This directory contains active projects being developed or maintained as part of the ClaudeTools ecosystem. Unlike the imported-conversations/ directory which serves as an archive, projects here are actively worked on and may include both source code and conversation history.
Current Projects
MSP Tools (94 files, 20.1 MB)
Moved From: D:\ClaudeTools\imported-conversations\msp-tools/
Move Date: 2026-01-17
Status: Active development
Managed Service Provider (MSP) tooling and infrastructure projects, including conversation history and development artifacts.
Structure
msp-tools/
├── guru-rmm/ # 54 files, 14 MB
│ └── [JSONL conversation files] # RMM system development history
└── guru-connect/ # 40 files, 6.1 MB
└── [JSONL conversation files] # MSP integration development history
guru-rmm (54 files, 14 MB)
Description: Remote Monitoring and Management (RMM) system development conversations
Source: C:\Users\MikeSwanson\.claude\projects\C--Users-MikeSwanson-claude-projects-gururmm-guru-rmm
Key Topics:
- RMM system architecture
- Monitoring solutions
- Agent deployment
- Infrastructure management
- MSP automation
Project Type: MSP Infrastructure
guru-connect (40 files, 6.1 MB)
Description: MSP connectivity and integration tooling conversations
Source: C:\Users\MikeSwanson\.claude\projects\C--Users-MikeSwanson-claude-projects-guru-connect
Key Topics:
- Integration patterns
- API connectivity
- Service orchestration
- Client management
- Cross-platform integration
Project Type: MSP Integration
File Format
All conversation files are in JSONL (JSON Lines) format:
- Extension:
.jsonl - Format: Each line is a valid JSON object
- Content: Individual conversation messages from Claude
- Encoding: UTF-8
- Can be processed line-by-line for analysis
Usage
Accessing Project Files
# List all projects
ls -lh D:\ClaudeTools\projects\
# Browse MSP tools conversations
ls -lh D:\ClaudeTools\projects\msp-tools\guru-rmm\
# Count conversation files
find D:\ClaudeTools\projects\ -name "*.jsonl" | wc -l
# Search for specific topics
grep -r "FastAPI" D:\ClaudeTools\projects\
Integration with ClaudeTools
These conversations can be:
- Analyzed and indexed into context recall system
- Used to extract reusable code snippets
- Mined for technical decisions and patterns
- Converted into knowledge base entries
- Referenced for similar future projects
Adding New Projects
When adding new active projects to this directory:
- Create a descriptive folder name (e.g.,
project-name/) - Include conversation history if available
- Update this README with project details
- Consider creating a project-specific README
- Tag appropriately for context recall
Related Documentation
- imported-conversations/INDEX.md - Archive of all imported conversations
- imported-conversations/IMPORT_MANIFEST.json - Detailed import metadata
- .claude/CLAUDE.md - Main ClaudeTools project documentation
- SESSION_STATE.md - Current project state and development history
Project Organization
Active Projects (this directory):
- Currently under development
- May include both code and conversation history
- Subject to frequent updates
- Integrated with ClaudeTools development
Archived Conversations (imported-conversations/):
- Historical reference only
- Read-only archive
- Organized by project type
- Preserved for knowledge extraction
Future Projects
This directory will grow as new projects are added. Potential additions:
- guru-backup - Backup and recovery tooling
- guru-dashboard - MSP management dashboard
- integration-tools - Third-party integration utilities
- automation-scripts - MSP automation workflows
Statistics
Current Totals:
- Projects: 1 (msp-tools)
- Conversation Files: 94 JSONL files
- Total Size: 20.1 MB
- Subcategories: 2 (guru-rmm, guru-connect)
Breakdown:
- guru-rmm: 54 files (57.4%), 14 MB (69.7%)
- guru-connect: 40 files (42.6%), 6.1 MB (30.3%)
Notes
- This directory was created on 2026-01-17
- First project (msp-tools) moved from imported-conversations archive
- All conversation files preserved with original timestamps
- Original source paths documented in IMPORT_MANIFEST.json
Maintained By: ClaudeTools Project
Location: D:\ClaudeTools\projects
Documentation Status: Active