Refactor admin actions to prevent error information leakage

[google-labs-jules]

🛡️ Sentinel: [MEDIUM] Fix information leakage in admin actions

Vulnerability:
Admin actions (updateUserRole, inviteUser, resendInvite) were throwing raw errors directly to the client. This could expose internal details (e.g., stack traces, database errors, email service errors) if not properly handled by the framework or if debug mode is enabled.

Impact:
Potential exposure of sensitive system information or confusing error messages to end users.

Fix:
Refactored these actions to use the Result pattern (ok, err) consistent with other parts of the application.

• Wrapped operations in try-catch blocks.
• Logged full error details on the server using log.error.
• Returned generic "SERVER" error messages to the client.
• Updated InviteUserDialog, UserRoleSelect, and ResendInviteButton to handle the Result type and display safe error messages.

Verification:

• Verified via pnpm typecheck, pnpm lint, and pnpm build.
• Visually verified error handling using a temporary test page and Playwright script (mocking unauthenticated state to trigger "Unauthorized" error toast).

---

PR created automatically by Jules for task 11930672150919906896 started by @timothyfroehlich

[vercel]

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

Project	Deployment	Review	Updated (UTC)
pin-point	Ready	Preview, Comment	Jan 14, 2026 7:16pm

[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.