Create smoke test workflow to validate common development tool availability

[Copilot]

• Understand the requirements for the smoke test workflow
• Create .github/workflows/smoke-test-tools.md smoke test workflow
• Compile workflow with gh aw compile to generate .lock.yml
• Verify compiled workflow is valid
• Create specs/agent-container-testing.md documentation
• Run formatting and linting validation
• Run code review and security checks
• Address PR feedback: Add Go, Java, .NET runtimes
• Address PR feedback: Remove wget from tests

Summary

Created a smoke test workflow that validates common development tools in the agent container:

Files Created

• .github/workflows/smoke-test-tools.md - Smoke test workflow for 12 common tools
• .github/workflows/smoke-test-tools.lock.yml - Compiled workflow
• specs/agent-container-testing.md - Documentation for the smoke test

Tested Tools (12 total)

1. bash - Shell scripting
2. sh - POSIX shell
3. git - Version control
4. jq - JSON processing
5. yq - YAML processing
6. curl - HTTP requests
7. gh - GitHub CLI
8. node - Node.js runtime
9. python3 - Python runtime
10. go - Go runtime
11. java - Java runtime
12. dotnet - .NET runtime (C#)

Runtimes Configured

runtimes:
  node:
    version: "20"
  python:
    version: "3.11"
  go:
    version: "1.24"
  java:
    version: "21"
  dotnet:
    version: "8.0"

Triggers

• Schedule: Every 12 hours
• Manual: workflow_dispatch
• PR Label: smoke label on pull requests

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[plan] Create smoke test workflow to validate common development tool availability</issue_title>
<issue_description>## Objective

Create a minimal smoke test workflow that validates commonly-used development tools are accessible in the agent container environment.

Context

Building on #11975 (integration test suite), we need a quick smoke test that can run in CI to catch regressions. This should test the most common workflow scenarios:

• Running shell commands (bash, sh)
• Using version control (git)
• Processing JSON/YAML (jq, yq)
• Making HTTP requests (curl, wget)
• Using GitHub CLI (gh)

Approach

1. Create .github/workflows/smoke-test-tools.md with simple tests:

   ---
   engine: copilot
   name: Agent Container Smoke Test
   ---
   
   # Smoke Test Tools
   
   Test that common development tools are available:
   
   1. Run `git --version` and verify output
   2. Run `jq --version` and verify output
   3. Run `curl --version` and verify output
   4. Run `gh --version` and verify output
   5. Run `yq --version` and verify output
   6. Run `node --version` and verify output
   7. Run `python3 --version` and verify output

2. Compile workflow with gh aw compile
3. Add to CI pipeline to run on every PR
4. Document expected output and failure modes

Files to Create/Modify

• Create: .github/workflows/smoke-test-tools.md (smoke test workflow)
• Create: .github/workflows/smoke-test-tools.lock.yml (compiled workflow)
• Modify: .github/workflows/ci.yml (add smoke test job if needed)
• Update: specs/agent-container-testing.md (document smoke test)

Acceptance Criteria

• Smoke test workflow runs successfully in CI
• Tests cover at least 7 common development tools
• Test failures provide clear error messages
• Workflow executes in under 2 minutes
• Documentation explains how to run locally
• Test serves as early warning for mounting regressions

Related

Complements #11975 with quick smoke test before comprehensive integration tests
Related to #11970

AI generated by Plan Command for #11970

Comments on the Issue (you are @copilot in this section)

Custom agent used: agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing

• Fixes [plan] Create smoke test workflow to validate common development tool availability #12377

---

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

[Mossaka]

@copilot Add more, Go, Java, C#, etc.

Also add those runtimes into runtimes: frontmatter

[Copilot]

Added Go (1.24), Java (21), and .NET (8.0) runtimes to both the test cases and the runtimes: frontmatter configuration. The workflow now tests 12 tools total. (e6b0433)

[Mossaka]

@copilot remove this

[Copilot]

Removed wget from the HTTP tools section. (e6b0433)