omk-flow-bugfix

To fix a bug using root cause analysis, you collect reproduction evidence like expected versus actual behavior, identify the root cause from logs or recent modifications, implement a minimal correction, and add a regression test to verify the resolution.

The best way to debug a broken feature after recent code modifications is to gather reproduction details, use logs and failing tests to narrow the scope, apply a minimal safe correction, and run targeted quality gates to confirm no regression.

Evidence-driven debugging works by collecting expected versus actual behavior and reproduction context, then using that evidence to narrow scope, identify the root cause, implement a minimal fix, and validate the outcome with targeted tests for software verification.

You do not strictly need failing tests to start a debugging workflow, but having reproduction details like expected versus actual behavior, logs, and recent modification context is required to narrow scope and identify the root cause for suspicious regressions.

You should implement a minimal fix because it targets the root cause directly and is likely to resolve the bug without introducing new regressions, which is then validated by updating regression tests and running targeted quality gates.