Utix: Implement stale authorization cleanup and renewal flow

[prissca]

Summary

Old authorizations, approvals, or delegated permissions should expire and be renewable through a safe, audited process.

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

• Identify authorizations that need expiry.
• Add cleanup job or report for stale authorizations.
• Create renewal path with audit events.

Acceptance criteria

• Expired authorizations no longer allow protected actions.
• Renewal requires authorized actor confirmation.
• Tests cover active, expired, cleaned, renewed, and revoked states.

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.