v0.10.0 — Understand the codebase, not just check it

New: codebase-comprehension features

Conformance checking tells you what's wrong. It doesn't help someone dropped
into an unfamiliar repo actually understand what's there. This release adds
that, fully language-agnostic — no framework- or ecosystem-specific parsing.

• ## Start here in archsteer docs/report — ranks core components
  by how much internal code depends on them, and separately lists likely
  entry points (real exported APIs, nothing internal depends on them).
• ## Component map — a real file-to-file Mermaid dependency graph,
  capped to the 25 most-connected components. The existing layer diagram
  only ever drew layer-to-layer arrows; this shows the actual edges, e.g.
  two different controllers sharing the same dependency.
• archsteer graph <path> — one component's direct dependencies and
  dependents. No archsteer init/declared intent required — same posture
  as archsteer xray, built for "I just cloned this and need to orient."
• MCP: current_architecture() now surfaces core components + entry
  points; new component_neighbors tool for an agent mid-task.

Validated against Spring PetClinic (Java) and Dreamhouse LWC (Apex/LWC) —
no change to conformance scoring, purely additive read-only surfaces.

Full Changelog: v0.9.1...v0.10.0