Define generic reporting and export primitives for RIMS

[fusion94]

Description

Many DamageLabs apps need exports, reports, dashboards, and inventory summaries. RIMS should own the reusable primitives for those capabilities without taking on domain-specific reporting logic.

This issue is for defining what generic reporting features belong in the framework core and how domain apps should extend them.

Acceptance Criteria

• Define generic export primitives such as CSV and JSON
• Define common report primitives such as inventory summaries and lifecycle/activity views
• Define shared dashboard building blocks
• Document how domain-specific reports should extend rather than pollute core
• Identify what reporting concerns belong in RIMS vs domain modules
• Produce a design note or architecture section for reporting