chrome-ext implementation does not allow for auto-complete

[jpc-ae]

Describe the bug
When using the following settings:

{
  "i18n-ally.enabledFrameworks": [
    "chrome-ext"
  ],
  "i18n-ally.localesPaths": "_locales",
  "i18n-ally.dirStructure": "dir",
  "i18n-ally.keystyle": "nested",
  "i18n-ally.ignoreFiles": [
    "*/starter.json",
    "*/store_page.txt"
  ],
  "i18n-ally.regex.usageMatchAppend": [
    "[^\\w\\d]i18n\\(\\s*['\"`]({key})['\"`]"
  ]
}

i18n-ally is able to find and match strings no problem as seen below:

The problem is auto-complete doesn't seem to be working. I just get a message that the key doesn't exist until I type out the full key and it finds a match:

It's the same whether I use my custom function or the default chrome.i18n.getMessage({key}[, ...substitutions]):

Everything else is working fine, but I'm really missing autocomplete which I know would normally work if I create a custom framework without the .message refactor (except .message will be appended which I don't want), so it seems that's what's tripping it up.

Extension Version
i18n Ally VS Code extension v2.13.1

Framework/i18n package you are using
chrome-ext

To Reproduce
Steps to reproduce the behavior:

1. Type chrome.i18n.getMessage('
2. Start typing the name of an existing message
3. See that no suggestions are provided

Device Infomation

• OS: Windows 11 Home
• Version: 24H2
• VS Code Version: 1.96.2

Extension Log

🈶 Activated, v2.13.1

――――――
...
――――――

🧩 Enabled frameworks: Chrome Extension
🧬 Enabled parsers: json, yaml, json5

🚀 Initializing loader "c:\..."
📂 Directory structure: dir
🗃 Path Matcher Regex: /^(?<locale>[\w-_]+)(?:.*\/|^).*\.(?<ext>json|ya?ml|json5)$/

📂 Loading locales under c:\...\_locales
	📑 Loading (en) en/messages.json [1736262669052.11]

👀 Watching change on c:\...\_locales
✅ Loading finished


――――――

🔄 Update usage cache of c:\...\popup\main.js

Screenshots
See above