[Schema Consistency] 🔍 Schema Consistency Check — 2026-10-26

[github-actions[bot]]

Three confirmed inconsistencies affect documented configuration. No critical runtime bug was established. Repository source files were unchanged.

Summary

• Inconsistencies found: 3 new findings, excluding cached findings.
• Categories analyzed: schema, parser/compiler, reference documentation, and workflow/shared usage.
• Strategy: Minimal counterexample validation of documentation contracts.
• New strategy: Yes; day 299 modulo 10 = 9 selected exploration.
• Revision: 9a57ef760fda8457186126cf0f098ff595a3b5f7.

Key Issues

1. Schema improvement needed: add-comment.allows-comment-ids rejects documented expression syntax. The example at docs/src/content/docs/reference/safe-outputs.md:438 uses ${{ needs.prepare.outputs.comment_ids }}. The schema at pkg/parser/schemas/main_workflow_schema.json:8645 permits only an array of strings. The parser explicitly preprocesses this field as a templatable string array at pkg/workflow/add_comment.go:75. A minimal object containing the expression fails schema validation; replacing it with ["123"] passes. Impact: schema validation blocks the documented expression form before parser support can apply. Fix: align the schema with the existing templatable-list contract and add a regression case for the documented expression.

2. Documentation gap / parser feature decision: MCP script input enum is unsupported. docs/src/content/docs/reference/mcp-scripts.md:189 advertises enum: ["option1", "option2", "option3"] as limiting choices. Input properties under mcp-scripts in the schema (pkg/parser/schemas/main_workflow_schema.json:14069) exclude enum and forbid additional properties. parseMCPScriptInputs at pkg/workflow/mcp_scripts_parser.go:158 does not extract an enum; generateMCPScriptInputSchema at pkg/workflow/mcp_scripts_generator.go:91 does not emit one. A complete inert tool definition with description and script fails solely on the added enum and passes when enum is removed. Impact: the advertised choice restriction cannot be configured or enforced through this contract. Fix: remove the unsupported claim/example, or implement schema acceptance, parsing, generated enum constraints, and validation together. The documentation fragment also omits an implementation body; that incompleteness was excluded from this finding.

3. Documentation gap: expires does not accept runtime Actions expressions as advertised. The Templatable Fields section at docs/src/content/docs/reference/safe-outputs.md:2127 claims runtime expression support and shows expires: ${{ inputs.expires-days }}. The create-issue schema at pkg/parser/schemas/main_workflow_schema.json:6838 accepts positive integer days, duration strings, or false; an expression matches none. parseExpiresFromConfig at pkg/workflow/time_delta.go:382 sends strings to static relative-time parsing. preprocessExpiresField at pkg/workflow/config_preprocessing.go:175 converts unrecognized values to zero rather than retaining an expression. A minimal create-issue expression fails schema validation; expires: 7d passes. Impact: copying the runtime-input example fails validation; widening schema acceptance alone would not implement the advertised behavior. Fix: document static expiry values now, or implement runtime resolution consistently with maintenance scheduling before advertising it.

Analysis evidence, workflow scope, and limitations

• Started from the supplied precomputed diff and strategy database. The apparent missing top-level fields are false positives: docker-image-pull-policy is consumed through RawFrontmatter in pkg/workflow/docker.go:294; work-queue-policy is consumed through RawFrontmatter in pkg/workflow/work_queue_policy.go:184.
• Validated reference YAML snippets with a local Draft7 validator while preserving YAML on keys. Reduced the three findings to inert JSON objects and checked corrected controls. No workflow code was executed and no live dispatch was attempted.
• The supplied diff reports no top-level workflow keys outside the schema. Targeted scans included .github/workflows/shared/. Expiry expressions in five shared components use github.aw.import-inputs, for example shared/daily-issue-base.md:39; these are import-time substitutions and are not classified as violations of the runtime-expression finding.
• No workflow violation was confirmed for these findings. This is a focused static analysis, not a claim that every nested field in every workflow validates.
• Non-authoritative AWF warning: /tmp/gh-aw/agent/awf-config-drift.json has degraded: true because canonical config sources could not be retrieved. No AWF drift conclusion is drawn from that incomplete comparison; no corrective PR, drift issue, or failed required check is proposed.
• Source references are local paths at the revision above. Existing cached findings were excluded.

Recommendations and Next Steps

• Extend the comment-ID allowlist schema to match existing parser expression support.
• Correct the MCP input enum documentation, or implement the feature across schema, parser, and generated input validation.
• Correct the expiry templating claim; any future runtime support must account for maintenance scheduling.
• Add focused regression coverage for these three contracts. No workflow file correction is currently established.

Strategy Performance

• Findings: 3.
• Effectiveness: High for targeted contract mismatches.
• Should reuse: Yes.
• Saved strategy-9 and its findings in the strategy database.

References: §40274984977

Generated by ✅ Schema Consistency Checker · codex · gpt61 · ~18 AIC · ⌖ ~7 AIC · ⊞ 19.6K · ◷

• expires on Oct 26, 2026, 9:40 PM UTC-08:00

[github-actions[bot]]

This discussion has been marked as outdated by Schema Consistency Checker.

A newer discussion is available at Discussion #72328.