[log] Add debug logging to safe-outputs config parsers and maintenance conditions

[github-actions]

Add meaningful debug log calls to 5 workflow package files. Three of these files had logger variables already declared but never used directly; two others had no logging at all.

Changes

• pkg/workflow/maintenance_conditions.go — New maintenanceConditionsLog logger + log calls in buildNotForkAndScheduledOrOperation (logs the operation name) and buildRunOperationCondition (logs excluded operations list). These condition builders control maintenance job execution, so knowing which conditions are being assembled helps trace why a maintenance job runs or is skipped.

• pkg/workflow/merge_pull_request.go — Entry log when parsing merge-pull-request config and result log showing requiredLabels, allowedLabels, and allowedBranches. The logger was already declared but unused.

• pkg/workflow/mark_pull_request_as_ready_for_review.go — Entry log at parse time and result log showing the resolved target. Logger was already declared but unused.

• pkg/workflow/update_issue_helpers.go — Entry log in parseUpdateIssuesConfig. Logger was already declared but unused.

• pkg/workflow/update_release.go — Entry log in parseUpdateReleaseConfig. Logger was already declared but unused.

Test plan

• make build — no compilation errors
• go vet ./pkg/workflow/... — no vet issues
• Max 5 files modified
• No test files modified
• Logger arguments have no side effects (only struct fields and slice values)
• No duplicate logging with existing logs (existing logs are in the helper functions called downstream)

🤖 Generated with [Claude Code]((claude.com/redacted)

Generated by Go Logger Enhancement · ● 1.1M · ◷

• expires on Apr 23, 2026, 9:36 PM UTC