Swift module resolution fails in opencode edit tool, blocking edits

[irffanasiff]

Description

Summary
When using OpenCode in a Swift/Xcode workspace with internal Swift packages, the edit tool refuses to apply changes. It runs diagnostics that can't resolve these local modules. The project builds fine in Xcode, but OpenCode's diagnostics fail and block all edits.

Steps to Reproduce

1. Open an Xcode Swift project with internal Swift packages/frameworks.
2. Use the edit or write tool on a Swift file that imports these modules.
3. Observe diagnostics errors like:
   • ERROR [10:8] No such module 'Modulename'
   • ERROR [11:8] No such module 'Modulename'
4. Edits are rejected even though the project compiles successfully in Xcode.

Expected Behavior

The edit tool should allow changes without requiring module resolution, or it should resolve modules using the project's Xcode build settings.

Actual Behavior

Edits are blocked due to diagnostics in OpenCode’s environment.

Notes

This seems like a false negative because OpenCode doesn’t load Xcode build configurations or package dependencies. This makes it impossible to apply Swift edits in otherwise valid projects.

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• sourcekit-lsp - wrong error that can't find function/module in scope but app working in symulator correct #4295: sourcekit-lsp - wrong error that can't find function/module in scope but app working in simulator correct (very similar symptom - cannot find modules that should be available)
• Swift LSP not detected #4258: Swift LSP not detected (related Swift LSP detection issue)
• Sessions become unusable due to large LSP diagnostics (Lua + possibly others) #6310: Sessions become unusable due to large LSP diagnostics (related to edit tool being blocked/unusable due to diagnostics issues)

Feel free to ignore if none of these address your specific case.

[irffanasiff]

This is a blocker for me as the agent is no more able to work on my project