You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Areas analyzed: schema, parser/compiler, documentation, and targeted workflow usage
Strategy: guardrail data-flow and generated-example audit; new strategy
Priority: correct the daily credit default and preserve configured turn limits.
Critical Issues
Daily credit default is described incorrectly. The schema and frontmatter reference say omission disables the guardrail. The compiler instead resolves the Actions variable or a 5,000-credit default; the cost guide agrees with the compiler. Authors may be surprised by skipped runs. Update schema and reference text, regenerate the full reference, and test omitted, overridden, and explicitly disabled cases.
Expression-valued turn limits do not reach the AWF proxy cap. The schema accepts expressions for max-turns and deprecated max-runs. Extraction preserves max-turns for engine configuration but converts it to an integer for maxRuns; the conversion discards expressions, and AWF configuration falls back to 500 unless a numeric legacy max-runs is present. An expression-valued max-runs is similarly discarded. Other engine-specific turn enforcement may still apply, but the documented proxy limit does not follow the expression. Preserve and validate runtime expressions in the proxy cap, or reject unsupported forms and document the limitation; test expression values above and below 500 and precedence with legacy max-runs.
Documentation Gaps
Generated expression examples are invalid. The full reference presents timeout-minutes: example-value as the expression format; the same occurs for max-turns and max-tool-denials. The schema requires the Actions expression wrapper, and typed parsing rejects ordinary strings. Generate a valid expression for patterned string branches and validate generated examples against their schema.
Schema Improvements Needed
Zero is accepted for limits that the compiler ignores.max-turns and max-tool-denials use the nonnegative templatable integer definition, so 0 passes schema validation. Their parsers require a positive integer and return an unset value for zero; existing tests confirm this. The requested value silently becomes a default or absent limit. Use a positive-integer schema if zero is unsupported, or implement and document explicit zero semantics. Cover both fields in compilation tests.
Parser Updates Required
Address expression propagation and zero handling above, with tests that inspect the generated proxy configuration as well as engine settings.
Workflow Violations
The precomputed top-level usage diff showed no keys outside the schema. Targeted searches found ordinary numeric turn-limit usage and explicit daily-credit opt-outs; this was not an exhaustive validation of every workflow or nested field. The four apparent top-level struct gaps include fields handled through raw frontmatter and are not by themselves violations.
Scope and source availability
Canonical AWF configuration sources were unavailable in the precomputed comparison. Any AWF config-source drift assessment is therefore non-authoritative; no drift finding is asserted. This report is based on repository schema, compiler code, documentation, existing tests, and targeted workflow searches; it did not execute workflows or perform live runs.
Recommendations
Align the daily credit default across schema and reference documentation.
Resolve and test expression and zero behavior for turn-related limits at the generated proxy boundary.
Generate schema-valid examples and validate them automatically.
Strategy Performance
Strategy: guardrail data-flow and generated-example audit
Findings: 4; effectiveness: high; reuse: yes
Next Steps
Fix schema descriptions and limit constraints.
Update compiler handling and focused tests.
Regenerate and validate documentation examples.
Review affected workflows when behavior is corrected.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
🔍 Schema Consistency Check - 2026-11-14
Summary
Critical Issues
Daily credit default is described incorrectly. The schema and frontmatter reference say omission disables the guardrail. The compiler instead resolves the Actions variable or a 5,000-credit default; the cost guide agrees with the compiler. Authors may be surprised by skipped runs. Update schema and reference text, regenerate the full reference, and test omitted, overridden, and explicitly disabled cases.
Expression-valued turn limits do not reach the AWF proxy cap. The schema accepts expressions for max-turns and deprecated max-runs. Extraction preserves max-turns for engine configuration but converts it to an integer for maxRuns; the conversion discards expressions, and AWF configuration falls back to 500 unless a numeric legacy max-runs is present. An expression-valued max-runs is similarly discarded. Other engine-specific turn enforcement may still apply, but the documented proxy limit does not follow the expression. Preserve and validate runtime expressions in the proxy cap, or reject unsupported forms and document the limitation; test expression values above and below 500 and precedence with legacy max-runs.
Documentation Gaps
timeout-minutes: example-valueas the expression format; the same occurs for max-turns and max-tool-denials. The schema requires the Actions expression wrapper, and typed parsing rejects ordinary strings. Generate a valid expression for patterned string branches and validate generated examples against their schema.Schema Improvements Needed
0passes schema validation. Their parsers require a positive integer and return an unset value for zero; existing tests confirm this. The requested value silently becomes a default or absent limit. Use a positive-integer schema if zero is unsupported, or implement and document explicit zero semantics. Cover both fields in compilation tests.Parser Updates Required
Address expression propagation and zero handling above, with tests that inspect the generated proxy configuration as well as engine settings.
Workflow Violations
The precomputed top-level usage diff showed no keys outside the schema. Targeted searches found ordinary numeric turn-limit usage and explicit daily-credit opt-outs; this was not an exhaustive validation of every workflow or nested field. The four apparent top-level struct gaps include fields handled through raw frontmatter and are not by themselves violations.
Scope and source availability
Canonical AWF configuration sources were unavailable in the precomputed comparison. Any AWF config-source drift assessment is therefore non-authoritative; no drift finding is asserted. This report is based on repository schema, compiler code, documentation, existing tests, and targeted workflow searches; it did not execute workflows or perform live runs.
Recommendations
Strategy Performance
Next Steps
References: §43561302208
All reactions