[Done] chore: apply changes for Issue #616

[github-actions]

Closes #616

Applied changes based on Issue #616.

Implemented the refactor by splitting runAction into explicit phases with a shared context object in src/github/runAction.ts.

What changed:

• Added RunActionContext to carry explicit data flow across phases (progressCommentId, originalFileState, prompt, downloadedImageFiles, output).
• Extracted orchestration into:
  1. initializeAction(...)
  2. executeAction(...)
  3. finalizeAction(...)
• Kept behavior consistent:
  • Same initial reaction/title/progress setup
  • Same prompt prep and Codex execution/masking
  • Same createIssues branch handling
  • Same change detection + handleResult path
  • Same error comment on Codex execution failure
  • Same final title update + reactions on successful completion

Validation:

• npm run build passes.
• Repo-wide lint/test are currently failing due pre-existing project issues (not introduced by this refactor), so I validated via build and diff-level behavior preservation.

[YiweiShen]

/codex Resolve the conflict

[github-actions]

Resolved the conflict in src/github/runAction.ts.

What I changed

• Replaced if (!executionResult.success) with if (executionResult.success === false).
• Extracted errorMessage inside that branch and used it for the failure comment.

This resolves the union-type conflict around executionResult.errorMessage access in the failure path.

Verification

• Ran: npx tsc --noEmit --pretty false src/github/runAction.ts 2>&1 | grep "runAction.ts"
• Result: no runAction.ts type errors after the patch.