Bufdir Report Generation

All four partner organizations receive Bufdir funding and currently spend significant manual effort on compliance reporting. The source doc quotes the shared goal as "trykk på én knapp og få ut det Bufdir trenger." Reducing this to a single action removes a major operational burden, directly justifying the platform's cost for every signed organization. Norse Digital Products has committed to initiating dialogue with Bufdir on behalf of all organizations to negotiate a simplified reporting format, amplifying the value of this feature across the entire customer base. Failure to deliver this by Fase 2 risks organizations retaining legacy reporting workflows and reducing platform stickiness.

Build a dedicated report builder service on the Next.js backend that queries the activities, organizations, and user tables with a reporting-period filter. The output schema must match Bufdir's required field mapping - this requires early engagement with Bufdir (noted as an action item for Daniel in the source doc). Implement a snapshot table (bufdir_report_snapshots) to allow re-running historical reports without data drift. Norse Test Organization records must be excluded via an is_test_organization flag on the organizations table. Provide a preview page with a read-only structured view before the final export action. Apply row-level tenant isolation throughout.