no-workaroundslisted

# No Workarounds A workaround makes a failure disappear while leaving its cause intact. **Fix the source, not the signal.** Judge the violated contract and the evidence, not syntax alone: casts, null checks, retries, and framework initialization can be legitimate. Apply this distinction when reading the catalogs too. ## The gate: run before any fix ``` 1. Capture the failing behavior or diagnostic and the expected contract. 2. Trace the relevant data flow, lifecycle, or configuration to a cause supported by evidence. 3. Check that the proposed fix repairs that cause while preserving valid behavior. Silencing a signal -> redesign the fix against the root cause. Cause still unknown -> gather evidence; do not present a hypothesis as a verified fix. Root cause is external -> evaluate the escape valve. ``` Complete the fix when the original reproduction passes, relevant regression checks preserve the contract, and no remaining suppression or fallback conceals the defect. For a plan or review, identify the causal evidence and the checks required to verify the proposed fix; distinguish these from checks actually run. ## The seven signals Use these signals to investigate a possible workaround. Confirm the defect before changing a valid language or framework idiom. | Category | Suspected hidden defect | Fix the source by | |---|---|---| | **TYPE**: forced assertions, `dynamic`, unjustified `!` | Types conceal invalid or absent data | Correcting the contract, initialization, or