Designer Drift AuditMissing mappings and outdated standalone designer guidance #65750

Missing Trigger Mappings

• Source: .github/aw/triggers.md (standard events, command event identifiers, semi-active example).
• Missing from: Both — playbook's .github/aw/designer-mappings.md and agent file.
• Details: The mapping table has no direct push or issue_comment mapping. Its generic slash-command row does not explain issue_comment, pull_request_comment, and pull_request_review_comment event scoping. The agent's frontmatter list only names issues, pull requests, schedules, and manual dispatch, with no link to the full trigger guidance.
• Suggested fix: Add push/comment mappings and command event-scoping guidance; route the agent to the shared trigger table. Keep pull_request_comment explicitly identified as a command-scoping identifier, not a standalone Actions event.

Missing Safe Output Mappings

• Source: .github/aw/safe-outputs.md, its content/automation references, and /tmp/gh-aw/data/all-safe-output-types.txt; corroborated with pkg/workflow/safe_output_handlers.go and pkg/workflow/js/safe_outputs_tools.json.
• Missing from: Both.
• Details: Missing mappings for call-workflow, approve-workflow-run, ado-upload-workitem-attachment, and upload-code-coverage. Registered tools ledger_append and ledger_request_compaction also lack a designer route explaining their tools.ledger configuration. The standalone agent only gives three output examples and does not reference the complete mapping.
• Suggested fix: Add intent-to-output rows for reusable workflow fan-out, pending-run approval, work-item attachments, and coverage publishing; add a ledger guidance route. Preserve the distinction between configuration keys and runtime tool names. Existing repo-memory guidance covers push_repo_memory; this is not a missing output.

Network Identifier Coverage

• Source: .github/aw/network.md (ecosystem identifiers and engine domain sets).
• Missing from: Both, at the mapping/guidance level.
• Details: Common ecosystems and all listed less-common package ecosystems are covered directly or by an explicit reference. However, copilot-vendor, copilot, claude, codex, gemini, pi, pi-base, and threat-detection have no explicit mapping or engine-domain explanation. The standalone agent supplies no ecosystem mapping or reference route.
• Suggested fix: Add a compact route to the engine-domain section explaining automatic engine transport and the compatibility alias; do not indiscriminately add these identifiers to generated allowlists. Have the agent use the same network guidance.

Optional Frontmatter Coverage

• Source: .github/aw/syntax.md → syntax-core.md and syntax-agentic.md.
• Missing from: Both.
• Details: The generation template and interview omit explicit selection guidance for model, max-turns, max-ai-credits, max-daily-ai-credits, max-turn-cache-misses, models, and user-rate-limit. Runner choices such as runs-on-slim/runner and the pre-agent-steps hook also have no template guidance. The agent's abbreviated frontmatter list does not cover these fields. Their introduction dates cannot be established from the supplied history.
• Suggested fix: Add optional decision guidance for budgets, model policies, rate limits, runner requirements, and setup timing, linked to the canonical syntax pages. Keep default-valued and irrelevant fields omitted; this is a discoverability gap, not proof that the minimal skeleton is invalid.

Pattern and Optimization Routing

• Source: .github/aw/patterns.md, .github/aw/subagents.md, .github/aw/token-optimization.md, and .github/aw/create-agentic-workflow.md.
• Missing from: Agent file only.
• Details: The playbook's shared table covers all 20 named patterns. The standalone .github/agents/interactive-agent-designer.agent.md neither names those patterns nor routes to the pattern/playbook references. Its optimization guidance stops at concision and cache memory, without the playbook's DataOps, gh-proxy, and smaller-model sub-agent guidance.
• Suggested fix: Route workflow design/configuration requests from the agent to designer.md, designer-mappings.md, and the creation guide, including their pattern and optimization references, instead of maintaining a separate abbreviated knowledge surface.

Stale Field Placement Guidance

• Source: .github/aw/syntax.md → syntax-agentic.md (memory fields), corroborated by .github/aw/memory.md.
• Missing from: Agent file (correct nesting guidance).
• Details: The agent's “For Workflow Configuration (Frontmatter)” section lists cache-memory: alongside top-level fields without stating that it belongs under tools:; its optimization section repeats the bare field. Current syntax explicitly places it under tools. No removed documentation path was established.
• Suggested fix: Write tools.cache-memory explicitly and reference the memory guide, avoiding a generated top-level cache-memory field.