[Schema Consistency] Schema Consistency Check - 2026-09-29

[github-actions[bot]]

🔍 Schema Consistency Check - 2026-09-29

Summary

• Inconsistencies Found: 3
• Categories Analyzed: Schema, Parser, Documentation, Workflows
• Strategy Used: Schema-def spot checks + targeted parser/doc/workflow verification
• New Strategy: NO

Critical Issues

1. max-turn-cache-misses default mismatch (Schema ↔ Documentation)

   • Schema declares default 5 and explicitly states built-in default 5 in description (pkg/parser/schemas/main_workflow_schema.json:4374).
   • Reference docs contain stale/default guidance indicating 10 for related max-style safe-output limits and examples around this section, but do not reflect the schema’s 5 for max-turn-cache-misses (docs/src/content/docs/reference/frontmatter-full.md:3393).
   • Impact: Operators can tune based on incorrect expected fallback values, affecting cache-miss block behavior.

2. runs-on-slim default ambiguity in docs vs implementation (Schema/Parser ↔ Documentation)

   • Schema and code paths align on ubuntu-slim default for framework/generated jobs (pkg/parser/schemas/main_workflow_schema.json:2912, pkg/workflow/safe_outputs_runtime.go:22).
   • Reference docs contain broad default runner language (ubuntu-latest) in surrounding runner docs and do not clearly segregate runs-on vs runs-on-slim default semantics in a way that prevents confusion (docs/src/content/docs/reference/frontmatter.md:144).
   • Impact: Users may assume generated jobs run on ubuntu-latest and miss infra compatibility issues on environments lacking ubuntu-slim labels.

Documentation Gaps

1. Safe-outputs requirement signaling is under-enforced in examples
   • Schema marks safe-outputs as required when write-side tools are used (schema comment under safe-outputs property).
   • Multiple workflows in-repo contain write-like tool usage patterns without a visible top-level safe-outputs block (sample set includes .github/workflows/code-simplifier.md, .github/workflows/dead-code-remover.md, .github/workflows/lockfile-stats.md).
   • Impact: The practical contract (required for writes) appears inconsistently represented across examples/workflows, making author intent and migration expectations unclear.

Schema Improvements Needed

• Add explicit machine-readable cross-field constraint (if supported) linking write-capable tools to required safe-outputs presence, beyond prose-only schema comments.
• Add a dedicated default metadata field for runs-on-slim/generated-job runner fallback to reduce reliance on description text for critical default behavior.

Parser Updates Required

• No hard parser/schema type mismatch was confirmed in this run for sampled fields (max-turn-cache-misses, runs-on-slim, permissions, safe-outputs).
• Optional: add a compiler warning when write-capable tools are configured and safe-outputs is absent, to align runtime behavior with schema intent.

Workflow Violations

Potential (needs compiler-level confirmation):

• Workflows with write-like tools but no explicit safe-outputs section, e.g.:
  • .github/workflows/code-simplifier.md
  • .github/workflows/copilot-agent-analysis.md
  • .github/workflows/dead-code-remover.md
  • .github/workflows/lockfile-stats.md

AWF Config-Source Drift Signal

• /tmp/gh-aw/agent/awf-config-drift.json reports degraded: true with canonical source retrieval failure.
• Per policy, this run treats AWF drift as non-authoritative warning only and does not propose corrective PR/issue actions from that incomplete comparison.

Recommendations

1. Align frontmatter-full.md defaults for max-turn-cache-misses with schema default 5.
2. Add a dedicated docs callout separating runs-on default behavior from runs-on-slim (ubuntu-slim) generated-job behavior.
3. Add compile-time warning/error docs + examples for write-tool usage without safe-outputs to eliminate ambiguity.

Strategy Performance

• Strategy Used: Schema-def spot checks + targeted parser/doc/workflow verification
• Findings: 3
• Effectiveness: HIGH
• Should Reuse: YES

Next Steps

• Fix documentation defaults and runner-default wording
• Evaluate adding schema/compiler-enforced safe-outputs cross-field validation
• Audit workflows for explicit safe-outputs declarations where write tools are present

Generated by ✅ Schema Consistency Checker · codex · gpt53codex · 12.4 AIC · ⌖ 3.52 AIC · ⊞ 21K · ◷

• expires on Sep 29, 2026, 9:37 PM UTC-08:00

[github-actions[bot]]

This discussion was automatically closed because it expired on 2026-09-30T05:37:35.972Z.

Closed by Workflow