docs: document vibe-check analyze CLI (v0.1.0)

[jflowers]

What Changed

Document the newly released vibe-check analyze CLI (v0.1.0) on the public
website. vibe-check v0.1.0 is the first user-facing release: a Go-native
analyze command that computes package-level Martin coupling metrics and emits
JSON.

Content To Add

• Install: go install github.com/zero-dot-force/vibe-check/cmd/vibe-check@v0.1.0
• Usage: vibe-check analyze [path] (defaults to .); JSON report to stdout.
• Flags:
  • --max-instability (float, [0.0, 1.0])
  • --max-distance (float, [0.0, 1.0])
  • --max-lcom (int, >= 1)
  • --no-circular-deps (bool)
  • --timeout (duration; no default)
  • --version
• Exit codes: 0 success, 1 threshold violation, 2 tool error.
• Output: JSON schemaVersion 1.1 with an optional extensions object
  (e.g. go.interfaceWidth, go.interfaceProximity); link to the schema at
  metrics/modulegraph.schema.json.
• Metrics explained: Afferent (Ca) and Efferent (Ce) coupling, Instability,
  Abstractness, Distance from the main sequence, LCOM4 cohesion, and circular
  dependency detection.

Source Of Truth

• README: https://github.com/zero-dot-force/vibe-check/blob/main/README.md
• CHANGELOG [0.1.0]: https://github.com/zero-dot-force/vibe-check/blob/main/CHANGELOG.md
• Repository: zero-dot-force/vibe-check

Why It Matters

The constitution's Website Documentation Sync obligation requires
user-facing behavior shipped in a release to be reflected on the public site.
This is vibe-check's first user-facing CLI release.

References

• Filed from zero-dot-force/vibe-check PR fix: replace 6 stale Hivemind references with Dewey #21 as a /uf.review-council
  pre-merge obligation (Curator persona).