[Schema Consistency] Schema Consistency Check — 2026-10-13: four confirmed inconsistencies

[github-actions[bot]]

🔍 Schema Consistency Check — 2026-10-13

Summary

• Confirmed inconsistencies: 4; no critical security issue established.
• Areas analyzed: schema, parser/compiler, documentation, and repository workflows.
• Strategy: cached schema spot checks with targeted parser/doc/workflow verification (day 286 modulo 10 = 6; proven strategy).
• Validation: 457 workflow/shared-component frontmatter mappings and 83 reference-document YAML examples containing on checked with a local Draft-07 validator. Shared components received a synthetic on solely for this structural check; redirect-only stubs were excluded. These counts are a scoped structural audit, not full compilation coverage.

Key Issues

1. Schema rejects implemented on.slash_command.placeholder (medium). The documented example cannot pass frontmatter schema validation, despite compiler support. Add the string property to the slash-command object schema and cover acceptance plus footer propagation.
2. Two shared components declare unsupported import-schema type integer (medium). Five declarations contradict the schema's supported type enum; the input validator also has no integer case. Replace these declarations with number, or introduce integer support consistently across schema, validation, and documentation.
3. Reusable-workflow documentation recommends unsupported choice inputs (medium). The worker example specifies both type: choice and options, which the workflow_call.inputs schema rejects. Use string and explain worker-side allowed-value validation; review compiler tests that currently treat choice as supported.
4. Generated full frontmatter reference is not parseable YAML (low). Object-array children appear beneath field: [] without a sequence marker. Fix the generator, regenerate the reference, and add a YAML parse check.

Evidence, impacts, and concrete fixes

1. Slash-command placeholder: schema ↔ compiler ↔ documentation

• docs/src/content/docs/reference/command-triggers.md:204 demonstrates on.slash_command.placeholder: to review this PR.
• pkg/workflow/frontmatter_extraction_yaml.go:270 reads commandMap["placeholder"].
• pkg/workflow/compiler_pre_activation_job.go:377 propagates CommandPlaceholder into the activation step.
• pkg/parser/schemas/main_workflow_schema.json:752 defines slash-command configuration, with additionalProperties: false and no placeholder property.
• Direct schema validation rejects the documented object. pkg/parser/schema_validation.go:198 invokes schema validation before engine-specific checks.
• Fix: add the implemented string property and its description to the schema; retain the existing documentation example as a regression fixture.

2. Unsupported integer input declarations: workflows ↔ schema ↔ parser

• .github/workflows/shared/cache-memory-trending.md:35, :39, and :43 declare retention-days, backfill-threshold, and backfill-window as integer.
• .github/workflows/shared/repo-memory-standard.md:22 and :26 do the same for max-patch-size and max-file-size.
• pkg/parser/schemas/main_workflow_schema.json:14107 permits string, number, boolean, choice, and array for scalar/array parameter definitions, with a separate object branch; it excludes integer.
• pkg/parser/import_schema_validation.go:122 handles number, but the switch has no integer branch. This is a declaration mismatch, not evidence that an invalid runtime value was accepted by the full compiler.
• docs/src/content/docs/reference/imports.md:125 demonstrates the supported numeric type number.
• These components are imported by api-consumption-report.md, copilot-agent-analysis.md, and other workflows, so the mismatch extends beyond unused examples.
• Fix: prefer number for the immediate correction. If whole-number enforcement is intended, implement and document integer rather than silently declaring it.

3. Unsupported workflow_call choice inputs: documentation ↔ schema

• docs/src/content/docs/reference/safe-outputs.md:1479 presents a worker with environment.type: choice and options: [dev, staging, production]; the following prose lists choice as supported.
• pkg/parser/schemas/main_workflow_schema.json:2074 restricts reusable-workflow input types to string, number, and boolean; input objects also reject the additional options property.
• pkg/workflow/safe_outputs_call_workflow_test.go:311 exercises extraction of a choice input, which does not demonstrate acceptance through the main frontmatter schema.
• Fix: change the worker example to type: string, remove options, document explicit value validation, and align compiler tests with the reusable-workflow input contract. Keep workflow-dispatch choice examples separate.

4. Invalid generated YAML: documentation generator ↔ reference

• docs/src/content/docs/reference/frontmatter-full.md:72 emits threat-detection-suppress: [], followed by indented rule, reason, and expires mappings without -.
• A YAML parser fails at rule (line 75 of the document), before JSON Schema validation can run.
• scripts/generate-schema-docs.js:336 emits propName: [] for arrays and then emits object item properties at line 343.
• Fix: generate either an actual sequence item with correctly aligned child properties or an empty array followed by fully commented illustration text. Regenerate the reference and verify the complete block parses.

Ruled-out leads and limitations

• The precomputed top-level gaps docker-image-pull-policy and work-queue-policy are false positives from tag-only enumeration: consumers exist at pkg/workflow/docker.go:294 and pkg/workflow/work_queue_repo_config.go:32.
• No unknown top-level keys were found in the precomputed actual-workflow key set. The bulk validation flagged seven raw shared components; template-expression errors were not counted as confirmed violations because import substitution can resolve them. Only the unsupported integer declarations above were retained.
• The generated full reference could not join the 83 parsed documentation examples because its YAML syntax fails first. This audit did not execute workflow code or trigger workflow runs.
• Non-authoritative AWF warning: /tmp/gh-aw/agent/awf-config-drift.json has degraded: true; canonical-source retrieval failed. No AWF config-source drift conclusion, corrective PR, drift issue, or required-check failure is warranted from that comparison.

Recommendations and Next Steps

• Add slash_command.placeholder to the schema and verify the documented example.
• Correct the five shared-component numeric type declarations or implement integer validation consistently.
• Correct the reusable-worker input example and align relevant extraction tests.
• Repair object-array generation and verify regenerated reference YAML parses.

Strategy performance: 4 confirmed findings; high effectiveness; reuse recommended. Raw field gaps and unresolved import templates need targeted verification to avoid false positives. The strategy cache was updated; repository source files were unchanged.

References: §38352278753

Generated by ✅ Schema Consistency Checker · codex · gpt61 · 18.6 AIC · ⌖ 6.91 AIC · ⊞ 19.1K · ◷

• expires on Oct 13, 2026, 9:41 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 #68617.