Tracing should indicate what bicepconfig.json file(s) were found and are being used.

This would help debugging and understanding the behavior of where settings are coming from.

The issue concerns tracing and bicepconfig.json discovery, but it names no files, tests, or entry points. Start by locating the tracing and configuration-loading code, then determine where found files and the files actually used are reported. Done means tracing clearly identifies the relevant bicepconfig.json file or files.

Written by the indexing model from the issue text.