[Schema Consistency] 🔍 Schema Consistency Check — 2026-10-15

[github-actions[bot]]

Overview

Found 4 confirmed inconsistencies across schema examples, compiler behavior, and documentation. Reviewed all four areas using the precomputed field/workflow diff and targeted source checks. No repository source files were changed.

• Strategy: Schema metadata self-validation and rejected-feature triangulation.
• New strategy: Yes — day-of-year 288 modulo 10 = 8.
• Validation: Local Draft 7 JSON Schema validation rejected all three feature reproductions and all four project-operation examples described below. Compiler evidence was inspected; workflows were not executed.
• Critical issues: None established. The findings affect authoring reliability and documented configuration.

Actionable Findings

1. Schema rejects implemented and documented on.slash_command.placeholder (medium).

The documented example in command-triggers.md:204 sets placeholder: to review this PR. The slash-command object in main_workflow_schema.json:770 only permits name, events, and strategy, with additionalProperties: false. Yet frontmatter_extraction_yaml.go:270 extracts this string, and compiler_safe_outputs_envvars.go:112 propagates it. Fix: Add a string placeholder property to the slash-command schema and cover validation through the public compilation path.

2. QMD documentation advertises a rejected tool configuration (medium).

tools.md:182 shows tools.qmd.checkouts and promises a dedicated indexing job. Validating this exact configuration reports: Additional properties are not allowed (qmd was unexpected). Targeted searches of workflow Go sources found no dedicated QMD configuration/indexing implementation, only incidental references; the custom-tool fallback alone does not establish this feature. Fix: Determine whether QMD was retired or moved, then remove or migrate the reference and linked experimental guide. If intended to remain supported, restore schema and compiler support together before advertising it.

3. Reusable-workflow example uses unsupported choice inputs (medium).

safe-outputs.md:1496 declares on.workflow_call.inputs.environment.type: choice plus options, and explicitly lists choice as supported. main_workflow_schema.json:2049 permits only string, number, and boolean for workflow-call inputs and rejects options. The compiler helper test safe_outputs_call_workflow_test.go:201 nevertheless constructs choice inputs directly and expects an enum, bypassing frontmatter validation. Fix: Change the worker example to a string input with explicit value validation, and align helper tests with valid reusable-workflow inputs. Do not broaden the schema without also establishing valid generated GitHub Actions behavior.

4. Four embedded schema examples omit required project (low; one grouped finding).

safe-outputs.update-project requires project at main_workflow_schema.json:6906, but both examples at line 7054 omit it. Likewise, create-project-status-update requires project at line 7210, but both examples at line 7264 omit it. All four examples also fail when embedded in a complete minimal frontmatter object. Fix: Add valid project targets to the examples and add a schema-example consistency check.

Scope, false positives, and limitations

The precomputed diff reports no workflow top-level fields absent from the schema. This is a top-level consistency result, not proof that every workflow or imported component compiles. No workflow violations are asserted from this limited scan.

The two apparent schema/frontmatter gaps are false positives: docker-image-pull-policy is consumed through RawFrontmatter in pkg/workflow/docker.go:294, and work-queue-policy is consumed in pkg/workflow/work_queue_policy.go:184. Missing struct tags alone are not missing implementation.

Reference YAML snippets were screened in bulk while preserving the YAML on key. Partial snippets, non-workflow contexts, and security-related configurations were excluded from confirmed findings unless separately corroborated. No runtime or security-boundary testing was performed.

Non-authoritative AWF warning: The supplied AWF drift artifact has degraded: true because canonical-source retrieval failed. No AWF config-source drift conclusion is made. This warning must not fail a required check or justify a corrective PR or drift issue.

Recommendations and Next Steps

• Add the implemented slash-command placeholder to the schema.
• Resolve QMD feature status and update its documentation accordingly.
• Correct workflow-call input documentation and helper-test assumptions.
• Repair the four project-operation examples and validate embedded examples automatically.

Strategy Performance

Findings: 4 grouped issues. Effectiveness: High. Should reuse: Yes. The new strategy detects contradictions inside schema metadata and confirms documented-feature failures against the public schema before assigning compiler changes. Strategy metrics were saved to the requested strategy database.

References: §38687198709

Generated by ✅ Schema Consistency Checker · codex · gpt61 · 18 AIC · ⌖ 6.86 AIC · ⊞ 19.1K · ◷

• expires on Oct 15, 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 #69267.