Support indexing custom file extensions (e.g., .lua.txt) or respect files.associations

[mency89]

I am working on a Unity project using Lua. In the Unity ecosystem, Lua files must often strictly use the .lua.txt extension (or .txt) to be recognized as TextAsset resources.

Currently, Kilo Code completely ignores these files during indexing, resulting in an empty vector database (0 points in Qdrant), even though they contain valid code.

I have tried the following VS Code settings, but the indexer still skips them:
"files.associations": {
".lua.txt": "lua",
".txt": "lua"
}

It seems the indexer relies on a hardcoded extension allowlist and does not check the VS Code Language Mode or files.associations.
I would like Kilo Code to either:
1.Respect files.associations: If I map *.lua.txt to lua in VS Code, Kilo Code should treat it as a Lua file and pass it to the Tree-sitter parser.
2.Provide a configuration option: Add a setting like kilo.indexing.includePatterns or kilo.indexing.extensions to allow users to manually whitelist extensions (e.g., [".lua.txt", ".txt"]).

I verified the issue by manually renaming a .lua.txt file to .lua. The file was immediately indexed, and Qdrant points increased.

Environment:

OS: Windows 10

Context: Unity Development (Lua)

Vector DB: Qdrant (Docker)