🧹 Pre-Release Cleanup & Validation - Blade Generation System

🧹 Pre-Release Cleanup Phase

🆕 Added February 2, 2026 — Production Packaging Checklist

Before any release candidate is packaged for deployment, the codebase must be scrubbed of development artifacts, dead code, and sensitive information. This is a mandatory gate that runs AFTER the Python OVM analysis passes.

🗑️ Step 1: Strip Orphaned Macros

Remove OVM files that are not called by any production macro chain. The Python dependency checker identifies these.

ORPHAN DETECTION WORKFLOW 1. Python script scans all .ovm files for 'call XXX' statements 2. Build directed graph of caller → callee relationships 3. Walk graph from known entry points (fxCreateBladeFromIntersect, etc.) 4. Any .ovm NOT reachable from an entry point = ORPHAN 5. Review list manually → delete or archive confirmed orphans

○ Run dependency analysis from all production entry points
○ Generate orphan report with last-modified dates
○ Manual review: confirm each orphan is truly unused
○ Move confirmed orphans to _archive/ (don't delete immediately)

📄 Step 2: Remove Development Artifacts

Strip files that exist only for development/documentation purposes and should not ship.

Category	Pattern	Action
HTML docs	`*.html` in `docs/`	Exclude from production package
Markdown notes	`.md`, `HANDOFF_.md`	Exclude from production package
Text notes	`*.txt` (non-config)	Exclude from production package
Test harnesses	`fxTest*.ovm` in `testing/`	Exclude from production package
Backup files	`#backups/`, `_backup_/`, `_baseline_/`	Delete entirely
Copy variants	Files with "copy" or "backup" in name	Delete after confirming original exists
Analysis scripts	`*.py` (dependency checkers, analyzers)	Move to `tools/` (internal only)

🔒 Step 3: IP Protection Scrub

Remove or redact information that could expose internal infrastructure, development process, or proprietary methods.

Target	Pattern to Find	Replacement
UNC paths	`\\servername\share\`	Remove or replace with relative paths
Usernames	Windows usernames in paths or comments	Remove
TODO/HACK/FIXME	Markers left during development	Resolve or remove
Debug print	`print 'DEBUG'`, verbose tracing	Remove or gate behind debugLevel
AI references	"Claude", "AI Assistant", "Anthropic"	Replace with company attribution
Internal IPs	`192.168.*`, NAS addresses	Remove

⚠️ AI Attribution

All file headers currently showing Created by: Claude AI Assistant must be changed to Created by: Camtek Software LLC or the appropriate author before release.

✅ Step 4: Final Verification

○ Run Python OVM analyzer on cleaned codebase (MUST still pass)
○ Run grep -r for all IP scrub patterns (zero hits required)
○ Verify all production entry points still function (smoke test)
○ Confirm CRLF line endings on all .ovm and .var files
○ Package release candidate with version stamp

📦 Deliverables

cleanup_checklist.md — Step-by-step pre-release checklist

ip_scrub.py — Automated IP pattern scanner

package_release.bat — Build script that excludes dev artifacts

🔢 Magic Number Detection

🆕 Added February 2, 2026 — Python Analyzer Extension

Extension to the existing Python OVM source analyzer. Flags hardcoded numeric literals that are unit-dependent or tolerance values not assigned to named constants. These "magic numbers" cause silent failures when switching between metric and imperial units.

🎯 Detection Targets

Category	Magic Number	What It Is	Named Constant
Unit conversion	`25.4`	mm per inch	`w_MM_PER_INCH`
Unit conversion	`0.03937`	inches per mm	`w_INCH_PER_MM`
Unit conversion	`0.0254`	meters per inch	`w_M_PER_INCH`
Tolerance	`0.001`	Common tolerance	`w_TOL_FINE`
Tolerance	`0.0001`	Fine tolerance	`w_TOL_ULTRA`
Tolerance	`0.01`	Coarse tolerance	`w_TOL_COARSE`
Angular	`3.14159`	Pi (or fragments)	`w_PI`
Comparison	`999999`	Large sentinel	`w_LARGE_VALUE`

🔍 Detection Algorithm

MAGIC NUMBER SCANNER LOGIC For each .ovm file: For each line (skip comments starting with '): 1. SKIP lines that ARE constant definitions: e.g. w_TOL_FINE = 0.001 ← this is FINE (it IS the definition) 2. FLAG lines that USE magic numbers in expressions: e.g. if w_distance < 0.001 ← BAD: should be w_TOL_FINE e.g. w_val = w_x * 25.4 ← BAD: should be w_MM_PER_INCH 3. FLAG lines that use raw numbers in SLD commands: e.g. sld cnv ... 0.001 ← BAD: tolerance should be named 4. IGNORE safe patterns: - Loop counters: for i = 1 to 10 - Array indices: w_array( 3 ) - VDM slot numbers: vdm add i_set 7 - Known constants: i_TRUE, i_FALSE, i_NOT_SET - Zero and one: 0, 1, -1 (universal)

📋 Output: Named Constants File

All magic numbers should be replaced with named constants defined in a central .var file:

'*** fxConstants.var — Unit-independent named constants '*** Include in any macro that uses tolerances or unit conversions w_MM_PER_INCH = 25.4 w_INCH_PER_MM = 0.03937007874 w_M_PER_INCH = 0.0254 w_PI = 3.14159265359 '*** Tolerances (metric, mm) w_TOL_ULTRA = 0.0001 w_TOL_FINE = 0.001 w_TOL_STANDARD = 0.01 w_TOL_COARSE = 0.1 '*** Tolerances (angular, degrees) w_TOL_ANGLE_FINE = 0.01 w_TOL_ANGLE_COARSE = 0.1 '*** Sentinel values w_LARGE_VALUE = 999999.0 w_SMALL_VALUE = -999999.0

○ Add magic number detection to ovm_analyzer.py
○ Create fxConstants.var with all named constants
○ Run scan on full codebase — generate report
○ Replace flagged occurrences with named constants
○ Add magic number check to pre-release validation gate

📦 Deliverables

ovm_analyzer.py — Extended with magic number detection module

fxConstants.var — Central named constants file

magic_number_report.html — Scan results with file:line references

🔬 Pre-Release Validation Process

🆕 Added January 8, 2026 - Mandatory Pre-Production Analysis

Before releasing production code for testing, ALL OVM macros must pass through the Python-based source code analysis system.

📊 Python OVM Source Interrogation

Automated analysis of OVM macro source files to detect common issues before production release.

PRE-RELEASE VALIDATION WORKFLOW ┌─────────────────────────────────────────────────────────┐ │ DEVELOPMENT COMPLETE │ │ ↓ │ │ Run Python OVM Analyzer │ │ ↓ │ │ ┌─────────────────────────────────────────────────┐ │ │ │ Checks Performed: │ │ │ │ • Variable declarations at top of macros │ │ │ │ • Local variables inside loops/conditionals │ │ │ │ • Extended ASCII characters (>127) │ │ │ │ • CRLF line endings │ │ │ │ • Undeclared variable usage │ │ │ │ • VDM open/close balance │ │ │ │ • Syntax pattern validation │ │ │ └─────────────────────────────────────────────────┘ │ │ ↓ │ │ PASS? ─── YES ──→ Release for Testing │ │ │ │ │ NO │ │ │ │ │ └──→ Fix Issues ──→ Re-analyze │ └─────────────────────────────────────────────────────────┘

✓ Python analyzer script created
✓ Variable declaration position checking
✓ Loop/conditional scope analysis
○ Integrate into release checklist
○ Add to CI/CD pipeline (future)
○ Generate HTML validation report

⚠️ MANDATORY GATE

No OVM code should be released for production testing without first passing the Python analysis. This catches common PEPS macro pitfalls that cause silent failures or hard-to-debug runtime errors.

📦 Deliverables

ovm_analyzer.py - Main analysis script

analyze_all_macros.bat - Batch runner for full codebase

validation_report.html - Generated analysis report