[deep-report] on.stop-after is dynamically parsed but has no typed frontmatter field (schema/parser drift)

[github-actions]

Problem

The stop-after field (nested under on:) is documented and actively parsed at runtime, but has no corresponding typed struct field — it's only accessible via dynamic map[string]any extraction. This is a schema/parser/docs-drift risk class: a field can silently stop being read correctly if the dynamic key name ever diverges from the docs, and nothing in the type system would catch it.

Evidence

• pkg/workflow/stop_after.go:16-46 (extractStopAfterFromOn()) reads stop-after dynamically from the parsed frontmatter map rather than from a typed field.
• docs/src/content/docs/reference/frontmatter-full.md:865+ documents stop-after as a supported on: field.
• Source: Schema Consistency discussion #56834, finding 2.

Suggested action

Add a typed field for stop-after to the relevant frontmatter config struct (mirroring how other on: fields are typed), and have extractStopAfterFromOn() read from the typed field instead of the dynamic map. This closes the drift gap and makes future doc/schema/parser mismatches for this field detectable at compile time or via existing consistency tests.

Acceptance criteria

• stop-after has a typed field in the frontmatter config struct.
• extractStopAfterFromOn() (or its successor) reads from the typed field.
• Existing tests updated/added to cover the typed extraction path.

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 · 258.7 AIC · ⌖ 8.26 AIC · ⊞ 12.4K · ◷

• expires on Aug 30, 2026, 10:49 PM UTC-08:00

[pelikhan]

@copilot allow GitHub expression.