Issue: loadConfig hardcodes configuration file path, preventing testing with different configurations
Issue: loadConfig hardcodes configuration file path, preventing testing with different configurations: a task in LegoFlow-SWE (Harbor dataset). The loadConfig function currently always reads configuration from a specific hardcoded file location . Because the path cannot be changed by the caller…
The task
The `loadConfig` function currently always reads configuration from a **specific hardcoded file location**. Because the path cannot be changed by the caller, it is impossible to:
Part of Lego-X/LegoFlow-SWE.