task: New language support (7 requests)

[DeusData]

Scope

Umbrella tracker for new-language support requests. Each one needs:

1. A vendored tree-sitter grammar
2. Language registration in the lang spec table
3. AST → graph visitor (Function, Module, Class, CALLS, IMPORTS edges)
4. Optional: Hybrid LSP semantic resolver (Tier 2+)
5. Test fixtures from a popular OSS project in that language

Sub-issues

• [Feature Request] Can you add PowerShell 7 and Windows PowerShell support to this? #35 — [Feature Request] PowerShell 7 and Windows PowerShell support
• [Feature Request] I know the language is mostly obsolete, but CFML support? #38 — [Feature Request] CFML support
• Add support for Luau? #39 — Add support for Luau
• Qt QML language support  #42 — Qt QML language support
• Feature Request: GDScript support (.gd files) #186 — Feature Request: GDScript support (.gd files)
• feat: HCL/Terraform semantic extraction — wire tree-sitter visitor to graph builder #337 — feat: HCL/Terraform semantic extraction
• feat: Helm/YAML semantic extraction — named templates, includes, chart dependencies #338 — feat: Helm/YAML semantic extraction

Acceptance

Per language:

1. Grammar vendored or marked as out of scope (with rationale).
2. If in scope: lang spec entry + AST visitor + at least one realistic OSS testbed indexed without errors.
3. Hybrid LSP support is not required for closure — tree-sitter-only coverage is acceptable for a first pass.

Why one task

These are independent but follow the same pattern. Grouping them lets us prioritize by community signal (👍 reactions on linked issues), batch grammar audits, and keep the per-language work consistent.