[plan] Create smoke test workflow to validate common development tool availability

[github-actions]

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