Exporting and printing
How the export stays identical to the screen.
The report exports by printing the page it is already on. There is one component, one set of figures and one methodology footer — so “the export matches the screen” is true by construction rather than by keeping two renderers in step.
What is dropped
Navigation, controls and shell chrome. The report is the deliverable; the interface around it is not.
What is kept
The dark treatment, deliberately. It is the agency's branded artifact and a light-mode variant would be the second renderer this approach exists to avoid. A reader who disables background graphics still gets a legible report, just without the surfaces.
Why not server-side PDF
It buys pagination control and costs a headless browser in the deployment, a second layout to maintain, and a new way for the exported figures to disagree with the screen. For this deliverable, print CSS is far less machinery for the same outcome.
See it against your own client list
A working demo runs your prompts, in your market, on live engines — not a sandbox with seeded data. Bring one client brand and three competitors.