Drop the Tailwind framing from a stale comment in app.css

The recovery-codes pulse comment still explained itself against
Tailwind's animate-pulse, which left the stack in 2.0.0. The reason
stands on its own: the package keeps no keyframe utility for a pulse
loop, so the loading state animates on the effects spring instead.

config/livewire.php:237 stays on Livewire's own "tailwind" default:
SealShare still installs livewire-material ^2.0 from Gitea, whose
vendor copy has no `pagination::material` view yet, so pointing
pagination_theme at it now would break pagination. The package takes
the theme over itself once 2.2.0 is tagged and pulled.
DesignLanguageTest carried no Tailwind wording to update.

Full suite (322) and Pint green, unchanged — run against the old
vendor copy, so the guard's new undeclared-class check is not
exercised here yet.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

resources/css/app.css

@@ -268,7 +268,7 @@
 /*
  * resources/views/pages/settings/two-factor/recovery-codes.blade.php: a code dims to M3's disabled
  * content opacity while regenerateRecoveryCodes() is in flight, and back, on the effects spring
- * instead of Tailwind's animate-pulse loop — 2.0.0 keeps no keyframe utility for it. The
+ * rather than a keyframe pulse loop — 2.0.0 keeps no keyframe utility for one. The
  * transition sits on the code itself so the way back eases too; under reduced motion the token's
  * duration is 0ms.
  */