Utix: Build contributor-safe seed data for complex edge cases

[prissca]

Summary

Contributors need realistic seed data that covers complex edge cases without using private production data.

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

• Create deterministic seed fixtures for core workflows.
• Include edge cases such as failed settlement, revoked access, overdue workflow, and historical records.
• Document how to load and reset seed data.

Acceptance criteria

• Seed data loads locally without production credentials.
• Fixtures are deterministic and safe to commit.
• Tests or validation confirm seeded records are internally consistent.

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.