Resolved conflicts in test files by adopting the new t.Cleanup pattern
from PR #1704 while maintaining fixes for golangci-lint issues.

Apply PR #1704 pattern to terraform_test.go - wrap t.Log in t.Cleanup handler
that only outputs verbose terraform plan results when tests fail.

## what
- Wrapped unconditional `t.Log(output)` in t.Cleanup with t.Failed() check
- Terraform plan output now only shown when test fails

## why
- Line 230 had unconditional t.Log that dumped terraform output to CI logs
- This was pre-existing (added in May, commit d4fa2fe) before PR #1704
- Caused noisy CI logs with walls of component YAML configuration
- Follows same pattern as PR #1704 for other test files

## impact
- CI logs quieter - terraform output only shown on test failures
- Consistent with PR #1704 pattern across all test files
- Debug information preserved when actually needed

Related to PR #1704 (only log verbose test output on failure).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Apply PR #1704 pattern comprehensively across all test files - only show
verbose output (YAML, JSON, debug info) when tests fail.

## what
Fixed unconditional output in 6 test files:
- cmd/root_test.go: command output
- tests/cli_terraform_test.go: terraform stdout/stderr
- tests/validate_schema_test.go: schema validation output
- pkg/merge/merge_context_demo_test.go: error formatting demos
- pkg/config/command_merging_behavior_test.go: command structure debugging
- pkg/config/command_merge_core_test.go: command verification output

## why
- These tests had unconditional t.Log() or fmt.Printf() calls
- Dumped walls of YAML/JSON/debug info to CI logs on every run
- Made CI logs extremely noisy and hard to read
- Some dated back to May 2025, predating PR #1704

## how
- Wrapped all output in t.Cleanup handlers with t.Failed() checks
- Converted fmt.Printf to t.Logf for proper test integration
- Output now only appears when tests actually fail
- Preserved all debug information for troubleshooting

## impact
- CI logs dramatically quieter - no verbose output on success
- Debug info still available when tests fail
- Consistent with PR #1704 pattern across entire codebase
- Easier to spot actual problems in CI output

Related to PR #1704 (quiet test output on success).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Found 6 more instances of unconditional verbose logging in provenance YAML
parser tests. These tests iterate through every line of parsed YAML and log
the entire pathMap, creating walls of debug output in CI logs.

## what
Fixed debug output in 2 files:
- pkg/provenance/yaml_parser_multiline_test.go: 1 instance
- pkg/provenance/yaml_parser_arrays_test.go: 5 instances

All "=== PATH MAP ===" debug outputs now wrapped in t.Cleanup handlers.

## why
- Tests unconditionally logged every YAML line with path mapping
- Created verbose output like:
  ```
  === MULTILINE CONTEXT PATH MAP ===
  Line 0: "description: |" -> Path: "description", IsKey: true
  Line 1: "  This is" -> Path: "description", IsCont: true
  ... (dozens more lines)
  ```
- Made CI logs extremely noisy for tests that always pass
- Debug info is important for troubleshooting parser issues

## how
- Wrapped all pathMap logging loops in t.Cleanup with t.Failed() checks
- Debug output now only shown when tests actually fail
- Preserves full debugging capability when needed

## impact
- Significantly quieter CI logs for passing provenance tests
- Debug output still available when parser tests fail
- Consistent with PR #1704 pattern

Related to PR #1704 (quiet test output on success).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

…p handlers (#1722)

* fix: Only log terraform test output on failure

Apply PR #1704 pattern to terraform_test.go - wrap t.Log in t.Cleanup handler
that only outputs verbose terraform plan results when tests fail.

## what
- Wrapped unconditional `t.Log(output)` in t.Cleanup with t.Failed() check
- Terraform plan output now only shown when test fails

## why
- Line 230 had unconditional t.Log that dumped terraform output to CI logs
- This was pre-existing (added in May, commit d4fa2fe) before PR #1704
- Caused noisy CI logs with walls of component YAML configuration
- Follows same pattern as PR #1704 for other test files

## impact
- CI logs quieter - terraform output only shown on test failures
- Consistent with PR #1704 pattern across all test files
- Debug information preserved when actually needed

Related to PR #1704 (only log verbose test output on failure).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

* fix: Wrap all unconditional test output in t.Cleanup handlers

Apply PR #1704 pattern comprehensively across all test files - only show
verbose output (YAML, JSON, debug info) when tests fail.

## what
Fixed unconditional output in 6 test files:
- cmd/root_test.go: command output
- tests/cli_terraform_test.go: terraform stdout/stderr
- tests/validate_schema_test.go: schema validation output
- pkg/merge/merge_context_demo_test.go: error formatting demos
- pkg/config/command_merging_behavior_test.go: command structure debugging
- pkg/config/command_merge_core_test.go: command verification output

## why
- These tests had unconditional t.Log() or fmt.Printf() calls
- Dumped walls of YAML/JSON/debug info to CI logs on every run
- Made CI logs extremely noisy and hard to read
- Some dated back to May 2025, predating PR #1704

## how
- Wrapped all output in t.Cleanup handlers with t.Failed() checks
- Converted fmt.Printf to t.Logf for proper test integration
- Output now only appears when tests actually fail
- Preserved all debug information for troubleshooting

## impact
- CI logs dramatically quieter - no verbose output on success
- Debug info still available when tests fail
- Consistent with PR #1704 pattern across entire codebase
- Easier to spot actual problems in CI output

Related to PR #1704 (quiet test output on success).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

* fix: Wrap provenance test debug output in t.Cleanup handlers

Found 6 more instances of unconditional verbose logging in provenance YAML
parser tests. These tests iterate through every line of parsed YAML and log
the entire pathMap, creating walls of debug output in CI logs.

## what
Fixed debug output in 2 files:
- pkg/provenance/yaml_parser_multiline_test.go: 1 instance
- pkg/provenance/yaml_parser_arrays_test.go: 5 instances

All "=== PATH MAP ===" debug outputs now wrapped in t.Cleanup handlers.

## why
- Tests unconditionally logged every YAML line with path mapping
- Created verbose output like:
  ```
  === MULTILINE CONTEXT PATH MAP ===
  Line 0: "description: |" -> Path: "description", IsKey: true
  Line 1: "  This is" -> Path: "description", IsCont: true
  ... (dozens more lines)
  ```
- Made CI logs extremely noisy for tests that always pass
- Debug info is important for troubleshooting parser issues

## how
- Wrapped all pathMap logging loops in t.Cleanup with t.Failed() checks
- Debug output now only shown when tests actually fail
- Preserves full debugging capability when needed

## impact
- Significantly quieter CI logs for passing provenance tests
- Debug output still available when parser tests fail
- Consistent with PR #1704 pattern

Related to PR #1704 (quiet test output on success).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

* fix: Remove unused imports and empty loop from test refactoring

Cleaned up unused imports and code left over from wrapping fmt.Print*
calls in t.Cleanup handlers.

## what
- Removed unused `fmt` imports from 3 test files
- Removed empty `for _, cmd := range commands {}` loop

## why
Build was failing with:
- pkg/config/command_merge_core_test.go:4 - "fmt" imported and not used
- pkg/merge/merge_context_demo_test.go:5 - "fmt" imported and not used
- tests/validate_schema_test.go:5 - "fmt" imported and not used
- pkg/config/command_merging_behavior_test.go:295 - declared and not used: cmd

These were left over from converting fmt.Printf to t.Logf in t.Cleanup handlers.

## impact
- ✅ Build passes
- ✅ Tests compile successfully
- ✅ Clean code without unused artifacts

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

---------

Co-authored-by: Claude <[email protected]>
Co-authored-by: Andriy Knysh <[email protected]>