Implement JOVIAL & CMS-2 Legacy Defense Signatures

[squid-protocol]

Epic: #75
Target: gitgalaxy/standards/language_standards.py

Context & Strategic Value

Legacy military platforms (like the F-15 and the U.S. Navy Aegis Combat System) still rely on millions of lines of JOVIAL and CMS-2. Modern static analysis tools completely ignore these languages. By mapping their structural signatures, GitGalaxy provides instant architectural visibility into dead languages, bridging a massive generational knowledge gap for defense contractors.

Implementation Tasks

JOVIAL

• Add jovial to LANGUAGE_DEFINITIONS.
• Define Extensions: .jov, .cpool.
• Set lexical_family to standard_block (" or % for comments).
• Implement class_start signature: Target TABLE and ITEM declarations.
• Implement high_risk_execution signature: Target GOTO, FALLTHRU (Critical for tracking unstructured legacy flow).
• Implement memory_alloc signature: Target manual memory overlays (OVERLAY).

CMS-2

• Add cms2 to LANGUAGE_DEFINITIONS.
• Define Extensions: .cms2, .cms.
• Set lexical_family to standard_block (Uses COMMENT ... $ block markers).
• Implement globals signature: Target SYS-DD (System Data Design).
• Implement structural_boundaries signature: Target PROCEDURE, EXEC.

Validation

Ensure that legacy unstructured jumps (GOTO) correctly spike the high-risk execution telemetry vectors.