Feat/lui 143 145 enhance define ritual form

[luidgi-dev]

LUI-143: Confirmation toast when a ritual is created

Why

In the synthetic beta study (LUI-142, finding F1), all 3 participants tapped Create ritual, saw the sheet close, and could not tell whether the ritual had been saved. The save did work. What was missing was an acknowledgment right after the action.

What

• After a ritual is created, a toast appears: Ritual defined · {name} (FR: Rituel défini · {name}). It uses the existing Toast with the check icon.
• This happens on create only. Editing a ritual shows no toast, because the card already updates in place.
• The copy follows UX_WRITING.md: calm and precise, no gamified wording. The · pattern matches the chat log card (Logged · {name}).

How

• New ToastProvider + useToast() (components/ui/toast-provider.tsx), mounted in the protected layout around <main>.
  • It shows one toast at a time. A new toast replaces the current one, and each toast closes itself after 5 s or when dismissed.
  • The toast state lives in the layout, not in the button, so it survives when the page content is replaced. This matters for the first ritual: the empty state's CTA unmounts as soon as the list replaces it.
• RitualForm → RitualFormSheet: onSuccess now passes the saved values up, and the sheet exposes an optional onSaved. The edit flow does not use it and is unchanged.
• DefineRitualButton: calls toast.show(...) when the save succeeds.
• Refactor: the Settings feedback confirmation now uses the provider. Its local auto-dismiss wrapper and duplicate timer code are removed; message, icon and duration are unchanged.
• Adds the i18n key rituals.create.saved in en.json and fr.json. No new styles; the toast uses existing color tokens.

Out of scope

• createRitual only revalidates /protected/rituals, not /protected/flow. This was noted during the investigation but left untouched on purpose, to keep this change low risk.
• The nudge toast and this toast share the same position. They can overlap if a ritual is created within 6 s of opening the app with unseen nudges. This was accepted as unlikely.

Testing

• tsc --noEmit, eslint, vitest run (76 passed)
• Create a ritual from the Rituals board: toast show

What

• After a ritual is created, a toast appears: Ritual defined · {name} (FR: Rituel défini · {name}). It uses the existing Toast with the check icon.
• This happens on create only. Editing a ritual shows no toast, because the card already updates in place.
• The copy follows UX_WRITING.md: calm and precise, no gamified wording. The · pattern matches the chat log card (Logged · {name}).

How

• New ToastProvider + useToast() (components/ui/toast-provider.tsx), mounted in the protected layout around <main>.
  • It shows one toast at a time. A new toast replaces the current one, and each toast closes itself after 5 s or when dismissed.
  • The toast state lives in the layout, not in the button, so it survives when the page content is replaced. This matters for the first ritual: the empty state's CTA unmounts as soon as the list replaces it.
• RitualForm → RitualFormSheet: onSuccess now passes the saved values up, and the sheet exposes an optional onSaved. The edit flow does not use it and is unchanged.
• DefineRitualButton: calls toast.show(...) when the save succeeds.
• Refactor: the Settings feedback confirmation now uses the provider. Its local auto-dismiss wrapper and duplicate timer code are removed; message, icon and duration are unchanged.
• Adds the i18n key rituals.create.saved in en.json and fr.json. No new styles; the toast uses existing color tokens.

Out of scope

• createRitual only revalidates /protected/rituals, not /protected/flow. This was noted during the investigation but left untouched on purpose, to keep this change low risk.
• The nudge toast and this toast share the same position. They can overlap if a ritual is created within 6 s of opening the app with unseen nudges. This was accepted as unlikely.

Testing

• tsc --noEmit, eslint, vitest run (76 passed)
• Create a ritual from the Rituals board: toast shows the ritual name
• Create a ritual from Rhythm ("Add a ritual")
• Edit a ritual: no toast
• Settings, send feedback: same confirmation as before
• Create the first ritual from an empty account (empty-state CTA unmounts): toast stays visible
• FR copy check

[vercel]

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

Project	Deployment	Actions	Updated
strive	Ready	Preview	Sep 13, 2026 3:10pm UTC

[github-actions]

Strive PR Agent Review

The review could not be generated for this run (model unavailable or rate-limited). Push again to retry.