[Schema Consistency] 🔍 Schema Consistency Check - 2026-11-12

[github-actions[bot]]

Summary

• Inconsistencies found: 3
• Areas reviewed: schema, parser/compiler, documentation, and selected project workflows
• Strategy: precomputed field-gap triage with targeted constraint and example comparisons; reused cached strategy (day-of-year modulo 10 = 6).
• Scope: targeted static review, not exhaustive validation of every example or workflow. The precomputed inventory reports no top-level workflow keys missing from the schema. The four schema fields absent from the typed frontmatter structure have raw-frontmatter handling, so that difference alone is not a defect.

Key findings

1. High — Daily credit guardrail default is described incorrectly. pkg/parser/schemas/main_workflow_schema.json:5027 and docs/src/content/docs/reference/frontmatter.md:578 say omission disables max-daily-ai-credits; the generated reference repeats this at docs/src/content/docs/reference/frontmatter-full.md:4424. In contrast, pkg/workflow/daily_aic_workflow.go:208 resolves an omitted value to the repository variable or built-in default, and pkg/workflow/daily_aic_workflow.go:234 enables the guardrail unless explicitly disabled or in dry-run. pkg/constants/constants.go:444 sets the fallback to 5000; docs/src/content/docs/reference/cost-management.md:214 agrees. Authors relying on the incorrect text may encounter unexpected activation blocking. Update the schema description and friendly reference to explain the 5000 default, variable override, imports, and explicit -1 opt-out; regenerate the full reference.

2. Medium — Skip questions pass schema validation but fail compiler validation. pkg/parser/schemas/main_workflow_schema.json:39 accepts any nonblank string, including a question containing ${{ inputs.reason }}. pkg/workflow/skip_if_decision.go:25 explicitly rejects ${{, and docs/src/content/docs/reference/frontmatter.md:91 says Actions expressions are unsupported. Editors and schema-only validators can therefore accept configuration that compilation rejects. Add a schema prohibition for that literal sequence, with a regression case for both valid questions and expressions, while retaining the compiler check. Existing examples such as .github/workflows/daily-file-diet.md:33 use runtime file references.

3. Medium — Generated frontmatter reference contains schema-invalid example values. docs/src/content/docs/reference/frontmatter-full.md:25 emits connectors: {}, but the schema requires at least one connector (main_workflow_schema.json:27). The reference emits max-turns: "example-value" at line 4375, although its string alternative requires an Actions expression (main_workflow_schema.json:15289), and user-rate-limit.events: [] at line 25034 despite minItems: 1 (main_workflow_schema.json:13987). Copying these illustrative alternatives produces validation errors. Teach the reference generator to respect property counts, array minimums, and string patterns or select schema-provided examples; validate generated alternatives against the corresponding schema fragments.

Review notes and limitations

• Workflow usage: the precomputed top-level inventory found no unknown keys; selected skip-if-decision usage and the explicit max-daily-ai-credits: -1 in .github/workflows/pr-sous-chef.md:6 were checked. This does not establish that all nested fields or workflow values validate.
• Parser changes: no parser change is recommended for the three findings; align the schema with existing rejection and correct the documentation/generator.
• AWF source availability: the precomputed AWF comparison is degraded because canonical sources could not be retrieved. This is a non-authoritative availability warning, not a drift finding.
• Strategy performance: 3 findings; effectiveness high for this focused review; reuse with independent verification of raw-frontmatter paths.

Next actions

• Correct daily guardrail default descriptions and regenerate the reference.
• Align the skip-question schema with compiler validation and add coverage.
• Make generated alternatives schema-valid and add fragment validation.

References: §43161108939

Generated by ✅ Schema Consistency Checker · codex · routed: gpt61 medium · ~10 AIC · ⌖ ~2 AIC · ⊞ 470 · ◷

• expires on Nov 12, 2026, 9:30 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 #77360.