Configuration mismatch in karate-config.js during environment-based credential switching

When utilizing karate-config.js to separate production credentials from mock data for integration testing, the framework relies on the -env system property to load specific profiles. The goal is to ensure that tests targeting a local mock server (Karate Netty) never inadvertently trigger requests to production endpoints due to configuration leaks.

There is uncertainty regarding the priority of variable assignment when a variable is defined both in the global configuration and overridden within a specific feature file during a mock-based test run. If the baseUrl is dynamically reassigned to a local port, the interaction between the JavaScript-based config engine and the feature-level variable scope must be strictly defined to prevent credential exposure.

• How does Karate handle the precedence of variables defined in karate-config.js when they are redefined within a feature file during a mock server execution?
• Is there a mechanism to enforce a strict "non-production" state that prevents the execution of any request if production credentials are detected while the environment is set to dev?