[Schema Consistency] 🔍 Schema Consistency Check — 2026-06-17

[github-actions[bot]]

Summary

• Inconsistencies Found: 3 open (1 HIGH, 2 LOW)
• Categories Analyzed: Schema ↔ Parser ↔ Documentation ↔ Workflows
• Strategy Used: strategy-28 tools.* sub-object struct-vs-schema diff (NEW)
• New Strategy: YES (day-of-year mod 10 = 8 → new approach)
• Good news: 2 previously-open findings are now RESOLVED in the schema.

This run took a fresh angle (every tools.* sub-object with additionalProperties:false) and re-verified all standing findings from cache.

Critical Issues

1. engine.extensions — triple gap (parser ✅ / schema ❌ / docs ❌) — HIGH

The parser reads and acts on engine.extensions:

pkg/workflow/engine.go:483  if extVal, hasExt := engineObj["extensions"]; hasExt {
pkg/workflow/engine.go:493  ... Extracted engine.extensions: ... (array of strings; used by the Pi engine)

But extensions is absent from every engine_config schema branch. A full diff of all engineObj[...] key-reads against the union of schema engine-config properties shows extensions is the only key the parser reads that the schema does not declare:

• Parser reads: agent, api-target, args, auth, bare, command, concurrency, config, copilot-sdk, copilot-sdk-driver, env, extensions, harness, id, max-continuations, max-turns, mcp, model, permission-mode, provider, runtime, token-weights, user-agent, version
• Schema declares the same set minus extensions (plus structural-only description, display-name, models, options, runtime-id).

Because the engine-config branches are additionalProperties:false, strict schema validation rejects a workflow that sets engine.extensions, even though it is a working feature. It is also undocumented in docs/src/content/docs/reference/.

Fix: add an extensions property (array of string) to the engine-config object branch(es) in pkg/parser/schemas/main_workflow_schema.json, and document it (Pi-engine usage).

Schema Improvements Needed

2. dispatch-repository (dash) alias not in schema — LOW

The parser explicitly accepts both spellings:

pkg/workflow/dispatch_repository.go:30  // Accepts both "dispatch_repository" (underscore, preferred) and "dispatch-repository" (dash, alias).
pkg/workflow/dispatch_repository.go:38  if configData, exists = outputMap["dispatch_repository"]; !exists { ... }

The schema declares only dispatch_repository (underscore). Under additionalProperties:false on safe-outputs, the documented dash alias is schema-rejected. Fix: either add dispatch-repository to the schema or drop the alias from the parser.

3. dispatch_repository naming inconsistency — LOW (cosmetic)

dispatch_repository is the sole snake_case key among otherwise kebab-case safe-output siblings (e.g. create-issue, create-pull-request, create-discussion). Cosmetic only; the dash alias above is the practical mitigation.

Resolved Since Last Run ✅

Two standing findings from the strategy cache are now fixed in the schema — re-verified this run:

• normalize-closing-keywords — now declared in the schema for create-issue, add-comment, and create-pull-request (exactly the three handlers that emit it: safe_outputs_handler_registry.go:29,49,472). Previously absent → rejected under additionalProperties:false. ✅
• create-discussion.required-category — now a direct property of the create-discussion schema branch (it was previously only under close-discussion). Read by create_discussion.go:25 and used for close-older matching. ✅

Investigated & Clean (this run's new approach)

tools.* sub-object struct-vs-schema diff — no gaps found

Checked every tools.* object with additionalProperties:false:

• tools.github — all parser-read keys (type, mode, github-token, lockdown, toolsets, allowed, allowed-repos, repos, min-integrity, version, github-app, ...) are declared in the schema.
• tools.repo-memory — parser accepts array notation where each entry has an id (repo_memory.go:48,171). The schema's repo-memory oneOf does include an array branch alongside boolean/null/object, so this is correctly covered (initial extraction that only read object .properties produced a false lead — branch types must be enumerated).
• tools.comment-memory, tools.cache-memory, tools.playwright — property sets align with parser usage.

No inconsistencies in this category.

safe-outputs github-app per-type coverage — asymmetric but low-confidence, not reported

github-app and github-token are both BaseSafeOutputConfig fields inlined onto every safe-output type struct. In the schema, github-token is declared on 41 of 55 type branches but github-app on only 1 (create-check-run). However, github-app is consumed at the top-level SafeOutputs config (compiler_safe_outputs_job.go:427), not per-type, so the per-type asymmetry is likely not a real functional gap. Flagged for a future confidence check rather than reported as a bug.

Recommendations

1. (HIGH) Add extensions: { type: array, items: { type: string } } to the engine-config object branch in main_workflow_schema.json and document it under the engines reference.
2. (LOW) Add dispatch-repository (dash) to the safe-outputs schema, or remove the dash alias from dispatch_repository.go so parser and schema agree on one spelling.
3. (LOW/cosmetic) Track dispatch_repository snake_case as a known naming exception (or migrate to dispatch-repository as the canonical key once the alias is in schema).

Strategy Performance

• Strategy Used: strategy-28 (tools.* struct-vs-schema diff) — NEW
• Findings (new approach): 0 new (category clean); re-confirmed 1 HIGH + 2 LOW from prior strategies
• Effectiveness: LOW for the new angle (tools.* is well-covered), HIGH for re-verification
• Should Reuse: Engine-config diff (strategy-25) and base-config diff (strategy-27) remain the highest-yield; tools.* diff is reusable but low-yield

Next Steps

• Add engine.extensions to schema + docs (HIGH)
• Reconcile dispatch-repository/dispatch_repository spelling between parser and schema (LOW)
• Future: extend struct-vs-schema diff to the remaining safe-output types; settle github-app per-type consumption confidence

Generated by ✅ Schema Consistency Checker · ◷

• expires on Jun 17, 2026, 11:08 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 #40011.