[plan] Add documentation headers to helper files

[github-actions]

Objective

Add clear file header documentation to helper files that lack it, following the pattern established in config_helpers.go.

Context

Several helper files lack documentation explaining their purpose and usage:

• map_helpers.go (2 functions)
• git_helpers.go (1 function)
• engine_helpers.go (6 functions)
• close_entity_helpers.go (4 functions)
• update_entity_helpers.go (4 functions)
• prompt_step_helper.go (2 functions)

The file config_helpers.go serves as an excellent example with clear documentation of purpose and usage patterns.

Approach

1. Review existing documentation:

   • Study pkg/workflow/config_helpers.go as the documentation template
   • Identify what makes it clear and helpful

2. Add file headers to each helper file with:

   • Brief purpose statement
   • When to use this helper (vs alternatives)
   • Key patterns or conventions
   • Example usage if appropriate

3. Document the "why":

   • Explain why the helper file exists
   • Clarify separation from main implementation files

Files to Modify

• pkg/workflow/map_helpers.go - Add header documentation
• pkg/workflow/git_helpers.go - Add header documentation
• pkg/workflow/engine_helpers.go - Add header documentation
• pkg/workflow/close_entity_helpers.go - Add header documentation
• pkg/workflow/update_entity_helpers.go - Add header documentation
• pkg/workflow/prompt_step_helper.go - Add header documentation

Acceptance Criteria

• Each helper file has a clear file header comment
• Documentation explains purpose and usage patterns
• Documentation style consistent with config_helpers.go
• Comments explain when to use vs alternatives (where applicable)
• No functional changes (documentation only)
  Related to [refactor] Semantic Function Clustering Analysis - Code Organization Opportunities #7136

AI generated by Plan Command for #7136