edge-case-hunter

Enumerate every input field, map its type and assumptions, then generate cases per boundary axis: null, empty string, zero, negative, huge values, duplicates, and exotic Unicode. Execute each literal input and observe whether the result is a clean error, silent corruption, or correct handling.

Test zero, negative values, and huge values that may overflow integers or trigger loops and out-of-memory errors. For example, quantity 0 may cause division by zero downstream, and count 2147483648 may overflow a 32-bit integer.

Submit zero-width joiners, RTL override characters, emoji, and combining characters to check for invisible duplicates or broken rendering. Verify whether the system normalizes Unicode intentionally before reporting a finding, since normalization by design is not a bug.

A case is a false positive when framework schema validation rejects the input before the handler, when null or zero is an intentional default handled downstream, or when the axis does not apply to the field type, such as negative values for an enum.

Silent success with wrong state is worse than a crash because it raises no alert while corrupting data. Findings should be reported with the exact literal input, the observed output or state, and a confidence level from CONFIRMED down to SPECULATIVE.