🔒 prevent raw error message exposure in UI

[esenmx]

🎯 What: Replace raw exception message strings displayed in SnackBar with a generic, user-friendly error message.

⚠️ Risk: Displaying raw error messages (such as exception messages or stack details) in the UI can leak sensitive system architecture, database details, or internal logic to end users.

🛡️ Solution: Replaced Text('Failed: $error') with a static user-friendly message (Text('An unexpected error occurred. Please try again.')) in example/lib/main.dart and updated README.md and tests accordingly.

---

PR created automatically by Jules for task 17720049058267261281 started by @esenmx

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[esenmx]

Thanks, but closing this one. The principle is sound in general, but it does not apply here: the package itself (lib/) never renders errors, and the only place $error is shown is the example app, where the sole exception is the literal Exception('simulated failure') thrown in the same file — there is nothing sensitive to leak. The README snippet is deliberately minimal and sits under "No error state" to show where a re-thrown error is handled; the message copy is not its subject, and the example's Failed: Exception: simulated failure is what shows which exception was caught when running the demo. The new widget test for the failure path (tap -> spinner -> idle -> SnackBar) is genuinely useful — that part will be landed separately as a test-only change asserting the existing text.

[google-labs-jules]

Thanks, but closing this one. The principle is sound in general, but it does not apply here: the package itself (lib/) never renders errors, and the only place $error is shown is the example app, where the sole exception is the literal Exception('simulated failure') thrown in the same file — there is nothing sensitive to leak. The README snippet is deliberately minimal and sits under "No error state" to show where a re-thrown error is handled; the message copy is not its subject, and the example's Failed: Exception: simulated failure is what shows which exception was caught when running the demo. The new widget test for the failure path (tap -> spinner -> idle -> SnackBar) is genuinely useful — that part will be landed separately as a test-only change asserting the existing text.

Understood. Thank you for the detailed context and explanation. Acknowledging that this pull request is being closed as the simulated error message in the example app is intentional for demo purposes.