Suggested test: copilot/sandbox-filesystem-allow-write-kebab-case #19040

Motivation

github/gh-aw#64302 — Sandbox frontmatter fields are now normalized to kebab-case (e.g. allowWrite → allow-write, authHeader → auth-header, entrypointArgs → entrypoint-args). Camel-cased fields are rejected without parser aliases; gh aw fix provides migration. No current test exercises the kebab-case sandbox filesystem fields at runtime.

Proposed test

• Workflow file: test-copilot-sandbox-filesystem-allow-write.md
• Trigger: workflow_dispatch
• Engine: copilot
• Safe output: create-issue
• Variant: standard

Minimal test prompt sketch

Configure sandbox.agent.config.filesystem.allow-write: [/tmp/e2e-allowed] (kebab-case). Ask the agent to write a file under /tmp/e2e-allowed and confirm success, then create one issue reporting whether the write succeeded — validating the kebab-case field compiles and is honored at runtime.

New fixtures or secrets needed

None.

Notes

Existing sandbox tests (test-copilot-sandbox-runtime-profile.md, test-copilot-sandbox-exclude-env.md) don't touch filesystem.allow-write or other renamed fields. This is primarily a compiler/schema change, so the test's main value is confirming the new canonical field name compiles and behaves correctly end-to-end; verifying the old camelCase form is rejected would require a compile-failure assertion, which may need harness support — flagging as an open question if that path is not currently distinguishable from a runtime failure.

Generated by 🔍 Suggest New E2E Tests · copilot · auto · 69.9 AIC · ⌖ 5.56 AIC · ⊞ 8.5K · ◷