[deep-report] Fix inverted strict: mode documentation in frontmatter reference #52086

Description

docs/src/content/docs/reference/frontmatter.md describes strict: mode backwards. It says setting strict: false is for "Disable[d] for development/testing" and that strict "Disables enhanced security validation for production workflows," implying strict: true is the weaker/looser setting. The schema (pkg/parser/schemas/main_workflow_schema.json) and compiler (pkg/workflow/strict_mode_update_check_validation.go) both confirm the opposite: strict defaults to true and is the stronger security/compliance mode — it rejects check-for-updates: false, for example, only when strictMode is true.

A user following the docs literally could set strict: false believing they're tightening security, when they're actually weakening it.

Expected Impact

Prevents users from unintentionally weakening workflow security posture due to backwards documentation. Small, surgical text fix in one reference page.

Suggested Agent

Docs-focused agent (e.g. a documentation-quality or schema-consistency workflow) or a human PR.

Estimated Effort

Quick (< 1 hour)

Data Source

DeepReport analysis 2026-08-11, sourced from Schema Consistency Check discussion #51954 (2026-08-11).

Generated by 🔬 Deep Report · agent · 142.3 AIC · ⌖ 47.8 AIC · ⊞ 11.4K · ◷

• expires on Aug 13, 2026, 7:07 AM UTC-08:00