Overview
Two codemod gaps recurred across ≥2 independently-verified gh-aw repos during
the daily cross-repo compilation audit (build 0368d98). Both leave
gh aw fix --write unable to fully repair a --strict compile failure.
1. sandbox-runtime-profiles codemod hard-errors on gvisor+privileged combo
Seen in github/gh-aw-mcpg (readonly-stress-gvisor.md) and
github/gh-aw-firewall (4 files: smoke-gvisor-build-test.md,
smoke-gvisor-claude.md, smoke-gvisor-codex.md, smoke-gvisor.md).
✗ Error processing smoke-gvisor.md: codemod sandbox-runtime-profiles failed:
sandbox.agent.runtime: gvisor combined with privileged security options
(sudo/legacy-security) is no longer supported. Choose one runtime profile:
keep 'runtime: gvisor' for strict network isolation and remove 'sudo'/
'legacy-security', or use 'runtime: docker-sudo-iptables' for the privileged
iptables profile with host access
Suggested fix: rather than aborting the file's fix pass, auto-migrate to
runtime: docker-sudo-iptables (preserves the privileged/sudo intent that was
present in the original config) and continue, or at minimum let --write
skip just this rule with a clear per-file warning instead of leaving the file
completely untouched.
2. No codemod for tools.bash required when min-integrity: none
Seen in chrizbo/agentics-beyond-code (weekly-status.md) and
verkyyi/github-agent-runner (weekly-research.md, plus a similar
daily-report workflow).
strict mode: when 'tools.github.min-integrity' is set to 'none', 'tools.bash'
must be explicitly specified so that shell access is intentional
gh aw fix --write reports "No fixes needed" for these files even though
compilation still fails — there's no registered codemod for this rule.
Suggested fix: add a codemod that inserts tools.bash: false when
tools.github.min-integrity: none is set and tools.bash is absent. This
preserves current behavior (no bash was configured before) while satisfying
the new strict-mode requirement, so it's safe to apply automatically.
Representative repos
- github/gh-aw-firewall (130★)
- github/gh-aw-mcpg (159★)
- chrizbo/agentics-beyond-code (21★)
- verkyyi/github-agent-runner (10★)
Generated by 🔧 Daily AW Cross-Repo Compile Check · agent · 165.4 AIC · ⌖ 7.88 AIC · ⊞ 7.3K · ◷
Overview
Two codemod gaps recurred across ≥2 independently-verified gh-aw repos during
the daily cross-repo compilation audit (build
0368d98). Both leavegh aw fix --writeunable to fully repair a--strictcompile failure.1.
sandbox-runtime-profilescodemod hard-errors on gvisor+privileged comboSeen in
github/gh-aw-mcpg(readonly-stress-gvisor.md) andgithub/gh-aw-firewall(4 files:smoke-gvisor-build-test.md,smoke-gvisor-claude.md,smoke-gvisor-codex.md,smoke-gvisor.md).Suggested fix: rather than aborting the file's fix pass, auto-migrate to
runtime: docker-sudo-iptables(preserves the privileged/sudo intent that waspresent in the original config) and continue, or at minimum let
--writeskip just this rule with a clear per-file warning instead of leaving the file
completely untouched.
2. No codemod for
tools.bashrequired whenmin-integrity: noneSeen in
chrizbo/agentics-beyond-code(weekly-status.md) andverkyyi/github-agent-runner(weekly-research.md, plus a similardaily-report workflow).
gh aw fix --writereports "No fixes needed" for these files even thoughcompilation still fails — there's no registered codemod for this rule.
Suggested fix: add a codemod that inserts
tools.bash: falsewhentools.github.min-integrity: noneis set andtools.bashis absent. Thispreserves current behavior (no bash was configured before) while satisfying
the new strict-mode requirement, so it's safe to apply automatically.
Representative repos