Never time out a snackbar that carries an action

M3's accessibility page forbids it outright: an actioned snackbar has to wait
for the person to read it and reach its action. An entry with an action and no
timeout of its own is now untimed, the close button it already draws being the
way out; a timeout written out still wins. Plan step 11, actions.md ACT-03.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9

resources/views/components/toast.blade.php

@@ -7,9 +7,10 @@
      dispatches from a Livewire component — and for `window.materialToast(title, options)` from
      JavaScript (`{ type, description, timeout, sticky, action: { label, handler, event } }`).
      Toasts queue and show in turn, each for its `timeout` (4s by default; M3 asks for 4–10s),
-     paused while the pointer or focus is on it. A toast with an action or no timeout gets a close
-     button. Pressing the action closes the snackbar, calls `handler` and dispatches `event` (a
-     name) on `window`; both may be given.
+     paused while the pointer or focus is on it. A toast with an `action` has no timeout at all,
+     as M3 requires — it waits to be read and acted on — unless the caller writes a `timeout` out.
+     A toast with an action or no timeout gets a close button. Pressing the action closes the
+     snackbar, calls `handler` and dispatches `event` (a name) on `window`; both may be given.
 
      `sticky: true` keeps a toast until it is dismissed or its action pressed, without holding up
      the queue: a toast that arrives meanwhile shows in its place, and the sticky one comes back