Skip to content

[deep-report] Add normalize-closing-keywords to safe-output schema branches (documented feature un-schemable) #39597

@github-actions

Description

@github-actions

Description

normalize-closing-keywords is a BaseSafeOutputConfig field (pkg/workflow/compiler_types.go:640) inlined onto every safe-output type and actively emitted by three handlers — pkg/workflow/safe_outputs_handler_registry.go:29 (create_issue), :49 (add_comment), :472 (create_pull_request). It is documented as a user-facing feature, yet it appears 0 times in pkg/parser/schemas/main_workflow_schema.json. Because every safe-output object branch is additionalProperties: false, any workflow that sets it fails schema validation despite the field being fully implemented and documented.

Fix: add normalize-closing-keywords (boolean) to the create-issue, add-comment, and create-pull-request object branches in the schema.

Expected Impact

Eliminates spurious validation failures for a documented, working feature. Highest-impact item of the schema-consistency cluster this run.

Suggested Agent

Schema Consistency agent (or a focused schema-fix workflow).

Estimated Effort

Quick (< 1 hour)

Data Source

DeepReport Intelligence Briefing 2026-06-16 · Schema Consistency Check #39506 (HIGH, new). Verified this run: grep -c "normalize-closing-keywords" main_workflow_schema.json0; struct + 3 handler emit sites present.

Generated by 🔬 DeepReport - Intelligence Gathering Agent · 321.6 AIC · ⌖ 18.6 AIC · ⊞ 10K ·

  • expires on Jun 18, 2026, 8:25 AM UTC-08:00

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions