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

[github-actions[bot]]

Summary

• Inconsistencies found: 4
• Areas reviewed: schema, parser/compiler, documentation, and repository workflows
• Strategy: generated-example and boundary behavior comparison; new strategy
• Highest priority: the daily credit default is described incorrectly, and the schema accepts a denial threshold that the compiler discards.

Key findings

1. Daily AI-credit default is documented as disabled, but the compiler supplies 5,000. The schema description (main_workflow_schema.json:5028) and frontmatter reference:578 say omission disables the guardrail. Instead, daily_aic_workflow.go:208 falls back to an Actions variable and the 5,000-credit constant, matching the enterprise controls reference. Workflows omitting the field can therefore experience unexpected admission checks or skips. Update the schema and frontmatter reference to describe precedence and explicit -1 disabling, and test that the documented default matches compilation.

2. The schema accepts max-tool-denials: 0, but the compiler drops it. The field references the non-negative templatable integer. The parser requires a minimum of 1 and returns an empty value for zero; support validation then treats it as unset. An author can pass schema validation while the requested threshold is ignored. Use the positive-integer schema and reject zero explicitly, with a schema-to-compiler regression test.

3. Generated frontmatter examples violate their own schema. The generated reference shows empty connectors: {}, despite the minimum of one property; it also shows an invalid source SHA and invalid expression placeholders. The generator falls back to example-value without respecting patterns. Generate valid representative values and validate individual alternatives against their schema in generator tests.

4. Glossary excludes supported Pi tool limits. The denial entry says Copilot SDK only, and the calls entry excludes other engines. Compiler validation and the Pi reference support both limits for built-in Pi CLI, SDK and RPC drivers. The unsupported-engine error also incorrectly says denials are Copilot-only. Align the glossary and error message with supported Pi drivers.

Scope, workflow usage, and limitations

• The precomputed inventory reports no top-level keys used in repository workflows that are missing from the schema. Sampled workflows use skip-if-decision and explicit daily credit limits; this was a targeted review, not a full workflow validation.
• The four top-level schema fields absent from FrontmatterConfig are not automatically defects: targeted code inspection found raw-frontmatter handling for connectors, Docker pull policy, skip decisions, and the deprecated work-queue policy.
• Canonical AWF config sources were unavailable in the supplied drift data. No authoritative AWF config-source drift conclusion can be drawn from that degraded comparison.
• Findings are based on static cross-checks and existing compiler fixtures; no workflow was executed.

Next actions

• Correct daily-credit default descriptions and add a default consistency check.
• Align the denial threshold schema and compiler rejection, including zero coverage.
• Generate and schema-validate valid examples.
• Update Pi tool-limit documentation and unsupported-engine diagnostics.

Strategy performance: 4 actionable findings; high effectiveness; reuse for constrained-value and generated-example checks.

References: §43371724452

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

• expires on Nov 13, 2026, 9:29 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 #77667.