Fix: Restore result-encoding in detect-invalid-ci-commands workflow

[justin808]

Summary

The result-encoding: string parameter was accidentally removed from .github/workflows/detect-invalid-ci-commands.yml in commit 4970d21 ("Fix JSON parsing error in detect-invalid-ci-commands workflow").

This removal may cause issues with the workflow's JSON parsing logic.

Current State (on master)

The workflow has:

- name: Check for similar commands
  id: check_command
  uses: actions/github-script@v7
  with:
    script: |
      // ... script content ...
      return { shouldRespond: false };
    result-encoding: string

What was removed

In branch jg/swc-detection-fix, commit 4970d21 removed the result-encoding: string line.

Fix Required

Restore the result-encoding: string parameter if it's needed for proper JSON parsing, or verify that the workflow works correctly without it.

Context

This change was bundled with an unrelated SWC detection feature PR. It should be handled separately.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and agent prompts for this issue.

• Create Plan

Examples

• Example 1
• Example 2

🔗 Related PRs

#1714 - Remove compromised GH action [merged]
shakacode/react-webpack-rails-tutorial#628 - Require comment trigger for Review Apps [merged]
#2037 - Add workflow to detect invalid CI command attempts [merged]

👤 Suggested Assignees

• alexeyr-ci2
• Judahmeek
• justin808

---

🧪 Issue enrichment is currently in early access.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

[justin808]

Deep-dive triage pass (2026-03-22):

• Domain: ci/tooling
• Labels/Priority signals: P3
• Current PR coverage: no open PR currently linked
• Proposed next step: add this to the new triage PR stack so it has explicit implementation ownership.

Question: Should this run in the CI/tooling maintenance wave, or be deferred behind release-critical runtime work?

[justin808]

Closing — the detect-invalid-ci-commands.yml workflow already has result-encoding: string on the check_command step and downstream output reading works correctly.