Audit and improve generated report formatting

[techmore]

Summary

Report output still needs a focused visual audit, but the runtime/report wiring work is now mostly in place on codex/runtime-contract-fixes.

What Is Already Done

• report generation now uses explicit web vs PDF stylesheet inputs
• the saved-scan PDF generation path lives in the shared reporting module
• report workflow boundaries are much cleaner than they were when this issue was filed

Remaining Work

This issue should focus on output quality, not pipeline architecture:

• typography hierarchy
• spacing and section rhythm
• table readability
• browser vs PDF parity checks
• print-safe layout validation on representative reports

Recommendation

Keep this issue only if you want it to represent the design/format audit itself.
Otherwise, consolidate it with #96 and #97 into a single report-rendering initiative and track implementation details under that umbrella.

[techmore]

Pushed an initial formatting fix in 1804802. PDF generation now prefers a browser-quality renderer first and the print stylesheet has been tightened for cleaner margins, no fixed nav, and more stable printable card/table output. Leaving this open pending user validation of the generated report quality.

[techmore]

Audit note after the codex/runtime-contract-fixes branch: a chunk of the report-pipeline correctness work that used to sit behind this issue is now resolved, including explicit web/PDF stylesheet routing and the saved-scan PDF regeneration flow living in the shared reporting path.

What remains here is mostly output quality and design parity rather than pipeline wiring.

Recommendation: consider consolidating this with #96 and #97 into a single report-rendering initiative, then break out only the remaining actionable work:

• visual parity goals
• dedicated print stylesheet strategy
• renderer-specific formatting fixes

[techmore]

Subsumed by #106.

The remaining work here is now better tracked as part of the combined report-rendering/parity initiative, since the pipeline wiring concerns have already been addressed on codex/runtime-contract-fixes and the open work overlaps directly with HTML/PDF parity and stylesheet strategy.