[Schema Consistency] Schema Consistency Check — 2026-10-14

[github-actions[bot]]

🔍 Schema Consistency Check — 2026-10-14

Summary

• Confirmed inconsistencies: 3; no critical runtime bug demonstrated.
• Areas analyzed: schema, parser/compiler, documentation, project workflows.
• Strategy: new bulk documentation snippet validation with compiler evidence (day-of-year modulo 10 = 7).
• Coverage: 475 frontmatter documents including shared components; 344 top-level workflow documents; 484 reference YAML mapping snippets.

Key Issues

1. Schema rejects implemented on.slash_command.placeholder (medium). The documented example at docs/src/content/docs/reference/command-triggers.md:204 sets placeholder: to review this PR. The slash-command object at pkg/parser/schemas/main_workflow_schema.json:765 permits only name, events, and strategy, with additionalProperties: false at line 820. Yet pkg/workflow/frontmatter_extraction_yaml.go:270 extracts the field and pkg/workflow/compiler_safe_outputs_envvars.go:112 emits it for footer hints. Fix: add a string placeholder property to the slash-command schema and verify that the documented example passes validation and reaches generated footer configuration.

2. MCP script docs promise unsupported enum validation (medium). docs/src/content/docs/reference/mcp-scripts.md:187 shows choice-param.enum and says values are limited to three options. The input parameter schema at pkg/parser/schemas/main_workflow_schema.json:13829 allows type, items, description, required, and default, and rejects additional properties. MCPScriptParam at pkg/workflow/mcp_scripts_parser.go:66 has no enum field; extraction at line 158 and generated input schemas at pkg/workflow/mcp_scripts_generator.go:98 do not propagate enum constraints. Fix: remove the unsupported example and validation claim, or implement enum support in schema, parser, and generated MCP input schemas together. The example also omits a script implementation, so correcting enum alone does not make it a complete tool definition.

3. QMD documentation advertises schema-invalid configuration (medium). docs/src/content/docs/reference/tools.md:182 shows tools.qmd.checkouts, and docs/src/content/docs/experimental/qmd.md:21 repeats QMD setup. Validating the documented root tools object yields Additional properties are not allowed ('qmd' was unexpected). The compiler retains a QMD mention in CLI mounting (pkg/workflow/mcp_cli_mount.go:100), but that does not establish end-to-end support. Fix: clarify whether QMD is still supported; remove or clearly mark unavailable configuration if retired, or restore complete schema/compiler support before recommending it.

Validation details and limits

Method

Used the supplied schema diff rather than rebuilding field enumeration. Both apparent schema-only fields, docker-image-pull-policy and work-queue-policy, have RawFrontmatter consumers (pkg/workflow/docker.go:294, pkg/workflow/work_queue_policy.go:184), so neither was reported as missing implementation.

Used local Python YAML and JSON Schema validation with local schema references. Boolean resolution preserved the YAML on key. Documentation snippets were checked per known root field so omitted unrelated required fields would not create findings. Other rejected snippets remain untriaged and are not included in the confirmed count.

Workflow Violations

No additional schema errors appeared in the 344 top-level workflow documents after excluding missing-trigger errors for fragments/redirects. Shared components were also inspected, but their missing on fields and unresolved import-input expressions were not counted as violations. This is static source validation, not compilation after import resolution, and does not establish full workflow correctness. No workflow was executed.

AWF Canonical Source Warning — Non-Authoritative

The supplied awf-config-drift.json has degraded: true: canonical source retrieval failed. No authoritative AWF drift conclusion is possible from this run. This warning is excluded from the inconsistency count; no required-check failure, corrective PR, or drift issue is proposed from that comparison.

Strategy Performance

• New strategy: yes.
• Findings: 3.
• Effectiveness: high for finding actionable invalid documentation and schema omissions.
• Reuse: yes, with compiler corroboration and fragment/template exclusions.
• Strategy metrics saved to the strategy cache; repository source files were not changed.

Recommendations and Next Steps

• Add schema support for the implemented slash-command placeholder.
• Align MCP script enum documentation with actual validation support.
• Resolve QMD support status and align schema/compiler/documentation.
• Add focused validation of complete documentation examples, distinguishing fragments from standalone workflows.

References: §38517037831

Generated by ✅ Schema Consistency Checker · codex · gpt61 · 18.5 AIC · ⌖ 6.77 AIC · ⊞ 19.1K · ◷

• expires on Oct 14, 2026, 9:36 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 #68969.