internal/core/spec/params.go (1)

154-161: ⚠️ Potential issue | 🟠 Major

Schema-mode detection here is too global and can drop step params silently.

parseParamValue is also used by step/sub-DAG params parsing, so this branch can reinterpret ordinary maps as schema-backed and return no pairs when values is absent. That changes behavior outside DAG-root params parsing and can lose user input without an explicit error.

💡 Suggested fix direction

-func parseParamValue(ctx BuildContext, input any) ([]paramPair, error) {
+func parseParamValue(ctx BuildContext, input any, allowSchemaDeclaration bool) ([]paramPair, error) {
...
-	case map[string]any:
-		if _, ok := extractParamsSchemaDeclaration(v); !ok {
+	case map[string]any:
+		if !allowSchemaDeclaration {
+			return parseMapParams(ctx, []any{v})
+		}
+		if _, ok := extractParamsSchemaDeclaration(v); !ok {
			return parseMapParams(ctx, []any{v})
		}

Then call DAG-root parsing with allowSchemaDeclaration=true, and step/sub-DAG parsing with false.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@internal/core/spec/params.go` around lines 154 - 161, The current schema-mode
detection in parseParamValue (using extractParamsSchemaDeclaration and checking
v["values"]) is too global and can silently drop step/sub-DAG params; update
parseParamValue to accept an allowSchemaDeclaration bool and only treat maps as
schema-backed when allowSchemaDeclaration is true, leaving the existing branch
(extractParamsSchemaDeclaration + v["values"] check) guarded by that flag;
update callers that parse DAG-root params to pass allowSchemaDeclaration=true
and callers for step/sub-DAG params to pass allowSchemaDeclaration=false so
ordinary maps are not reinterpreted as schema declarations.