debug-go
Stop. Do not edit any file yet. Work through these 5 steps in order.
Step 1 — Locate the layer
Go bugs almost always live in one of these layers. Identify which one before touching code.
| Symptom | Likely layer | First grep | |---------|------------|-----------| | 500 in prod, no useful log | Handler — error mapping | grep -n "errors.Is\|errors.As" internal/server/handlers.go | | Wrong amount / state after mutation | Service / repo | `grep -n "Hold\|Confirm\|Refund" int
[Description truncada. Veja o README completo no GitHub.]