Resolve compiler, runtime, and test gaps

[MettaMazza]

Summary

• enforce identical type, ownership, safety, and optimization passes across check-only, C, LLVM, and native compilation paths
• add binary-safe raw socket sends, restore WebSocket linkage, and cover embedded-NUL payloads
• modernize installation, compiler selection, self-hosting fixpoint verification, editor grammar, CI gates, and documentation
• activate the forensic suite and replace exit-only or nondeterministic tests with stable assertions and expected outputs

Root causes

Several secondary compiler paths bypassed validation performed by normal C generation. The WebSocket module referenced a runtime function that was never implemented. Installer and documentation assumptions had also drifted from the modular self-hosted compiler and current test inventory.

Impact

Native and check-only modes now preserve the language's safety guarantees. WebSocket framing can send binary data without strlen truncation. CI exercises 84 reference cases, 55 self-hosted runnable cases, 12 rejection cases, 43 differential cases, and dedicated native/check gates.

Validation

• cargo build --release
• cargo test --release — 49/49
• ./run_tests.sh — 84/84
• tests/run_epc_parity.sh — 55/55 runnable, 12/12 rejected
• tests/run_differential.sh — 43/43
• native, check-only, stdlib, and key-input gates
• three-stage byte-identical self-host fixpoint
• clang-only bootstrap freshness and parity verification
• shell syntax, JSON parsing, and git diff --check