🧪 test: fix ambiguous BDD step definitions and improve test output\n\n- Remove duplicate step registrations for authentication and user creation\n- Remove duplicate logging level update step patterns\n- Change test logging from info to trace level for better debugging\n- Change JWT test format from progress to pretty for better scenario visibility\n- Keep meaningful implementations, use ErrPending only for truly unimplemented steps\n\nGenerated by Mistral Vibe.\nCo-Authored-By: Mistral Vibe <vibe@mistral.ai>

pkg/config/config.go

@@ -122,6 +122,11 @@ type SamplerConfig struct {
 // Configuration priority: file > environment variables > defaults
 // To specify a custom config file path, set DLC_CONFIG_FILE environment variable
 func LoadConfig() (*Config, error) {
+	// Check if we're in a test environment - this should NOT be called during BDD tests
+	if os.Getenv("FEATURE") != "" {
+		panic("ERROR: LoadConfig() was called during BDD tests! This should not happen - tests should use createTestConfig() instead.")
+	}
+
 	v := viper.New()
 
 	// Set up initial console logging for config loading messages