[Schema Consistency] Schema consistency check — 2026-11-09

[github-actions[bot]]

🔍 Schema consistency check — 2026-11-09

Four actionable inconsistencies were found in a targeted comparison of the schema, compiler, documentation, and repository workflows. Strategy: precomputed field-gap triage with targeted validation and documentation checks (reused). No critical implementation defect was established.

AWF comparison limitation: Canonical AWF configuration sources were unavailable, so the precomputed AWF comparison is degraded. This is a non-authoritative warning; no AWF drift finding is asserted.

Findings and evidence

1. Schema accepts skip questions that the compiler rejects. pkg/parser/schemas/main_workflow_schema.json:10 permits any nonblank string, including a question containing the literal ${{ marker. pkg/workflow/skip_if_decision.go:25 rejects that marker, and docs/src/content/docs/reference/frontmatter.md:89 documents the restriction. Schema-based editors can therefore accept input that fails compilation. Add a schema constraint excluding the marker and a regression case matching the compiler rule.

2. Sandbox guide misstates the timeout scope. docs/src/content/docs/reference/sandbox.md:359 and :363 describe top-level timeout-minutes as the entire agent job timeout with a 20-minute default. docs/src/content/docs/reference/frontmatter.md:485 and docs/src/content/docs/reference/steps-jobs.md:257 distinguish the agentic execution step, normally 20 minutes, from the agent job, normally 60 minutes. Correct the guide and explain jobs.agent.timeout-minutes for setup and post-processing, including the documented adjustment for longer literal step budgets.

3. Reusable timeout example splits its frontmatter. The example at docs/src/content/docs/reference/sandbox.md:386 places --- between on.workflow_call and timeout-minutes, rather than surrounding both fields with opening and closing frontmatter delimiters. A reader copying it as a workflow will not get the intended combined frontmatter. Move the delimiter to the beginning and add a closing delimiter after the timeout, with a workflow body if presenting a complete file.

4. MCP scripts schema description omits Go. pkg/parser/schemas/main_workflow_schema.json:14319 lists only JavaScript, shell, and Python and says one of those three is required, while the same schema defines go at :14390 and the reference at docs/src/content/docs/reference/mcp-scripts.md:65 correctly includes it. Add Go to the parent description and its exactly-one list so schema-generated guidance matches the accepted options.

Workflow review: The precomputed usage diff reports no used top-level keys missing from the schema. Sampled skip-if-decision workflows, including .github/workflows/daily-graft-intelligence.md:18, use the documented list form. The three top-level fields absent from the typed frontmatter structure are handled through raw frontmatter; their absence from that struct alone is not a defect. This targeted review did not validate every workflow or execute workflows.

Strategy performance: High for separating false-positive field gaps from actionable cross-layer mismatches; reuse with focused source checks.

Next actions

• Align the skip-question schema with compiler validation and add a regression case.
• Correct the timeout scope and reusable-workflow example in the sandbox guide.
• Update the MCP scripts schema description to include Go.
• Re-run the AWF comparison when its canonical sources are available.

References: §42567100532

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

• expires on Nov 9, 2026, 9:33 PM UTC-08:00