Allow cache-memory writes in GitHub MCP Structural Analysis sandbox

[Copilot]

The GitHub MCP Structural Analysis workflow was emitting missing_data(cache_memory) because /tmp/gh-aw/cache-memory/ was read-only during agent execution, preventing both historical reads and daily snapshot writes (mcp_analysis.jsonl). This change makes cache-memory explicitly writable for the agent so 30-day trending data can persist across runs.

• Root-cause alignment

  • Added explicit sandbox filesystem write allowance for the cache-memory path used by this workflow’s prompt and persistence logic.

• Workflow source update (.md)

  • Extended sandbox.agent config to include:
    • filesystem.allowWrite: [/tmp/gh-aw/cache-memory]

• Compiled workflow update (.lock.yml)

  • Recompiled generated workflow so runtime sandbox config reflects the markdown source change.

sandbox:
  agent:
    runtime: cloud-hypervisor
    config:
      filesystem:
        allowWrite:
          - /tmp/gh-aw/cache-memory

• Fixes [aw] GitHub MCP Structural Analysis is missing required data #55383

[github-actions]

Thanks for fixing the cache-memory sandbox issue! 🎯

This PR correctly addresses issue #55383 by adding the necessary filesystem write permissions for the cache-memory directory. The fix is focused and properly maintains both the markdown source and compiled lock file in sync.

Minor improvement: Since this modifies sandbox permissions (a critical security surface), consider adding validation in your test workflow to confirm the directory is writable before the agent starts. This would catch similar issues earlier.

Add a validation step to github-mcp-structural-analysis.md that checks if /tmp/gh-aw/cache-memory/ is writable before the agent phase begins. If not writable, exit with a clear error message explaining the sandbox configuration issue.

Generated by ✅ Contribution Check · copilot · auto · 60.8 AIC · ⌖ 10.4 AIC · ⊞ 9.3K · ◷