docs drift: conditional/hit/log breakpoint support matrix conflicts with implementation

[Timi16]

Problem

Feature docs claim conditional/hit/log breakpoints are unsupported, but backend and adapter advertise and process these capabilities.

Evidence:

• Docs say NO: docs/feature-matrix.md:36-38, extensions/vscode/README.md:248-250
• Adapter announces support flags: extensions/vscode/src/dap/adapter.ts:135-137
• Backend capabilities are true: src/server/debug_server.rs:839-844

Files to change

• docs/feature-matrix.md
• extensions/vscode/README.md
• tests/cli/help_tests.rs or extension docs tests if present

Acceptance criteria

• Capability docs match runtime behavior.
• If support is partial, docs clearly state limitations.
• No contradictory statements between matrix and extension README.

[kunal-drall]

@kunal-drall has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I'll take this — docs/code alignment fix.
Will audit the actual runtime behavior of conditional/hit/log breakpoints against both the adapter flags and backend capabilities, then update feature-matrix.md and extensions/vscode/README.md to reflect reality. Document any partial support with clear limitation notes. Verify no contradictions remain.
Experienced with DAP/debugger tooling and technical documentation across developer tools.

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

[AbdulHafizM]

@AbdulHafizM has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I would like to work on this issue.

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

[Free-codaer]

@Free-codaer has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi, I'm a seasoned senior developer, and I would love to work on this issue.

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

[drips-wave]

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

🧑‍💻 @AbdulHafizM: 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 removed from the Stellar Wave Program by the repository maintainers.

@AbdulHafizM, you have been unassigned from this issue. If you have any questions, please reach out to the repo maintainers.