Summary

With Waza 0.33.0 and the copilot-sdk executor, a task-level fixture declared as inputs.context.fixture does not appear to be copied into the task workspace. The agent starts in a fresh temp workspace and file discovery calls do not find the fixture files.

Minimal shape

# eval.yaml
name: fixture-copy-repro
skill: qa
config:
  executor: copilot-sdk
  model: claude-haiku-4.5
tasks:
  - "tasks/*.yaml"

# tasks/behavior-001.yaml
id: behavior-001
inputs:
  context:
    fixture: "fixtures/demo"
  prompt: "Inspect repository files with glob/read tools and summarize what you find."

Expected: files from fixtures/demo are available in the fresh task workspace, or Waza schema validation rejects inputs.context.fixture as unsupported.

Actual: the run creates a temp workspace, but tool calls report no usable fixture files. A downstream eval suite saw glob/view attempts against the temp workspace rather than copied fixture content.

Environment

• Waza: 0.33.0
• Executor: copilot-sdk
• Model used for repro: claude-haiku-4.5

Downstream workaround

For now, downstream is wiring only one demonstration task to the fixture and is not blanket-migrating evals until fixture materialization is confirmed or documented as unsupported.