Let people view their own form submission outside of an event

🤖 From Claude (opened on Mae's behalf):

Problem

A person can only view their own form submission when it came through an event (the slug/ticket → public registration confirmation flow). A standalone form submission (not tied to an event registration) has no path for the submitter to see what they submitted.

Proposed solution

• Send a confirmation email after a form submission that links the submitter to their own view of that submission.
• That view should share the answer-display partials already used by the event form-submission views (form_submissions/submission, shared/form_answer_value, section grouping) so the two stay in sync.
• It just needs a different route + access path (slug/token-based, scoped to the submitter) rather than the event-registration pathway.

Why it matters

Submitters currently have no record of, or receipt for, a standalone form submission — they can't confirm what they sent or refer back to it.

Notes

• Reuse the existing display partials; don't fork the presentation.
• Access should be capability-based (unguessable slug), mirroring how the event ticket exposes the registration confirmation.

Start by tracing the standalone form-submission flow and the existing event form-submission views, especially form_submissions/submission and shared/form_answer_value. Follow how event tickets expose registration confirmations, then identify the confirmation-email and route entry points. Done means a standalone submitter can follow an unguessable slug or token to view their submission using the shared answer partials.