Update JavaScript developer instructions to clarify export pattern for top-level .cjs files

[Copilot]

The JavaScript refactoring skill documentation incorrectly showed top-level .cjs scripts calling await main() directly. The bundler automatically injects this call during inline execution, so scripts should only export main.

Changes

• Added "Top-Level Script Pattern" section explaining correct pattern with side-by-side comparison:

  // ✅ Correct - export only
  async function main() {
    core.info("Running the script");
  }
  module.exports = { main };
  
  // ❌ Incorrect - don't call it
  await main(); // Bundler handles this

• Updated all code examples in Step 5 and Complete Example sections to use module.exports = { main } without calling await main()

• Added clarification to Pattern 2 (Main Workflow Script) explicitly stating scripts must export but not call main

• Documented rationale: Bundler injects execution, enables testing by allowing imports without execution, maintains consistency with codebase (create_issue.cjs, add_comment.cjs, etc.)

Context

This pattern enables:

• Tests to import and call main() with mocks without side effects
• Bundler to inject await main() at execution time in GitHub Actions
• Clean separation between module definition and execution

Original prompt

Update JavaScript developer instruction to create top level .cjs file that export main but do not call it.

---

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