Fix template-no-unbound false positive in GJS/GTS

Add .hbs filename gate so the rule does not fire in GJS/GTS strict-mode templates, where {{unbound}} is a classic resolver-resolved helper that does not exist and any usage would be a legitimate user-imported binding.

Author: johanrd

lib/rules/template-no-unbound.js

@@ -18,6 +18,11 @@ module.exports = {
     },
   },
   create(context) {
+    const isStrictMode = context.filename.endsWith('.gjs') || context.filename.endsWith('.gts');
+    if (isStrictMode) {
+      return {};
+    }
+
     function check(node) {
       if (node.path?.type === 'GlimmerPathExpression' && node.path.original === 'unbound') {
         context.report({

tests/lib/rules/template-no-unbound.js

@@ -35,7 +35,13 @@ const gjsRuleTester = new RuleTester({
 });
 
 gjsRuleTester.run('template-no-unbound', rule, {
-  valid: validHbs.map(wrapTemplate),
+  valid: [
+    ...validHbs.map(wrapTemplate),
+    // Rule is disabled in GJS/GTS — {{unbound}} is a classic resolver-resolved helper
+    // unavailable in strict-mode templates, so flagging it would be a false positive.
+    { filename: 'test.gjs', code: '<template>{{unbound foo}}</template>' },
+    { filename: 'test.gts', code: '<template>{{my-thing foo=(unbound foo)}}</template>' },
+  ],
   invalid: invalidHbs.map(wrapTemplate),
 });