Designer Drift Report — 2026-10-06
Summary
Seven drift items were found across six categories. The designer skill's shared mappings provide substantial coverage, but several operations and generation options are missing; the interactive agent also lacks a route to the current reference guidance.
Drift Items
View Drift Items by Category
1. Missing Trigger Coverage
- Source:
.github/aw/triggers.md (Standard GitHub Events and command/incident sections)
- Missing from: both
- Details:
push appears in the reference but has no entry in the skill's delegated .github/aw/designer-mappings.md trigger table. The agent file lists only issues, pull_request, schedule, and workflow_dispatch; it omits push, workflow_run, deployment_status, slash_command, and label_command, and does not link to the shared mappings.
- Suggested fix: Add a branch-scoped push mapping and route the agent's frontmatter design flow through the shared trigger table.
2. Missing Safe Output Types
- Source:
.github/aw/safe-outputs.md → safe-outputs-content.md / safe-outputs-automation.md; /tmp/gh-aw/data/all-safe-output-types.txt; .github/aw/test-coverage.md; .github/aw/memory.md
- Missing from: both
- Details: The shared safe-output mapping omits
ado-upload-workitem-attachment, approve-workflow-run, call-workflow, and upload-code-coverage. It also lacks guidance for the registered ledger_append and ledger_request_compaction tools. The agent supplies only three example output types and no reference to the complete mappings. ledger_mutation is a trusted audit handler, not a user-selectable output; push_repo_memory is already represented through repo-memory and is not counted as missing.
- Suggested fix: Add intent-to-operation rows for the four declarative outputs; add ledger routing through
tools.ledger and its append/compaction documentation rather than inventing corresponding safe-output frontmatter keys. Link the agent to this table.
3. Network Identifier Coverage
- Source:
.github/aw/network.md (Ecosystem Identifiers and Engine Domain Sets)
- Missing from: both, with different scope
- Details: The skill's mappings cover common ecosystems and explicitly route less common ecosystems to the reference. They do not explain the listed transport identifiers
copilot-vendor, copilot, claude, codex, gemini, pi, pi-base, and threat-detection. The agent has only a generic network-allowlist bullet and no ecosystem mapping or reference link.
- Suggested fix: Add a short routing note distinguishing automatically applied engine transport sets and compatibility aliases from user-selected package ecosystems; link the agent to the network table. Do not add every transport identifier to generated allowlists.
4. Tool Mode Coverage
- Source:
.github/aw/syntax.md → .github/aw/syntax-tools-imports.md; .github/aw/token-optimization.md
- Missing from: agent file
- Details: The skill's table covers
tools.github.mode: gh-proxy, mode: local, and tools.cli-proxy: true. The agent file lists tool names but none of these modes, their selection criteria, or a link to the table.
- Suggested fix: Route tool selection through the shared mapping and document the
gh-proxy default, local MCP use case, and CLI proxy option. Do not recommend the explicitly unsupported GitHub remote mode or removed Playwright mode: mcp.
5. Frontmatter Generation Coverage
- Source:
.github/aw/syntax.md → .github/aw/syntax-agentic.md / .github/aw/syntax-core.md
- Missing from: both
- Details: The skill's generation template and interview do not surface current controls including top-level
model, max-turns, max-ai-credits, max-daily-ai-credits, max-turn-cache-misses, models, and user-rate-limit, or trigger options on.cooldown and on.skip-author-associations. The agent's frontmatter checklist also omits these. The supplied history does not establish when these fields were introduced; these are current coverage gaps, not claims that all fields were added this week.
- Suggested fix: Add conditional generation guidance and reference links for model policy, cost limits, rate limits, and activation filters. Preserve the recommendation to omit unnecessary defaults rather than expanding every generated workflow with every optional field.
6. Pattern Routing Coverage
- Source:
.github/aw/patterns.md
- Missing from: agent file
- Details: All 20 named patterns are covered by the skill's shared Pattern Heuristics table. The agent has neither those mappings nor a link to the pattern router, leaving no explicit path to recommend patterns such as BatchOps, CorrectionOps, CentralRepoOps, or WorkQueueOps.
- Suggested fix: Link workflow architecture selection in the agent to
.github/aw/designer-mappings.md and .github/aw/patterns.md.
7. Token Optimization and Sub-Agent Guidance
- Source:
.github/aw/token-optimization.md; .github/aw/subagents.md; .github/aw/create-agentic-workflow.md
- Missing from: agent file
- Details: Its optimization section focuses on concise wording and cache memory, without DataOps prefetch, smaller-model inline sub-agents, or progressive loading of skills. It does not link to the relevant guides. The designer skill already covers DataOps and
model: small sub-agent processing and links to the detailed references.
- Suggested fix: Reuse the skill's optimization defaults and route batch/delegation requests to the sub-agent guide, including its bounded-delegation rules; link optional inline skills to the token guide.
No Drift
- ✅ Skill pattern coverage: all 20 named reference patterns have shared heuristic entries.
- ✅ Skill tool modes:
gh-proxy, local, and CLI proxy are represented.
- ✅ Skill coverage of ordinary network ecosystems: common mappings plus explicit routing for less common identifiers.
- ✅ No confirmed removed documentation path, field, or option was found in the inspected designer guidance. This is not an exhaustive compiler validation.
- ✅ No unmatched recent reference commit in the supplied history: both files list the same commit,
604e7e5. Matching commit IDs alone do not prove semantic synchronization.
Methodology
Compared outlines of 8 reference docs against both designer files.
Reference doc commits (last 7 days): 1
Designer file commits (last 7 days): 1
The supplied SKILL.md outline corresponds to .github/aw/designer.md, as confirmed by the audit workflow's extraction step. Followed its explicit delegation to .github/aw/designer-mappings.md and inspected the actual agent file and relevant split reference sections to avoid treating outline omissions as missing content. Counted explicit reference routing as coverage. The registered-output input includes nested schema fields and duplicates; filtered these using the local validation/tool definitions and distinguished internal handlers from configurable outputs. History counts describe only the supplied snapshots, whose reference path filter excludes split reference documents and whose designer filter excludes the shared mappings file.
Next Actions
Update the shared mappings for confirmed gaps, connect the interactive agent to the current designer references, and add optional generation guidance for current frontmatter controls. Improve future audit inputs to include delegated mappings and split reference history, and extract only top-level registered output names.
Generated by 🔍 Designer Drift Audit · codex · gpt60 · 80.9 AIC · ⌖ 28.3 AIC · ⊞ 15.7K · ◷
Designer Drift Report — 2026-10-06
Summary
Seven drift items were found across six categories. The designer skill's shared mappings provide substantial coverage, but several operations and generation options are missing; the interactive agent also lacks a route to the current reference guidance.
Drift Items
View Drift Items by Category
1. Missing Trigger Coverage
.github/aw/triggers.md(Standard GitHub Events and command/incident sections)pushappears in the reference but has no entry in the skill's delegated.github/aw/designer-mappings.mdtrigger table. The agent file lists onlyissues,pull_request,schedule, andworkflow_dispatch; it omitspush,workflow_run,deployment_status,slash_command, andlabel_command, and does not link to the shared mappings.2. Missing Safe Output Types
.github/aw/safe-outputs.md→safe-outputs-content.md/safe-outputs-automation.md;/tmp/gh-aw/data/all-safe-output-types.txt;.github/aw/test-coverage.md;.github/aw/memory.mdado-upload-workitem-attachment,approve-workflow-run,call-workflow, andupload-code-coverage. It also lacks guidance for the registeredledger_appendandledger_request_compactiontools. The agent supplies only three example output types and no reference to the complete mappings.ledger_mutationis a trusted audit handler, not a user-selectable output;push_repo_memoryis already represented throughrepo-memoryand is not counted as missing.tools.ledgerand its append/compaction documentation rather than inventing corresponding safe-output frontmatter keys. Link the agent to this table.3. Network Identifier Coverage
.github/aw/network.md(Ecosystem Identifiers and Engine Domain Sets)copilot-vendor,copilot,claude,codex,gemini,pi,pi-base, andthreat-detection. The agent has only a generic network-allowlist bullet and no ecosystem mapping or reference link.4. Tool Mode Coverage
.github/aw/syntax.md→.github/aw/syntax-tools-imports.md;.github/aw/token-optimization.mdtools.github.mode: gh-proxy,mode: local, andtools.cli-proxy: true. The agent file lists tool names but none of these modes, their selection criteria, or a link to the table.gh-proxydefault, local MCP use case, and CLI proxy option. Do not recommend the explicitly unsupported GitHubremotemode or removed Playwrightmode: mcp.5. Frontmatter Generation Coverage
.github/aw/syntax.md→.github/aw/syntax-agentic.md/.github/aw/syntax-core.mdmodel,max-turns,max-ai-credits,max-daily-ai-credits,max-turn-cache-misses,models, anduser-rate-limit, or trigger optionson.cooldownandon.skip-author-associations. The agent's frontmatter checklist also omits these. The supplied history does not establish when these fields were introduced; these are current coverage gaps, not claims that all fields were added this week.6. Pattern Routing Coverage
.github/aw/patterns.md.github/aw/designer-mappings.mdand.github/aw/patterns.md.7. Token Optimization and Sub-Agent Guidance
.github/aw/token-optimization.md;.github/aw/subagents.md;.github/aw/create-agentic-workflow.mdmodel: smallsub-agent processing and links to the detailed references.No Drift
gh-proxy,local, and CLI proxy are represented.604e7e5. Matching commit IDs alone do not prove semantic synchronization.Methodology
Compared outlines of 8 reference docs against both designer files.
Reference doc commits (last 7 days): 1
Designer file commits (last 7 days): 1
The supplied
SKILL.mdoutline corresponds to.github/aw/designer.md, as confirmed by the audit workflow's extraction step. Followed its explicit delegation to.github/aw/designer-mappings.mdand inspected the actual agent file and relevant split reference sections to avoid treating outline omissions as missing content. Counted explicit reference routing as coverage. The registered-output input includes nested schema fields and duplicates; filtered these using the local validation/tool definitions and distinguished internal handlers from configurable outputs. History counts describe only the supplied snapshots, whose reference path filter excludes split reference documents and whose designer filter excludes the shared mappings file.Next Actions
Update the shared mappings for confirmed gaps, connect the interactive agent to the current designer references, and add optional generation guidance for current frontmatter controls. Improve future audit inputs to include delegated mappings and split reference history, and extract only top-level registered output names.