reversa-docs-analyst

To generate visual documentation from code metrics, the analyst aggregates modules and dependency JSON into a consolidated metrics schema and renders Highcharts-based HTML pages with treemaps, complexity bars, and dependency Sankey diagrams.

Yes, you can create a project timeline from a chronicle markdown file. The analyst optionally converts chronicle.md event history into timeline.json and renders an interactive timeline.html when the file exists.

The best way to visualize software dependency relationships is by using the generated Highcharts dashboard, which includes a dependency Sankey visualization derived from the project's deps.json file.

You need modules.json and deps.json available or extracted to run this code metrics analysis. The analyst loads these files to derive quantitative metrics and requires reversa state and configuration to honor cache and extraction policies.

Dashboard visualization fails to load local data because the analyst renders Highcharts-based pages without local fetch. It writes outputs directly under the .reversa/documentation/ directory to ensure static rendering.