CLI-11: Override discovery with --config

What it demonstrates

–config points validate at an explicit config file instead of auto-discovering one.

Builds on: CLI-08: Lean on auto-discovered config

How it’s done

A terminal session: the command as you’d run it, followed by the output it prints; trailing comments note the exit status.

# point validate at an explicit config file instead of auto-discovering one
markdown-contract validate ./decisions --config ci/strict.yaml
Scanned 1 file; 1 matched across 1 contract, 0 unmatched
  decisions: 1

No findings.
# ci/strict.yaml is a kind:config router; --config and --contract are mutually exclusive; exit status: 0

Surfaces exercised

• --config <file> override (.yaml/.yml/.js/.mjs)
• loadConfig explicit path
• mutually exclusive with --contract