Fix lock/unlock issue scripts to support both require() and inline modes

[Copilot]

The lock-issue and unlock-issue scripts needed to support two execution modes: require() mode (when used with setup action) and inline mode (when bundled and embedded in YAML).

Changes

Scripts (lock-issue.cjs, unlock-issue.cjs):

• Added module.exports = { main } for require() compatibility
• Scripts only export the main function without auto-execution
• Importer (require() caller) is responsible for calling await main()

Compiler (compiler_activation_jobs.go):

• Bundle lock-issue script before inlining using BundleJavaScriptWithMode()
• Bundler strips module.exports via removeExports() for inline mode
• Compiler adds await main(); after bundling for inline mode execution

Execution Modes

Require mode (setup action - primary):

const { main } = require('/tmp/gh-aw/actions/lock-issue.cjs');
await main(); // Importer calls main

Inline mode (direct YAML embedding - fallback):

script: |
  // Bundled script with module.exports removed
  async function main() { /* ... */ }
  await main();  // Compiler adds this

The scripts now correctly support both execution modes. Setup action files only export the main function, allowing the importer to control execution timing.

Original prompt

Fix the inlining of the lock issue, unlock issue scripts to support the require + exported main function scheme.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[pelikhan]

@copilot do not call main, let importer call it

[Copilot]

Removed await main() from lock-issue.cjs. The setup action files now only export the main function - the importer calls it. (commit 75b7509)

[pelikhan]

@copilot do not call main, let importer call it

[Copilot]

Removed await main() from unlock-issue.cjs. The setup action files now only export the main function - the importer calls it. (commit 75b7509)