[Schema Consistency] Schema Consistency Check — 2026-06-01

[github-actions[bot]]

Summary

• Inconsistencies found: 10 (all verified against current main)
• Categories analyzed: Schema ↔ Parser, Schema ↔ Docs, Schema ↔ Workflows, Parser ↔ Docs
• Strategies used: 12 proven detection strategies from cache + 1 new (strategy-19, naming-convention consistency)
• New strategy this run: ✅ Yes — safe-output key naming/plurality consistency
• Status: ⚠️ Consistent core, several low/medium hygiene gaps persist

Day-of-year selection landed in proven-strategy mode (152 mod 10 = 2). All previously-cached findings were re-verified against the current tree and still reproduce, and two new findings were discovered via a fresh naming-convention strategy.

Critical Issues

None. No correctness bug that would let an invalid value silently compile was found this run. All issues below are documentation, deprecation-signalling, or naming-hygiene gaps.

Schema ↔ Parser / Compiler Mismatches

#	Finding	Evidence	Severity
1	applyTo is accepted by the parser allowlist but is not a schema property and is undocumented	pkg/parser/include_processor.go:267 ("applyTo": true in validFields); absent from main_workflow_schema.json properties	medium
2	Dead $def: templatable_integer is defined but never $ref'd	main_workflow_schema.json — templatable_integer occurs once (the definition only); sibling templatable_boolean is referenced 10×	low
3	create-code-scanning-alert plural/singular split	Schema key + parse handler are singular (pkg/workflow/create_code_scanning_alert.go:24 reads outputMap["create-code-scanning-alert"]), but the Go struct yaml tag is plural create-code-scanning-alerts (pkg/workflow/compiler_types.go:647). The plural tag is effectively dead since parsing uses manual map access.	low-medium
4	dispatch_repository breaks the kebab-case convention	main_workflow_schema.json safe-outputs key uses snake_case dispatch_repository while every sibling (e.g. dispatch-workflow, create-issue) uses kebab-case	low

Schema ↔ Documentation Mismatches

#	Finding	Evidence	Severity
5	Three top-level fields have zero mentions in any curated doc	check-for-updates, disable-model-invocation, run-install-scripts — 0 hits in docs/src/content/docs/reference/frontmatter.md and sibling reference pages (excluding auto-generated frontmatter-full.md)	medium
6	Broken in-schema doc anchors	check-for-updates and run-install-scripts schema descriptions link to reference/frontmatter/#<field> anchors that have no matching heading in frontmatter.md	medium
7	user-invokable (in IgnoredFrontmatterFields, pkg/constants/constants.go:315) is silently dropped but appears nowhere in docs/	grep of docs/ returns no hits	low

Deprecation-Signalling Gaps

#	Finding	Evidence	Severity
8	inline-sub-agents description begins "Deprecated switch..." but .deprecated is null and it has no x-deprecation-message	main_workflow_schema.json (schema otherwise uses deprecated:true + x-deprecation-message in 14 places, so this is a genuine omission)	medium
9	rate-limit description begins "Legacy alias for 'user-rate-limit'" but .deprecated is null, no x-deprecation-message, and the parser only logs the legacy use at debug level (pkg/workflow/role_checks.go:301, roleLog.Print) — no user-visible deprecation warning	medium

Default-Value Inconsistency

#	Finding	Evidence	Severity
10	expires default is asymmetric across siblings	Schema sets default: 7 on create-discussion.expires but create-issue.expires has no default (null)	low

Dead / Defensive Allowlist Entries (observations)

SharedWorkflowForbiddenFields in pkg/constants/constants.go references command and roles, which are not top-level schema properties (the top-level schema is additionalProperties:false). These are harmless but dead/defensive entries worth pruning or documenting.

Recommendations

1. Add deprecated: true + x-deprecation-message to inline-sub-agents and rate-limit so tooling and editors surface the deprecation (findings 8, 9). For rate-limit, also emit a user-visible warning instead of a debug-only log.
2. Document or remove check-for-updates, disable-model-invocation, run-install-scripts, and fix their broken #<field> doc anchors (findings 5, 6).
3. Resolve applyTo: either add it to the schema + docs, or remove it from the parser validFields allowlist (finding 1).
4. Reconcile create-code-scanning-alert singular/plural: align the Go struct yaml tag (compiler_types.go:647) with the singular schema key, or add a documented alias (finding 3).
5. Normalize dispatch_repository to kebab-case (or document the intentional exception) for convention consistency (finding 4).
6. Prune dead entries: remove templatable_integer def, and command/roles from SharedWorkflowForbiddenFields if no longer needed; document user-invokable (findings 2, 7, observations).

Strategy Performance

• Proven strategies re-confirmed: 7, 8, 9, 10, 12, 13, 15, 16, 17 — all still reproduce on current main.
• New strategy: strategy-19 (safe-output key naming/plurality consistency) — 2 new findings, effectiveness HIGH, will reuse.
• Effectiveness: HIGH for deprecation/doc/naming audits; LOW for raw field_gaps diff (noisy due to map-access fields and flattened nested keys).

Next Steps

• Add deprecation flags + messages (inline-sub-agents, rate-limit)
• Document or remove 3 zero-doc fields + fix broken anchors
• Resolve applyTo schema/allowlist mismatch
• Reconcile create-code-scanning-alert singular/plural and dispatch_repository casing
• Prune dead $def / forbidden-field entries

---

Note: a parallel multi-agent fan-out was attempted but the dynamic workflow required interactive approval unavailable in this headless run; analysis fell back to batched inline detection. All findings above are independently verified against the current tree.

Generated by ✅ Schema Consistency Checker · opus48 1M · ◷

• expires on Jun 2, 2026, 7:04 AM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Schema Consistency Checker.

A newer discussion is available at Discussion #36416.