[jorgeluisblanco]

Summary

• add Visual Basic .NET (.vb) language discovery and configuration
• vendor a patched Tree-sitter VB.NET grammar with license and provenance metadata
• extract VB.NET types, methods, fields, properties, events, imports, inheritance and calls
• resolve VB.NET calls case-insensitively and include VB.NET in the .NET language family
• add corpus, extraction, registry, grammar and reproduction coverage

Validation

• Tree-sitter corpus: 18/18 passed
• targeted native test suites: 884 passed
• reproduction suites: 58 passed
• language contracts: 44/44 passed
• production build completed successfully
• indexed a representative 26-file VB.NET solution with 0 partial/unusable parses and 0 unresolved calls

Fixes #1178

AI assistance

This contribution was prepared with OpenAI Codex under the contributor's direction. The contributor reviewed and tested the changes and accepts responsibility for them.

[github-actions]

Thanks for opening this — it has been seen, and it is queued.

This note is automated, but it is not a brush-off: it exists so you know where your PR stands instead of having to guess from silence.

Current review status: working through a backlog. 0.9.1-rc.1 is out, so the release freeze that held reviews is over — but it left a large queue of open pull requests behind it, and we are reading through them oldest-first. The background is in discussion #1144.

What that means for this PR, concretely:

• It will not be closed for inactivity. No stale bot touches pull requests here.
• It may still sit a while before a human reads it. That is on us, not on you.
• Older PRs are read first, so a recent one is not being skipped — it is behind a queue.

Things that will genuinely speed it up whenever review does happen:

• Keep it rebased on main — the tree is moving quickly right now, and a conflicting branch cannot be reviewed as the diff you intended.
• Get CI green, or say which failures you believe are pre-existing.
• Keep the change to one claim. Bundled features and refactors get split before they get merged, which costs you a round trip.
• Every commit needs a sign-off (git commit -s) — CI enforces DCO.

If this fixes a bug, a reproduction we can run is worth more than a description of the symptom.

Thanks for contributing, and sorry in advance for the wait.

[DeusData]

Thank you, @jorgeluisblanco, for this VB.NET contribution, and welcome! This is a careful piece of work. The language wiring follows the existing C# and .NET patterns closely. The Inherits/Implements, field, import and constructor extraction is easy to follow. You updated every registration tripwire (call-node manifest, capability ledger, label goldens) consistently. The grammar provenance is written down clearly: the upstream pin, the byte-identical MIT LICENSE, and credit for the patch you built on. That makes our side of the review much easier.

I want to be upfront about how grammar changes work here, so nothing in this comment comes as a surprise later. We vendor third-party grammar code ourselves: we pin the upstream source, verify the licenses, regenerate the parser and do the vendoring in-house, rather than merging generated parser output from a pull request. That is the same note we left on #1178 for the earlier VB.NET work. The files involved here are everything under internal/cbm/vendored/grammars/vbnet/ and tools/tree-sitter-vbnet/, plus the license-audit and checksum tables under scripts/, which only maintainers edit. None of this reflects on the quality of your work. It is a policy we apply to every contribution, including our own.

There is also an older open pull request for the same language, #1179, and both touch the same language slot. We would like to look at the VB.NET grammar choice and the open VB-family pull requests together instead of deciding them one at a time. Some questions are still open on our side, such as which grammar to use, how VB.NET and VB6 share aliases like vb, and how case-insensitive names should resolve. Your PR is a very useful input for those decisions.

Nothing is needed from you right now. We will come back to you here once we have decided how the grammar side will proceed. For when you next touch the branch: the only red CI check is lint, and it is formatting only. clang-format wants the comments in the CBMLanguage enum in internal/cbm/cbm.h re-aligned now that CBM_LANG_VISUALBASIC is the longest entry, plus a few lines in lang_specs.c and extract_defs.c. All the test legs are green.

Thanks again for putting this much care into it, and sorry in advance for the wait while we sort out the grammar side.