[deep-report] Add missing repository_dispatch to user-rate-limit.events schema enum #52087

Description

pkg/parser/schemas/main_workflow_schema.json restricts user-rate-limit.events to a fixed enum (workflow_dispatch, issue_comment, pull_request_review, pull_request_review_comment, issues, pull_request, discussion_comment, discussion) that omits repository_dispatch. But pkg/workflow/role_checks.go already includes repository_dispatch in programmaticTriggers when auto-inferring rate-limited events from a workflow's on: block. Because schema validation uses additionalProperties: false-style enum enforcement, an author cannot explicitly declare events: [repository_dispatch] even though the compiler already treats it as a valid inferred trigger.

Expected Impact

Closes a schema/compiler mismatch so repository_dispatch-triggered workflows can explicitly configure user-rate-limit, matching what the compiler already infers implicitly. Prevents confusing validation failures for authors trying to be explicit.

Suggested Agent

Schema-consistency workflow or a small direct PR to main_workflow_schema.json.

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