View and Edit a Recently Submitted Registration

This is a high-complexity story with multiple distinct delivery components: an activity history list view, an edit form with pre-populated fields, conditional edit-window enforcement, a coordinator approval workflow path, and a dual-value audit trail. The dependency on story-quick-activity-registration-peer-mentor-001 means the base registration data model must be stable before this story begins. Cross-functional coordination is needed with coordinators, who must understand and accept the approval request flow for edits outside the 7-day window — this requires UAT with coordinator personas, not just peer mentors. The configurable edit window (default 7 days) needs a configuration management decision: where is this value stored and who can change it?

That dependency should be resolved before development begins. Testing scope is broad: happy path edits, boundary conditions at day 7, approval request triggering, audit trail integrity, and field lock enforcement for organisation and peer mentor ID. Plan for at least two sprint cycles and include a migration consideration if existing records need audit trail backfilling.

This story requires several interconnected system changes. The activity history list must query Supabase for the authenticated peer mentor's own registrations, ordered by created_at descending, and render them as tappable entries. Tapping a record opens an edit form pre-populated via a Supabase select by record ID; the organisation and peer_mentor_id fields must be rendered as read-only display elements, not editable inputs, to enforce the constraint. On save, the update payload should write changed fields plus an edited_at timestamp.

For the audit trail, consider storing the original values as a JSONB `edit_history` column appended on each update, or a separate audit table — confirm the approach with data schema owners before implementing. The edit window check compares the record's created_at against the current time using the configurable threshold (read from app config or a settings table). If outside the window, the save action must instead create a pending approval record and notify the coordinator (via existing notification infrastructure if available, or a new approvals table). Coordinator view must conditionally render both original and edited values from the audit trail.

Ensure Supabase RLS policies allow peer mentors to update only their own records and block direct writes to immutable fields.