Resolving Edge Cases

Use this before editing code when the task is to find, fix, or harden edge cases.

Loop

1. State the intended behavior and the boundary being hardened.
2. Trace the real flow end to end, including callers, sibling routes, cleanup paths, and stored state.
3. List only plausible edge cases for that flow; skip generic checklists that cannot occur.
4. Fix the shared root path, not only the reported symptom.
5. Add the smallest regression test or executable check that fails without the fix.
6. Run the narrow check, then scan sibling callers/routes for the same pattern.
7. Repeat while each fix exposes a concrete adjacent edge case.
8. Run the repo's normal verification gate before final response.

Edge-Case Families

Consider these only when relevant: