PySpector integrates a Rust-based scan engine. Currently, errors raised during engine execution are handled in a very generic way, which can make debugging and user feedback harder than necessary.

This issue is suitable for first-time contributors.

What to do:

• Review how exceptions are currently caught around the scan engine invocation
• Improve error handling by distinguishing common failure scenarios (e.g. configuration errors vs engine runtime errors)
• Keep user-facing output clean and friendly (no stack traces)
• Ensure behavior remains unchanged on successful scans

No Rust knowledge required. Basic Python exception handling is enough :)