[aw-compat] Common syntax errors: reserved aw_context input + codex/bash-allowlist mismatch (react-router) #66082

Overview

Two recurring, user-facing syntax/configuration mistakes surfaced repeatedly within remix-run/react-router's workflow set during today's compatibility audit. Both are already caught correctly by the compiler and (for one) an existing codemod, but both point at a shared scaffold/template that is out of date.

Pattern 1 — reserved workflow_dispatch.inputs.aw_context

Affected files (same repo, identical error, 5 occurrences): aw-command-implement.md, aw-command-iterate.md, aw-command-review-issue.md, aw-command-review-proposal.md, aw-comment-router.md

error: on.workflow_dispatch.inputs.aw_context is reserved and managed by the compiler; remove it from workflow inputs

All 5 files fail with the exact same message, which strongly suggests they were generated from a shared command-workflow scaffold authored before aw_context became a compiler-reserved input name. gh aw fix --write does not remove this input automatically.

Suggested remediation for workflow authors: delete aw_context from on.workflow_dispatch.inputs in any command-style workflow scaffold — the compiler now manages and injects this value itself.

Pattern 2 — engine: codex combined with bash command allow-listing

Affected files (same repo, 4 occurrences): aw-command-review-issue.md, aw-command-review-proposal.md, aw-command-review-pull-request.md, aw-comment-router.md

✗ codemod bash-allowlist-unsupported-engine-guided-error failed: engine 'codex' does not support
bash command allow-listing: 'bash: false' is silently ignored at runtime for this engine.
Manual fix required: switch to an engine that enforces the allow-list (claude, copilot, gemini, pi),
or replace the configuration with 'bash: ["*"]' to make the unrestricted access explicit.

This is not a bug — the existing codemod correctly detects the mismatch and intentionally requires a human decision rather than silently guessing. It is included here only because it is a recurring configuration mistake worth documenting: authors scaffolding new command workflows with engine: codex should be aware that bash allow-lists are silently ignored by that engine at runtime.

Why this matters

Both patterns point to the same root cause: a stale command-workflow template/scaffold used across 4-5 files in one repo. Fixing the template once (removing aw_context from inputs, and either switching the documented example engine away from codex or clarifying the allow-list caveat) would prevent this from recurring as the pattern gets copied to new workflows or new repos.

Next actions

• No gh-aw compiler change needed for Pattern 2 (working as intended).
• Consider whether gh aw fix should auto-strip reserved workflow_dispatch.inputs.aw_context for Pattern 1 — tracked in the companion missing-codemod issue discussion.

Generated by 🔧 Daily AW Cross-Repo Compile Check · claude · agent · 751.6 AIC · ⌖ 7.23 AIC · ⊞ 6.4K · ◷

• expires on Oct 13, 2026, 1:17 AM UTC-08:00