[aw] Smoke Bounded Agents gVisor is missing required data

Workflow Failure

Workflow: Smoke Bounded Agents gVisor
Branch: lpcox-create-auth-doctor
Run: https://github.com/github/gh-aw-firewall/actions/runs/30860664908

Warning

Missing Data Reported: The agent reported missing data during execution.

Missing Data:

bounded-agent result: The bounded-agent gVisor enclave smoke test was invoked against github/gh-aw with schema {"type":"boolean"} per the documented CLI usage, but returned {"status":"error"} instead of a boolean result.
- Context: Error responses are indistinguishable by design (could be launch failure, runtime not registered, budget exhaustion, timeout, etc.) per the bounded-agent SKILL.md contract. The socket /run/awf-bounded-agent/broker.sock exists and env vars (AWF_BOUNDED_AGEN
  [Content truncated due to length]
- Alternatives: Re-run the smoke test workflow; check broker/enclave logs on the host for gVisor (runsc) registration or API-proxy route failures, since none of that is inspectable from within the agent container.

Warning

Engine Failure: The copilot engine terminated unexpectedly.

Last agent output:

  └ 2 lines...
● missing_data (MCP: safeoutputs) · data_type: "bounded-agent result", reason: "The bounded-agent g…
  └ {"result":"success"}
I invoked the `bounded-agent` skill against `github/gh-aw` with a boolean schema (`{"type":"boolean"}`) asking whether `go.mod` exists at the repo root, exactly per the documented CLI contract. Both attempts returned `{"status":"error"}` rather than `true`/`false`. Since the smoke test only passes when the enclave returns `true`, and errors are indistinguishable by design (could be gVisor runtime registration, launch failure, budget, or timeout), I reported this via `missing_data` rather than a false `noop PASS true`.
Changes   +0 -0
Duration  2m 7s
Tokens    ↑ 384.5k • ↓ 1.9k • 342.5k (cached)
Run 'docker run --help' for more information
Run 'docker run --help' for more information
Run 'docker run --help' for more information

Action Required

Assign this issue to an agent to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/github/gh-aw-firewall/actions/runs/30860664908

Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the agentic-workflows prompt.

Start your agent
Load the agentic-workflows skill from .github/skills/agentic-workflows/SKILL.md or https://github.com/github/gh-aw/blob/main/.github/skills/agentic-workflows/SKILL.md
Type debug the agentic workflow smoke-bounded-agents-gvisor failure in https://github.com/github/gh-aw-firewall/actions/runs/30860664908

Tip

Stop reporting this workflow as a failure

To stop a workflow from creating failure issues, set report-failure-as-issue: false in its frontmatter:

safe-outputs:
  report-failure-as-issue: false

Generated from Smoke Bounded Agents gVisor · 19.2 AIC · ◷

expires on Aug 10, 2026, 11:05 PM UTC