[task] Extract validation methods from strict_mode.go to strict_mode_validation.go

[github-actions]

Objective

Extract validation methods from pkg/workflow/strict_mode.go into a dedicated validation file following the established *_validation.go pattern.

Context

Similar to the engine.go issue, strict_mode.go contains validation methods that should be in a dedicated validation file for consistency with the codebase pattern (docker_validation.go, npm_validation.go, etc.). This is part of Issue #3 from the semantic function clustering analysis (Priority 2: Medium Impact, Medium Effort).

Related to #3478

Approach

1. Review current structure of strict_mode.go and validation_strict_mode.go (note: analysis shows there's already a validation_strict_mode.go file)
2. Determine if consolidation into strict_mode_validation.go makes sense or if current split is intentional
3. If consolidation is appropriate, merge validation logic into a single strict_mode_validation.go
4. Move validateStrictMode and related methods to the consolidated file
5. Update imports and references
6. Verify all tests pass

Files to Modify

• Review: pkg/workflow/strict_mode.go
• Review: pkg/workflow/validation_strict_mode.go
• Potentially create: pkg/workflow/strict_mode_validation.go
• Update: Any files referencing these validation methods

Acceptance Criteria

• Validation logic properly organized following codebase patterns
• No duplication between strict_mode.go and validation files
• All validation methods in appropriate validation file(s)
• All imports correctly updated
• All existing tests pass
• Consistent naming with other *_validation.go files

Estimated Effort

1-2 hours

Benefits

• Improved consistency with validation file naming patterns
• Better organization of validation logic
• Easier to locate strict mode validation code
• Reduced confusion about where validation logic should live

Note

This task requires careful review of the existing validation_strict_mode.go file to determine the best consolidation approach.
Related to #3478

AI generated by Plan Command for #3478