panda850819 Debug
Reproduce the failure and identify its mechanism before editing. Verify the fix with a check that demonstrated the failure, rerun after the final edit, and search for the same defect in sibling paths. If reproduction is unavailable, report the diagnosis as unconfirmed.
For UI, native, or generated-artifact bugs, verify the running/rendered output rather than compilation alone. Before asking a human to test, prove artifact identity using the test-loop reference.
Consult known bug classes when relevant to the symptom. Use project learning recall for unexplained or recurring failures, not as an extra ceremony for an already-proven cause. New reusable findings are candidates for the host's memory store, not automatic writes.