BEJ-103: admin trial event and result creation

[asku1990]

ref bej-103

Summary

Integration pull request for the staged BEJ-103 implementation of admin trial event and manual result creation.

Each implementation gate is developed and reviewed in its own branch and pull request targeting this integration branch. Approved gates are merged here, and this pull request will be merged into develop only after the complete BEJ-103 workflow is finished and validated.

Implemented gates

E1 — Event workspace

• Add a dedicated /admin/trials/[trialEventId] route.
• Reuse the existing event details and result management UI on a stable event URL.
• Add explicit loading, not-found, retry, navigation, and deletion states.
• Add an Open event page action from the trials master-detail view.
• Preserve existing event editing, result editing, PDF generation, and result deletion behavior.

E2 — Event creation and empty-event lifecycle

• Add full-page admin trial event creation.
• Persist a newly created event before any results exist.
• Open the created event in its dedicated workspace.
• Preserve an event when its final result is deleted.
• Allow explicit deletion only for an empty event.
• Return stable errors for missing, duplicate, and non-empty events.

R1 — Manual result backend foundation

• Add manual trial entry request and response contracts.
• Add an authenticated admin Server Action for manual trial entry creation.
• Add shared registration normalization and validation.
• Create TrialEntry, TrialEra, and TrialEraLisatieto rows atomically.
• Link results through DogRegistration when a matching dog exists while allowing unknown registrations to remain unlinked.
• Use canonical identity:
  • SKL:<sklKoeId>|REG:<canonicalRegistration>
• Add database-backed duplicate protection and stable conflict errors.
• Add MANUAL_ADMIN as a canonical trial source.
• Define authoritative reconciliation where a later Koiratietokanta import replaces manual business data while preserving technical identity.
• Store trial event dates using PostgreSQL DATE semantics and serialize them as timezone-free YYYY-MM-DD values.

Remaining gate

R2 — Manual result UI and workflow

R2 will add the full-page result creation form and connect it to the approved R1 backend contract, including:

• registration entry;
• result, era, judge, note, and lisätieto sections;
• localized validation and stable error mappings;
• Save and add another and Save and finish workflows;
• dirty-form navigation protection;
• query invalidation and navigation back to the event workspace;
• the user-visible changelog entry for manual result creation.

Migration note

This branch updates existing Prisma migration files to reflect the intended final schema, including the trial source enum and PostgreSQL DATE storage for trial event dates.

There is currently no production data or deployed production migration history that must be preserved, so these migration edits are intentional and do not require corrective forward migrations.

Validation

The staged implementation includes focused coverage for:

• workspace routing and event loading states;
• event creation and empty-event deletion rules;
• authorization and stable Server Action errors;
• canonical registration handling;
• manual result input validation;
• atomic persistence and duplicate-race handling;
• manual-to-Koiratietokanta reconciliation;
• date-only conversion and trial search behavior.

Each gate must pass lint, typecheck, tests, coverage checks, and review before being merged into this integration branch.

Checklist

• E1 event workspace merged.
• E2 event creation and empty-event lifecycle merged.
• R1 manual result backend foundation merged.
• R2 manual result UI and workflow completed.
• Final integration review completed.
• Ready to merge into develop.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
beagle-db-v2	Ignored	Preview	Aug 4, 2026 5:14pm