fix: remove default value from complexity report option to enable tag-specific detection (#1049)

Removes the default empty array value from the complexity report option to properly detect when tags are explicitly provided vs when no tags are provided, fixing the expand --all command behavior with tagged tasks.

Co-authored-by: Ben Vargas <ben@example.com>

.changeset/fix-tag-complexity-detection.md

@@ -0,0 +1,7 @@
+---
+"task-master-ai": patch
+---
+
+Fix tag-specific complexity report detection in expand command
+
+The expand command now correctly finds and uses tag-specific complexity reports (e.g., `task-complexity-report_feature-xyz.json`) when operating in a tag context. Previously, it would always look for the generic `task-complexity-report.json` file due to a default value in the CLI option definition.

scripts/modules/commands.js

@@ -1564,8 +1564,8 @@ function registerCommands(programInstance) {
 		) // Allow file override
 		.option(
 			'-cr, --complexity-report <file>',
-			'Path to the report file',
-			COMPLEXITY_REPORT_FILE
+			'Path to the complexity report file (use this to specify the complexity report, not --file)'
+			// Removed default value to allow tag-specific auto-detection
 		)
 		.option('--tag <tag>', 'Specify tag context for task operations')
 		.action(async (options) => {