Fix CI test failure caused by go test -json piping

[Copilot]

CI test job was failing with exit code 1 despite all tests passing. The issue: go test -json | tee with set -o pipefail causes intermittent pipeline failures due to JSON output buffering.

Changes

Separated test execution from JSON artifact generation:

Before:

- name: Run unit tests with coverage
  run: |
    set -o pipefail
    go test -v -parallel=8 -timeout=3m -run='^Test' -tags '!integration' -coverprofile=coverage.out -json ./... | tee test-result-unit.json
    go tool cover -html=coverage.out -o coverage.html

After:

- name: Run unit tests with coverage
  run: |
    set -o pipefail
    go test -v -parallel=8 -timeout=3m -run='^Test' -tags '!integration' -coverprofile=coverage.out ./...
    go tool cover -html=coverage.out -o coverage.html

- name: Generate JSON test results  
  if: always()
  run: |
    go test -json -run='^Test' -tags '!integration' ./... > test-result-unit.json 2>&1 || true

Main test command now uses -v (human-readable output) without piping. JSON results generated separately with if: always() to ensure artifact creation regardless of test outcome.

Original prompt

Fix the failing GitHub Actions workflow test
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 61943541516
Job URL: https://github.com/githubnext/gh-aw/actions/runs/21499856490/job/61943541516

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.