feat(reporting): Implement backend PDF/HTML/CSV report generation and…

[Rafiaminhaj]

… PIL charts

Description

Related Issues

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

Checklist

• My code follows the code style of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.

[Rafiaminhaj]

"Hi @utksh1, as requested, I have split the report exporter feature into three focused PRs:

#986 - Security dependency audit exceptions ( Vite/esbuild audit exceptions)
#984 - Backend report generation & PIL charts
#985 - Frontend UI export controls & print CSS
Since the CI runs the full suite (including npm audit) on all pull requests, please merge the security exceptions configuration (#986) first. Once merged, I will update the other two branches with the base main branch, which will make the frontend-checks pass successfully on them as well. Thank you!"

[utksh1]

This reporting rewrite is too broad to merge in one PR. It changes backend report generation substantially, adds external Google Fonts links in generated reports, mixes backend report output with frontend-style interactive UI concepts, and frontend-checks are failing. Please split this into smaller PRs with tests for each output format and avoid external network dependencies in generated reports.

[utksh1]

Still blocked. This remains a large backend reporting rewrite with chart generation, remediation-roadmap heuristics, and broad HTML/CSS changes in one PR. Please split this into smaller reviewed pieces with focused tests for each output format and avoid landing a large report generator rewrite as a single broad change.

[utksh1]

Closing as superseded by the split reporting work that has now landed via #1026. Please continue any remaining roadmap/report UI work in the narrower follow-up PR rather than this older broad branch.