Dependencies analysis page, generated

[nathanacurtis]

Problem

specs analyze dependencies produces a report that answers which components depend on which, and the blast radius of changing one. The result lives in terminal output and a file on disk. Nothing in the tool the customer is already looking at shows it.

Scope

• A generated page under the Analyses section that renders the existing report file live.
• The report file stays the durable artifact — diffable, readable in CI, greppable by an agent with no browser. The page is a disposable view of it.
• Point-in-time class: regenerated wholesale, current truth, no history. Time-series presentation is out of scope and belongs to the separate umbrella gated by ADR B on Storybook with reports and foundations #574.

Blocked by #611

The reports section convention and mount point must exist first. Four analysis pages built ahead of it would each invent their own data contract, which is exactly the outcome the convention exists to prevent.

Acceptance criteria

• Page renders the current Dependencies analysis with no hand editing.
• It reads the report artifact rather than recomputing the analysis.
• A missing or stale report produces a clear empty state, not a broken page.
• It uses Reports section convention and mount point in Storybook #611's mount point, adding no new convention.

Case data

• Territory: cli
• Size: s
• Wave: 4 — last in the value order agreed on Storybook with reports and foundations #574