What Changed

• Updated documentation comments to reflect configuration now being loaded from modular .github/env/*.env files instead of .env.base and .env.custom files (updated in header comment and environment variables section)
• Added conditional execution to the load-env job to only run for fork PRs using if: ${{ github.event.pull_request.head.repo.full_name != github.repository }}
• Added comment clarifying that same-repo PRs are handled by pull-request-management.yml workflow
• Added visual separator line (════════════════════════════════════════════════════════════════════════════════) in the header
• Minor whitespace adjustments in security scanner justification comment block for improved alignment

Why It Was Necessary

• The conditional execution prevents the fork workflow from running unnecessarily on same-repository PRs, improving workflow efficiency and reducing redundant job execution
• Documentation updates reflect the migration to a modular environment configuration system, ensuring developers have accurate information about where configuration is managed
• The visual separator improves readability and organization of the extensive security documentation in the workflow header

Testing Performed

• Workflow syntax validation through GitHub Actions schema
• Verification that the conditional logic correctly identifies fork vs same-repo PRs using github.event.pull_request.head.repo.full_name comparison
• Review of documentation changes for accuracy and consistency across all references to configuration file locations

Impact / Risk

• Low Risk: Changes are primarily documentation updates and a conditional guard that prevents unnecessary execution
• No Breaking Changes: The workflow will continue to function for fork PRs as intended; same-repo PRs will simply skip this job (as they should)
• Improved Efficiency: Prevents duplicate workflow runs and clarifies the separation of concerns between fork and same-repo PR workflows