[deep-report] JSON Schema missing organization-custom-org-roles / organization-custom-repository-roles permission fields

[github-actions]

Problem

organization-custom-org-roles and organization-custom-repository-roles are supported permission fields in the Go types and documented, but they are missing from the JSON Schema, so workflows using them would not get schema-validated (or would be flagged as invalid by external tooling/editors that validate against the schema).

Evidence

• pkg/workflow/frontmatter_types.go:86,88 (GitHubAppPermissionsConfig) defines both fields.
• Documented at docs/src/content/docs/reference/frontmatter.md:186.
• Missing from $defs.github_actions_permissions.properties in the JSON Schema.
• Source: Schema Consistency discussion #56834, finding 3.

Suggested action

Add organization-custom-org-roles and organization-custom-repository-roles to $defs.github_actions_permissions.properties in the JSON Schema so schema-validated editors/tools recognize these already-supported fields.

Acceptance criteria

• Both fields are present in the JSON Schema's github_actions_permissions definition with correct types.
• A workflow frontmatter using either field validates cleanly against the schema.

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 网络 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