Codex safety filters overflag coding work

This looks less like a true security incident and more like a safety-regression incident with real product impact: the filter is apparently pessimizing normal developer work and degrading model quality as a side effect.

• –Benign frontend work being flagged as cyber-risk is a strong sign the classifier thresholds are too aggressive or too poorly scoped.
• –Forced downgrades from GPT-5.3 to GPT-5.2 create immediate UX and trust costs because users experience the model as inconsistent and unreliable.
• –If this is happening broadly, it can slow adoption among developers who expect Codex to handle ordinary repo changes without constant false alarms.
• –The right fix is likely tighter policy routing, better task-context signals, and clearer user-facing explanations when a downgrade is applied.