Wire CLI CI/CD Quality Gating and SQLite Compliance Vault

[squid-protocol]

Epic: #75
Target: galaxyscope.py (CLI Argument Parsing) & record_keeper.py

Context & Strategic Value

GitGalaxy already contains incredibly powerful database archiving (record_keeper.py) and delta tracking capabilities. However, these are currently internal capabilities. To be enterprise-ready, we need to expose these as CLI flags so DevOps engineers can use GitGalaxy to break builds in CI/CD pipelines and archive specific release candidates for compliance audits.

Implementation Tasks

• Add CLI flag --fail-on-risk (e.g., --fail-on-risk=80.0).
• Add CLI flag --fail-on-misra (e.g., --fail-on-misra=50.0).
• Update galaxyscope.py exit logic: If the final delta telemetry breaches either of these thresholds, trigger a native sys.exit(1) to fail the CI/CD job.
• Add CLI flag --compliance-vault.
• Update execution logic: Ensure the existing record_keeper.py SQLite generation is skipped during standard rapid runs, but engages fully when the --compliance-vault flag is present to generate a cold-storage database.

Validation

1. Create a test CI job that runs python galaxyscope.py --fail-on-misra=20.0 against a repository with high goto usage. Verify the script returns a non-zero exit code.
2. Run the engine with --compliance-vault and verify the gitgalaxy_vault.db SQLite file is cleanly generated with full table schemas.