test(hcl): mark resolution-benchmark fixture's module-reference edges as aspirational

tests/benchmarks/resolution/fixtures/hcl/expected-edges.json

@@ -1,7 +1,7 @@
 {
   "$schema": "../../expected-edges.schema.json",
   "language": "hcl",
-  "description": "Hand-annotated call edges for HCL/Terraform resolution benchmark. HCL uses module references rather than function calls — edges represent module source references.",
+  "description": "ASPIRATIONAL, not currently enforced (see resolution-benchmark.test.ts's hcl threshold, pinned at 0.0/0.0, and issue #2524): hand-annotated module-reference edges for a HCL/Terraform resolution capability that does not exist yet. HCL has no functions/calls to resolve in the traditional sense — these edges describe a genuinely different, unimplemented notion of module-source-reference linkage ('module.user_service references module.repository'), not a gap in the same call-resolution machinery other 0.0/0.0 languages (cuda/groovy/verilog) are missing. Building this fixture today yields 0 of these 2 edges; every edge that does materialize is a structural 'contains' edge.",
   "edges": [
     {
       "source": { "name": "module.user_service", "file": "main.tf" },

tests/benchmarks/resolution/resolution-benchmark.test.ts

@@ -245,6 +245,12 @@ const THRESHOLDS: Record<string, { precision: number; recall: number }> = {
   cuda: { precision: 0.0, recall: 0.0 },
   groovy: { precision: 0.0, recall: 0.0 },
   verilog: { precision: 0.0, recall: 0.0 },
+  // hcl's fixture (unlike cuda/groovy/verilog above) isn't just "call
+  // resolution not implemented yet" for the same kind of edge every other
+  // language has — HCL has no functions/calls at all. Its expected-edges.json
+  // aspirationally describes a genuinely different, unimplemented capability
+  // (module-source-reference linkage) that 0 of its own edges currently
+  // materialize (see that file's own description and issue #2524).
   hcl: { precision: 0.0, recall: 0.0 },
 };