Feature Request

Currently, the oxc.fixKind setting controls both which fixes are shown as available quick-fixes in the editor AND which fixes are auto-applied when saving with source.fixAll.oxc enabled.

This coupling prevents a common workflow I had with Eslint:

• See all available fixes (including suggestions and dangerous fixes) as manual quick-fix options
• Only auto-apply safe fixes on save

Use Case

I want to configure my VSCode extension to:

1. Display all suggestions/fixes in the editor (so I can manually apply them when needed)
2. Only auto-apply safe_fix level fixes when I save the file

Currently, if I set "oxc.fixKind": "safe_fix", I only see safe fixes as available quick-fixes. If I set it to "all", then all fixes (including dangerous ones) get auto-applied on save, which is too aggressive for me.

Proposed Solution

Split oxc.fixKind into two separate settings:

• setting1 Controls which fixes are shown as available quick-fix code actions in the editor
• setting2 Controls which fixes are automatically applied when source.fixAll.oxc is triggered on save

Alternatives

An alternative approach would be to always show all available fixes regardless of fixKind, and only use fixKind to control auto-apply behavior.

_{I used Claude Sonnet 4.5 Thinking to help me format this, with a thorough review.}