Skip to content

[deep-report] Fix max-runs schema/parser inconsistency (schema allows 0, parser silently treats as unset) #56574

Description

@github-actions

Description

Schema Consistency Checker (#56553, finding 1) found that max-runs is schema-valid down to 0 (pkg/parser/schemas/main_workflow_schema.json via templatable_integer's minimum: 0), but the compiler's parsePositiveIntValue (pkg/workflow/engine_config_parser.go:31-46) silently requires >= 1 and treats 0 as unset/default. A workflow author can pass schema validation with max-runs: 0 and get silently different runtime behavior than what they configured.

Expected Impact

Removes a schema/runtime disagreement that could silently produce unexpected run-limit behavior; closes a validation gap that currently gives users false confidence their config is enforced.

Suggested Agent

New Agent / manual — either tighten the schema's minimum to 1 for max-runs, or make the parser accept and document 0's actual semantics explicitly.

Estimated Effort

Quick (< 1 hour)

Data Source

DeepReport analysis 2026-08-28 cycle, from Schema Consistency Checker #56553, finding 1 (verified live against pkg/workflow/engine_config_parser.go:31-46 and pkg/workflow/engine.go:233-245).

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

  • api.anthropic.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.anthropic.com"

See Network Configuration for more information.

Generated by 🔬 Deep Report · claude · agent · 131.9 AIC · ⌖ 9.14 AIC · ⊞ 12.4K ·

  • expires on Aug 30, 2026, 1:34 AM UTC-08:00

Metadata

Metadata

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions