Add Pi offline regression coverage to wasm golden engine test

[Copilot]

The CGO workflow failure came from a stale Pi wasm golden expectation after Pi engine output started including PI_OFFLINE: 1. Both the test and build-wasm jobs failed on the same TestWasmGolden_AllEngines/pi mismatch.

• Root cause captured in a focused assertion

  • Adds a Pi-specific regression check in TestWasmGolden_AllEngines to require PI_OFFLINE: 1 in compiled output.
  • Keeps the behavior under direct test instead of relying only on a broad golden diff.

• Scope

  • Test-only change in /home/runner/work/gh-aw/gh-aw/pkg/workflow/wasm_golden_test.go
  • No production workflow compilation logic changes

if eng.name == "pi" {
	require.Contains(t, yamlOutput, "PI_OFFLINE: 1")
}

• Fixes [CGO] Workflow failure on main - Run #18537 #47253

[Copilot]

Pull request overview

Adds focused regression coverage ensuring Pi wasm output includes offline mode.

Changes:

• Asserts Pi compilation emits PI_OFFLINE: 1.
• Retains existing all-engine golden validation.

Show a summary per file

File	Description
pkg/workflow/wasm_golden_test.go	Adds the Pi offline-mode assertion.

Review details

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Medium

[github-actions]

🎉 This pull request is included in a new release.

Release: v0.83.0