fix(import): sanitize error messages to prevent backend detail leakage (#2455)

The catch block in processOneBookmark was storing raw error strings via
String(error) in the resultReason field, which is exposed to users through
the getImportSessionResults tRPC route. This could leak internal details
like database constraint errors, file paths, stack traces, or connection
strings.

Replace String(error) with getSafeErrorMessage() that only allows through:
- TRPCError client errors (designed to be user-facing)
- Known safe validation messages from the import worker
- A generic fallback for all other errors

The full error is still logged server-side for debugging.

https://claude.ai/code/session_01F1NHE9dqio5LJ177vmSCvt

Co-authored-by: Claude <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions