refactor: unify health/metrics/security registration via registerScanCommand

[Arthur742Ramos]

Summary

The three deterministic scan commands — bootcamp health, bootcamp metrics, bootcamp security — had grown into three ~28-line copy-pasted Commander registrations plus three byte-identical option interfaces, differing only in the command name, description, a few help strings, and the runner function.

This PR extracts a single registerScanCommand(...) helper:

registerScanCommand({
  name: "security",
  description: "...",
  checkHelp: "...",
  minScoreHelp: "...",
  jsonHelp: "...",
  run: runSecurityCommand,
});

The helper owns the shared flag surface (--branch, --check, --min-score, --json, --max-files, --keep-temp, --verbose) and the identical option plumbing — including the raw-argv fallback for the -b/-m flags that collide with the root command. The three *ActionOptions interfaces collapse into one ScanActionOptions.

Adding a future scan command is now a ~9-line config object instead of a 28-line copy-paste, and the three existing commands can no longer drift out of sync.

Behavior-preserving

Command names, descriptions, --help output, and option parsing are all unchanged. This is a pure internal refactor.

Verification

• cli-option-routing unit test ✓
• health / metrics / security command unit suites (30 tests) ✓
• health / metrics / security E2E suites (11 tests, real CLI: --json, --check gates, --max-files routing, --branch) ✓
• --help output for all three commands manually confirmed identical
• Full suite green; typecheck + lint + build clean
• Net −15 lines, and far less duplication

🤖 Generated with Claude Code