vscode-extension: Refactor for clearer module boundaries (workspace scan command)

[Gbangbolaoluwagbemiga]

Problem

This work item hardens vscode-extension in the area of workspace scan command so the project can
scale in production (reliable CI, predictable outputs, and safe-by-default behavior).

Work

• Identify the owner modules/files inside vscode-extension for workspace scan command.
• Implement the change described by Refactor for clearer module boundaries with minimal breaking surface.
• Add tests (unit + integration where relevant) and ensure they run in CI.
• Update docs/examples so contributors can adopt the new behavior confidently.

Acceptance criteria

• CI passes for the touched area (lint, tests, and any component-specific workflow).
• Behavior is documented (link from DOCUMENTATION_INDEX.md or the nearest canonical doc).
• Output formats remain stable; if changes are required, version bump + migration notes are included.

Notes

Component: vscode-extension
Subarea: workspace scan command
If this expands beyond a single PR, split into sub-issues and cross-link.

[codefather2026]

@codefather2026 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, i will like to solve this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @codefather2026 to this issue.

[Ekenesamuel8]

@Ekenesamuel8 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

hello boss, please i will like to work on this task. thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ekenesamuel8 to this issue.

[codemagician1949]

@codemagician1949 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Maintainer, I'd love to take this one on. I've gone through the codebase and I'm comfortable with the approach needed here. I'll keep the change focused, add tests, and make sure CI stays green. Happy to open a draft early so we can align on direction.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @codemagician1949 to this issue.

[drips-wave]

Congratulations, @codemagician1949! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @codemagician1949: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @codemagician1949 as part of the Stellar Wave Program's 6th Wave 🥳

😎 @codemagician1949: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.