handle_build_failurelisted

# handle_build_failure Build failures are mechanical — the compiler is telling you exactly what it doesn't understand. The key is learning to read what the compiler is actually saying, not just the last line. ## Step 1: Read the First Error, Not the Last Build tools often cascade: one error causes 10 more downstream. Fix the first error and many later ones disappear. Always scroll to the top of the build output. In Rust/cargo, errors are color-coded and clearly numbered. In TypeScript, errors at the top of the output are often the root. ``` # cargo output — read the FIRST error (E0308, E0432, etc.), not the last error[E0432]: unresolved import `crate::domain::Order` --> src/services/order_service.rs:3:5 | 3 | use crate::domain::Order; | ^^^^^^^^^^^^^^^^^ no `Order` in `domain` error[E0425]: cannot find value `order_service` in this scope --> src/commands/orders.rs:15:10 | 15 | order_service.create(args).await | ^^^^^^^^^^^^^ not found in this scope ``` Here, the second error is caused by the first — fix the import and both go away. ## Common Build Error Categories ### Missing Import / Module Not Found **Python (ImportError / ModuleNotFoundError)** ``` ModuleNotFoundError: No module named 'myapp.services.coupon' ``` Cause: the file doesn't exist, the path is wrong, or the package isn't installed. - Check: does `myapp/services/coupon.py` actually exist? - Check: is there an `__init__.py` in `myapp/services/`? - Check: run `pip list` — is t