`TranslationKeyExists` check not detecting translations in section schema

Describe the bug
When using the locales object in a section schema, Theme Check incorrectly flags them as missing

Source

// section/test-section.liquid

<p>{{ 'sections.test-section.title' | t }}</p>
<p>{{ 'sections.test-section.description.desktop' | t }}</p>
<p>{{ 'sections.test-section.description.mobile' | t }}</p>

{% schema %}
{
  "name": "Section",
  "locales": {
    "en": {
      "title": "Title",
      "description": {
        "desktop": "Lorem ipsum dolor sit amet consectetur, adipisicing elit.",
        "mobile": "Lorem ipsum dolor sit amet"
      }
    }
  }
}
{% endschema %}

Expected behaviour
No errors

Actual behaviour
The first three lines all have TranslationKeyExists errors

Debugging information

• OS: Mac
• OS Version: Sequoia 15.2
• Theme Check Version: 3.73.2

Start by tracing the TranslationKeyExists check for the section/test-section.liquid example and how it reads the schema's locales object. Verify the nested title and description.desktop/mobile keys against the translation references, then confirm the expected behavior produces no errors.