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

[github-actions[bot]]

🔍 Schema Consistency Check - 2026-09-25

Summary

• Inconsistencies Found: 4
• Categories Analyzed: Schema, Parser, Documentation, Workflows
• Strategy Used: Doc-claim contradiction audit
• New Strategy: YES

Critical Issues

1. runs-on-slim default appears inconsistent between schema and docs

   • Docs state default is ubuntu-slim in docs/src/content/docs/reference/frontmatter.md:411.
   • The schema-diff extraction reports unresolved type/default metadata for runs-on-slim (field_types shows blank type), suggesting schema constraints/default visibility may be incomplete or encoded in a way not surfaced by existing analysis.
   • Impact: consumers relying on schema tooling may not infer the documented default.

2. max-turn-cache-misses has mixed default examples in docs

   • Short reference example shows max-turn-cache-misses: 5 in docs/src/content/docs/reference/frontmatter.md:470.
   • Full reference contains an example with max-turn-cache-misses: 1 at docs/src/content/docs/reference/frontmatter-full.md:3387.
   • Impact: ambiguity on recommended/default operational threshold.

Documentation Gaps

1. Doc discoverability gap for schema-level typing on several top-level keys
   • Precomputed field_types from /tmp/gh-aw/agent/schema-diff.json reports complex/blank type extraction for multiple fields (e.g., engine, max-runs, runs-on, timeout-minutes).
   • Docs are rich, but this mismatch indicates either schema composition ($ref/oneOf) or doc wording makes machine-audited type extraction brittle.
   • Impact: drift detectors and external validators may report false negatives/positives.

Schema Improvements Needed

1. Strengthen explicit top-level type/default projection for composed fields

   • Candidate keys: engine, runs-on, runs-on-slim, max-runs, timeout-minutes.
   • Prefer exposing stable top-level type/default hints even when fields are $ref-backed.

2. Normalize canonical default examples for cache-miss limits

   • Align examples in frontmatter.md and frontmatter-full.md to avoid dual implied defaults.

Parser Updates Required

1. No direct parser missing-field gap found at top level
   • in_schema_not_frontmatter and in_frontmatter_not_schema are empty in /tmp/gh-aw/agent/schema-diff.json, indicating top-level parity.
   • Recommended parser action is therefore documentation/schema clarity, not new parser field wiring.

Workflow Violations

1. No top-level unknown-key violations detected in checked workflows
   • in_used_not_schema is empty in /tmp/gh-aw/agent/schema-diff.json.
   • Workflows widely use advanced keys such as strict, imports, safe-outputs, tracker-id, user-rate-limit, and those are represented in schema/frontmatter.

AWF Config-Source Drift Note (Non-Authoritative)

• /tmp/gh-aw/agent/awf-config-drift.json reports degraded: true and failed canonical-source retrieval.
• Per policy, this is a warning only and not used to trigger corrective or failing actions.

Recommendations

1. Add a schema-lint check that verifies every top-level property resolves to an explicit effective type/default in generated analysis output.
2. Reconcile max-turn-cache-misses examples between frontmatter.md and frontmatter-full.md (or annotate one as non-default scenario).
3. Add a docs consistency test that flags conflicting “default” claims across reference pages.

Strategy Performance

• Strategy Used: Doc-claim contradiction audit
• Findings: 4
• Effectiveness: MEDIUM
• Should Reuse: YES

Next Steps

• Clarify schema projection for composed fields
• Align reference examples for cache-miss defaults
• Add docs default-consistency CI checks
• Re-run consistency checker after docs/schema updates

Generated by ✅ Schema Consistency Checker · codex · gpt53codex · 11 AIC · ⌖ 4 AIC · ⊞ 21K · ◷

• expires on Sep 25, 2026, 9:34 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 #63568.