Utix: Implement historical trend export for operational and financial metrics

[prissca]

Summary

Maintainers need exportable historical trends for operations, failures, volume, and financial or protocol metrics.

This issue is scoped to Utix, a ticketing and event access protocol. Contributors should account for the current stack and integration points: TypeScript, ticket issuance, transfer, redemption, event operations, fraud controls, and organizer dashboards.

Difficulty

High - 200 points

Scope

• Define trend metrics and aggregation windows.
• Add export endpoint or command with schema version.
• Protect private or sensitive dimensions from unauthorized export.

Acceptance criteria

• Exports include schema version and generation metadata.
• Aggregation matches source data fixtures.
• Tests cover date ranges, empty data, permission denial, and large result sets.

Technical notes

• Keep the implementation aligned with the existing repository architecture.
• Include automated tests, fixtures, or a clear validation command.
• Update contributor-facing documentation when behavior, setup, or API contracts change.
• Do not add labels; maintainers will assign labels manually.

Pull request expectations

• Explain design decisions and tradeoffs.
• Include relevant test output, screenshots, logs, or API examples.
• Call out any migration, configuration, or deployment steps.