Description:
When solving a sketch using the Python bindings for the SolveSpace solver, the result includes a bad field indicating the number of bad constraints. However, the indices of these bad constraints are not provided, making it difficult to diagnose which constraints are causing issues.

Expected Behavior:
The solver should return the indices of the failed constraints instead of the count, allowing users to identify and fix problematic constraints.

Would be great to get feedback on whether this is feasible or if there's already a way to access this information that I may have missed. Thanks!

SolveSpace version: 3.1.0.dev26