Description
Today's Schema Consistency Checker (discussion #54161) found that strict: is documented and schema-defined with a default of true (docs/src/content/docs/reference/frontmatter.md, pkg/parser/schemas/main_workflow_schema.json), and the MCP compile tool explicitly injects strict=true (pkg/cli/mcp_tools_readonly.go) — but the regular CLI compile path (pkg/cli/compile_compiler_setup.go, compiler.SetStrictMode(config.Strict)) does not show the same explicit default, applying config.Strict directly instead.
This is a follow-on to previously-closed #49893 (which removed the MCP tool's forced strict default to fix unwanted lock-file diffs, #49482) — worth checking whether that change left the plain CLI flag path with no default at all, silently contradicting the docs/schema promise of strict-by-default.
Expected Impact
If config.Strict is actually false-by-default on the ordinary gh aw compile path, validation is silently weaker than documented for the most common invocation. Aligning it (or fixing the docs if the product intent has changed) closes a real correctness/docs gap.
Suggested Agent
General-purpose engineering agent — audit pkg/cli/compile_compiler_setup.go and its CLI flag registration for the actual default of config.Strict, compare against schema/docs/MCP tool behavior, and reconcile.
Estimated Effort
Quick (< 1 hour) to confirm; Medium if a code fix + tests are needed.
Data Source
DeepReport Intelligence analysis, 2026-08-20 cycle, based on Schema Consistency Checker discussion #54161.
Generated by 🔬 Deep Report · agent · 175.8 AIC · ⌖ 9.08 AIC · ⊞ 11.9K · ◷
Description
Today's Schema Consistency Checker (discussion #54161) found that
strict:is documented and schema-defined with a default oftrue(docs/src/content/docs/reference/frontmatter.md,pkg/parser/schemas/main_workflow_schema.json), and the MCP compile tool explicitly injectsstrict=true(pkg/cli/mcp_tools_readonly.go) — but the regular CLI compile path (pkg/cli/compile_compiler_setup.go,compiler.SetStrictMode(config.Strict)) does not show the same explicit default, applyingconfig.Strictdirectly instead.This is a follow-on to previously-closed #49893 (which removed the MCP tool's forced strict default to fix unwanted lock-file diffs, #49482) — worth checking whether that change left the plain CLI flag path with no default at all, silently contradicting the docs/schema promise of strict-by-default.
Expected Impact
If
config.Strictis actually false-by-default on the ordinarygh aw compilepath, validation is silently weaker than documented for the most common invocation. Aligning it (or fixing the docs if the product intent has changed) closes a real correctness/docs gap.Suggested Agent
General-purpose engineering agent — audit
pkg/cli/compile_compiler_setup.goand its CLI flag registration for the actual default ofconfig.Strict, compare against schema/docs/MCP tool behavior, and reconcile.Estimated Effort
Quick (< 1 hour) to confirm; Medium if a code fix + tests are needed.
Data Source
DeepReport Intelligence analysis, 2026-08-20 cycle, based on Schema Consistency Checker discussion #54161.