fix(template-anchor-has-content): fixable meta, clearer shadowing comment, is-native-element JSDoc sync (Copilot review)

- Add meta.fixable: null — the rule is not autofixable; be explicit so
  eslint-plugin/consistent-output / downstream tooling doesn't misclassify
  it.
- Clarify test comment: 'detects the shadowing via scope bindings in the
  scope chain' (the implementation walks scope.variables up scope.upper,
  it does not use scope.references).
- Byte-identical sync of lib/utils/is-native-element.js (+ test) to PR #50
  canonical; drops the stale template-no-noninteractive-tabindex JSDoc
  reference (non-existent rule on master).

Author: johanrd

lib/rules/template-anchor-has-content.js

@@ -157,6 +157,7 @@ module.exports = {
       url: 'https://github.com/ember-cli/eslint-plugin-ember/tree/master/docs/rules/template-anchor-has-content.md',
       templateMode: 'both',
     },
+    fixable: null,
     schema: [],
     messages: {
       anchorHasContent:

lib/utils/is-native-element.js

@@ -21,19 +21,17 @@ const ELEMENT_TAGS = new Set([...htmlTags, ...svgTags, ...mathmlTagNames]);
  * MathML spec registries, reached via the `html-tags` / `svg-tags` /
  * `mathml-tag-names` packages). It is NOT the same as:
  *
- *  - "native accessibility" / "widget-ness" — see `interactive-roles.js`
- *    (aria-query widget taxonomy; an ARIA-tree-semantics question)
- *  - "native interactive content" / "focus behavior" — see
- *    `html-interactive-content.js` (HTML §3.2.5.2.7; an HTML-content-model
- *    question about which tags can be nested inside what)
+ *  - "native accessibility" / "widget-ness" — an ARIA-tree-semantics
+ *    question (for example, whether something maps to a widget role)
+ *  - "native interactive content" / "focus behavior" — an HTML content-model
+ *    question about which elements are considered interactive in the spec
  *  - "natively focusable" / sequential-focus — see HTML §6.6.3
  *
  * This util answers only: "is this tag a first-class built-in element of one
  * of the three markup-language standards, rather than a component invocation
- * or a shadowed local binding?" Callers compose it with the other utils
- * above when they need a more specific question (see e.g. `template-no-
- * noninteractive-tabindex`, which consults both this and
- * `html-interactive-content`).
+ * or a shadowed local binding?" Callers should combine it with whatever
+ * accessibility, interactivity, or focusability checks they need for more
+ * specific questions.
  *
  * Returns false for:
  *  - components (PascalCase, dotted, @-prefixed, this.-prefixed, ::-namespaced —

tests/lib/rules/template-anchor-has-content.js

@@ -104,7 +104,7 @@ ruleTester.run('template-anchor-has-content', rule, {
 
     // Scope-shadowed lowercase `a` (local binding in GJS) — not the native
     // HTML anchor, so the rule does not validate it. `isNativeElement`
-    // detects the shadowing via scope reference tracking.
+    // detects the shadowing via scope bindings in the scope chain.
     {
       filename: 'test.gjs',
       code: `

tests/lib/utils/is-native-element-test.js

@@ -2,10 +2,12 @@
 
 const { isNativeElement, ELEMENT_TAGS } = require('../../../lib/utils/is-native-element');
 
-// Tests exercise the list-lookup path only. Scope-based shadowing is covered
-// by the rule-level test suites (see tests/lib/rules/template-no-block-params-
-// for-html-elements.js and siblings) because it requires a real ESLint
-// SourceCode / scope manager that's only built up by the rule tester.
+// Tests cover both the list-lookup path (no sourceCode) and scope-shadowing
+// detection via lightweight sourceCode stubs. Rule-level suites exercise
+// shadowing against a real ESLint scope manager built by ember-eslint-parser
+// (see tests/lib/rules/template-no-block-params-for-html-elements.js and
+// siblings); these unit tests verify the shadowing branch in isolation with
+// a minimal stub of the `getScope`/`variables`/`upper` surface it touches.
 
 // Stub a minimal ESLint-shaped sourceCode object. The real one uses scope
 // managers produced by ember-eslint-parser; for unit-level coverage we mock