Remove Claude engine output.txt handling as CLI no longer produces this file

[Copilot]

The Claude CLI no longer produces an output.txt file, but the Claude agentic engine was still declaring it as an output file. This caused the workflow compiler to generate unnecessary upload and cleanup steps for a file that doesn't exist.

Problem

When using the Claude engine, generated workflows included these unnecessary steps:

• Upload engine output files step attempting to upload output.txt
• Clean up engine output files step attempting to remove output.txt
• agent_outputs artifact creation for non-existent files

This resulted in workflows that tried to handle files that the Claude CLI no longer produces, leading to unnecessary complexity and potential confusion.

Solution

Updated ClaudeEngine.GetDeclaredOutputFiles() to return an empty list instead of []string{"output.txt"}. This prevents the workflow compiler from generating the upload and cleanup steps since there are no declared output files.

The change is minimal and surgical:

• Only affects Claude engine output file declarations
• Preserves all other Claude engine functionality
• Maintains GITHUB_AW_SAFE_OUTPUTS functionality for safe outputs handling
• Updated corresponding tests to reflect the new expected behavior

Verification

• All existing tests pass with updated expectations
• Manual workflow compilation confirms no more unnecessary upload/cleanup steps
• Generated workflows are cleaner and more efficient
• Safe outputs functionality remains fully intact

This fix aligns the code with the current behavior of the Claude CLI and eliminates unnecessary workflow steps.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.contoso.com
  • Triggering command: /tmp/go-build15137770/b279/cli.test -test.testlogfile=/tmp/go-build15137770/b279/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true (dns block)
  • Triggering command: /tmp/go-build1084126533/b279/cli.test -test.testlogfile=/tmp/go-build1084126533/b279/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true (dns block)
  • Triggering command: /tmp/go-build1885715907/b279/cli.test -test.testlogfile=/tmp/go-build1885715907/b279/testlog.txt -test.paniconexit0 -test.timeout=10m0s -test.v=true (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.