fix

To diagnose a bug's root cause across layers, use a diagnostics-first process that guides context gathering, generates hypotheses, and distills evidence into validated root causes using architecture docs and data-model checks.

Architecture-aware analysis for debugging is a method that evaluates frontend, backend, and data structures to identify systemic mismatches, leveraging cross-project memory to accelerate root-cause resolution.

To fix UI not updating after an API call, generate diagnostic hypotheses around data-model checks and API responses, validate the root cause, and apply user-confirmed changes followed by thorough testing.

Yes, architecture docs are required to use a diagnostics-first debugging workflow, as they provide the essential context for accurate hypothesis generation, instrumentation, and validated fixes.

The best way to ensure safe code changes when fixing complex bugs is to follow a diagnostic-first process that requires explicit user confirmation before applying fixes and conducting thorough testing.

You should not use a diagnostic-first approach for bug remediation when you lack access to the underlying code, architecture docs, or templates, as the workflow requires these to generate validated fixes.