[Schema Consistency] 🔍 Schema Consistency Check - 2026-10-16

[github-actions[bot]]

Overview

Found 3 inconsistencies in deprecated work-queue-policy configuration. Reviewed schema, parser/compiler, documentation, and workflow usage. No critical issue established. Source was inspected read-only; only the strategy cache was updated.

• Strategy: Nested configuration interaction audit (new approach; day 289 modulo 10 = 9).
• Evidence: Four inert JSON configurations validated with the local Draft7 schema, plus static compiler control-flow inspection.
• Workflow coverage: 459 workflow/shared-component frontmatter documents parsed; zero unknown top-level keys and zero YAML parse failures. This does not establish full type, value, import, or compilation consistency.

Key Issues

1. Medium — Explicit pools silently discard shorthand outstanding limits. The schema accepts pools.default.logical-limit: 16, native-limit: 16, and outstanding: {claims: 1, dispatches: 1} together. The compiler modifies a local copy of the default pool, then writes it back only when explicit pools are absent. Thus the configured limits remain 16 instead of the requested shorthand limits of 1. The same writeback condition discards shorthand dependency observation-age/repository changes with explicit pools. Reject ambiguous combinations or define and implement their precedence. This concerns proposed configuration; no installed Policy or historical result was altered.

2. Low — Schema permits mutually exclusive profile forms. A complete configuration containing both worker-profiles and pools passes schema validation, but the compiler explicitly rejects it with worker-profiles shorthand cannot be combined with pools. Add a schema exclusion matching the existing parser restriction.

3. Low — Dependency duration contract differs between schema and parser. The schema rejects max-observation-age: 1h, although the parser uses Go duration parsing and its error advertises an inclusive range through 1h. Conversely, 61m passes the schema but exceeds the compiler limit. Align accepted syntax and document where semantic duration bounds are enforced.

Evidence and analysis details

Schema ↔ Parser

All source links refer to the inspected commit.

• Finding 1: Schema independently permits outstanding and pools. The compiler copies the default pool, applies shorthand helpers, and conditionally saves it at work_queue_policy.go:207. The outstanding helper assigns the requested limits at line 292. A synthetic schema case with explicit pools and outstanding limits was accepted. The compiler conclusion is based on static assignment tracing, not an end-to-end compilation.
• Finding 2: The schema defines both properties at main_workflow_schema.json:39 without mutual exclusion. The parser rejects the combination at work_queue_policy.go:235. The synthetic schema case supplied complete profile, pool, and producer definitions and was accepted.
• Finding 3: The schema pattern is ^[1-9][0-9]*(ms|s|m)$ at main_workflow_schema.json:123; the compiler parses durations and enforces 1ms–1h at work_queue_policy.go:308. Synthetic schema results: 1h rejected; 61m accepted.

Documentation Gaps

The work-queue reference correctly marks workflow policy configuration deprecated and recommends repository aw.json settings. No independent documentation defect is asserted. When resolving these legacy inconsistencies, explain rejected shorthand/explicit combinations and accepted duration syntax without promoting legacy configuration for new workflows.

Workflow Violations and False Positives

The supplied diff reports no top-level workflow keys outside the schema; the additional scan included shared components and confirmed this bounded result. No workflow violation was established. The two apparent top-level struct gaps are handled via raw frontmatter: docker-image-pull-policy in pkg/workflow/docker.go:294, and work-queue-policy in pkg/workflow/work_queue_policy.go:184. Missing YAML struct tags alone are not evidence of unsupported fields.

AWF Canonical Source Warning — Non-authoritative

The precomputed AWF comparison has degraded: true: canonical config-source retrieval failed. No authoritative AWF drift conclusion is possible from this run. This warning is excluded from the inconsistency count; it does not warrant failing a required check, creating a drift issue, or creating a corrective pull request.

Strategy Performance

• Findings: 3; effectiveness: medium; should reuse: yes.
• Successful method: trace interactions between schema-accepted nested forms and compiler copy/writeback conditions, rather than treating field-tag differences as bugs.
• Saved as strategy-6 in the strategy database.
• Validation limits: targeted schema checks and static code review; no compiler execution, unit suite, workflow run, or infrastructure probing.

Recommendations and Next Steps

• Reject shorthand outstanding/dependency policy settings with explicit pools, or implement documented precedence; preserve separately supported credential-only behavior. Add a focused regression test for resolved limits.
• Add schema mutual exclusion for worker-profiles and pools, with a schema regression case.
• Reconcile duration syntax and bounds between schema and compiler; verify 1ms, 60m, 1h, and 61m boundaries.
• Update legacy compatibility guidance alongside the selected behavior; continue recommending repository scheduling configuration.
• Re-run the targeted checks after changes. No workflow edits are justified by this scan.

References: §38856151565

Generated by ✅ Schema Consistency Checker · codex · gpt61 · 18.8 AIC · ⌖ 6.95 AIC · ⊞ 19.5K · ◷

• expires on Oct 16, 2026, 9:35 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 #69633.