[OpenSpec] insight-exports-and-custom-reports

[github-actions]

⚠️ OpenSpec-managed issue — this content is automatically synced
from the openspec/ directory. Manual edits will be overwritten on next sync.

Artifacts

• ✅ Metadata
• ✅ Proposal
• ✅ Specs
• ✅ Design
• ✅ Tasks
• 🔲 Plan
• 🔲 Review

Summary

Today a municipal information manager can export exactly one thing from a user page: the portfolio report CSV for one organisation. The Applications, Services and Contracts lists have no export, the ArchiMate export of your own organisation sits in admin settings, and nobody can define a report of their own. This change opts the catalogue list pages into the component library's Export menu, adds an export for the two faceted lists, puts the own-organisation ArchiMate export on the organisation page with an ownership check, and adds a custom reports page over OpenRegister's export profiles.

Specs

• 📄 catalogue-exports-and-reports

Tasks

• Implement
• Test (PHPUnit tests/Unit/Service/OrganisationScopeGuardTest.php and tests/Unit/Controller/SettingsControllerOrgExportTest.php)
• Implement
• Test (Playwright tests/e2e/spec-coverage/catalogue-exports.spec.ts)
• Implement
• Test (PHPUnit tests/Unit/Controller/CatalogExportControllerTest.php and tests/Unit/Service/CatalogExportServiceTest.php)
• Implement
• Test (vitest tests/vitest/catalogExportUrl.spec.js and Playwright tests/e2e/spec-coverage/catalogue-exports.spec.ts)
• Implement
• Test (PHPUnit tests/Unit/Settings/CatalogExportFlagsTest.php and Playwright tests/e2e/spec-coverage/catalogue-exports.spec.ts)
• Implement
• Test (vitest tests/vitest/customReports.spec.js and Playwright tests/e2e/spec-coverage/custom-reports.spec.ts)
• Implement
• Test (docs build and a manual read of the screenshots against the running app)

Design

See design.md for technical design details.

---

Synced from openspec/changes/insight-exports-and-custom-reports by OpenSpec workflow
App: stackiq