feat: add Snyk Remediation Agent code action provider [IDE-2052]

[bastiandoetsch]

User description

Summary

• Add RemediationProvider interface and NoopProvider
• Add CodeActionsService.remediationCodeActions — offers RemediationAgentQuickFix for Code issues with HasAIFix=true and non-empty FindingId
• Action is deferred: edit is nil at list time, computed on codeAction/resolve
• Product filter guards: non-Code products and non-AI-fixable issues get no action
• Wire RemediationProvider into di/init.go (nil when feature flag off)

PR Stack — Merge Order

flowchart LR
    main(["main"])
    PR1["#1326 PR-1\nfindingId + kind"]
    PR2["#? PR-2 ← YOU ARE HERE\nCA provider"]
    PR3["#? PR-3\nremy initial"]
    PR4["#? PR-4\nworktree impl"]
    PR5["#? PR-5\nunit tests"]
    PR6["#? PR-6\ninteg+smoke tests"]
    main --> PR1 --> PR2 --> PR3 --> PR4 --> PR5 --> PR6
    style PR2 fill:#ffd700,color:#000

Loading

Depends on: #1326

Test plan

• make test passes

---

PR Type

Enhancement, Tests

---

Description

• Introduce the RemediationProvider interface and NoopProvider.

• Integrate the Remediation Agent into the CodeActionsService.

• Offer deferred "Fix with Snyk Remediation Agent" code actions for fixable findings.

• Add comprehensive tests for the new remediation functionality.

---

Diagram Walkthrough

flowchart LR
  CodeActionsService["CodeActionsService"] -- "Uses" --> RemediationProvider["RemediationProvider (Interface)"]
  RemediationProvider -- "Implemented by" --> NoopProvider["NoopProvider (Initial)"]
  CodeActionsService -- "Generates" --> DeferredCodeAction["Deferred Code Action"]
  DeferredCodeAction -- "Resolves via" --> RemediationProvider
  RemediationProvider -- "Requests" --> RemediationRequest["RemediationRequest"]
  RemediationRequest -- "Contains" --> FindingDetails["Finding ID, File, Range"]
  RemediationProvider -- "Returns" --> WorkspaceEdit["WorkspaceEdit (Lazy)"]

Loading

File Walkthrough

	Relevant files
Enhancement	4 files codeaction.go Integrate remediation provider into code actions service  +75/-15  init.go Initialize code action service with nil remediation provider +1/-1      noop.go Add Noop remediation provider implementation                          +32/-0    provider.go Define remediation provider interface and request                +40/-0
Tests	4 files codeaction_test.go Update code action tests for new constructor                          +3/-3      remediation_test.go Add remediation agent code action tests                                    +272/-0  test_init.go Test DI initialization with nil remediation provider          +1/-1      noop_test.go Test Noop remediation provider                                                      +34/-0

---

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[snyk-pr-review-bot]

PR Reviewer Guide 🔍

🧪 PR contains tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Improper Context Usage 🟡 [minor] The deferredEdit closure uses context.Background() when calling provider.Remediate. This prevents the remediation request from being canceled if the client disconnects or times out during the codeAction/resolve call. While ResolveCodeAction currently doesn't accept a context, the closure should ideally be designed to respect the caller's lifecycle if the interface is updated, or at least note that this call cannot be aborted. edit, err := provider.Remediate(context.Background(), remediation.RemediationRequest{ Incorrect Range Scope 🟡 [minor] In remediationCodeActions, the code assigns issueRange := r, where r is the range of the overall LSP request (params.Range). If a user selects a large block of code containing multiple issues, the remediation agent for a specific finding will receive the entire selection range instead of the precise range of the finding (issue.GetRange()). This can lead to the agent attempting to fix the wrong code or failing due to lack of local context. issueRange := r

📚 Repository Context Analyzed This review considered 17 relevant code sections from 13 files (average relevance: 0.95) domain/ide/command/code_fix.go (lines 1-148) docs/example.md (lines 156-251) infrastructure/code/fake_snyk_code_api_service.go (lines 1-122) application/server/codeaction_handlers.go (lines 1-92) application/server/server.go (lines 204-450) infrastructure/code/issue_enhancer.go (lines 1-238) domain/snyk/mock_snyk/issues_provider_mock.go (lines 1-225) ... and 6 more file(s)

[bastiandoetsch]

/describe

[snyk-pr-review-bot]

PR Description updated to latest commit (58ce900)

[bastiandoetsch]

/describe

[bastiandoetsch]

/describe

[snyk-pr-review-bot]

PR Description updated to latest commit (99f2243)

[snyk-pr-review-bot]

PR Description updated to latest commit (99f2243)

[basti-snyk]

/describe

[snyk-pr-review-bot]

PR Description updated to latest commit (a2330ca)