Fix assign_to_agent validation to support both issue_number and pull_number

[Copilot]

The assign_to_agent safe output validation required issue_number as mandatory, but the handler accepts either issue_number OR pull_number for assigning agents to issues or pull requests. This mismatch caused validation failures when attempting to assign agents to PRs.

Changes

Validation config (pkg/workflow/safe_output_validation_config.go):

• Changed issue_number from required to optional (OptionalPositiveInteger)
• Added pull_number field as optional (OptionalPositiveInteger)
• Added CustomValidation: "requiresOneOf:issue_number,pull_number" to enforce exactly-one semantics

Test config (pkg/workflow/safe_output_validation_config_test.go):

• Added "requiresOneOf:issue_number,pull_number" to valid custom validation rules

JavaScript validator tests (actions/setup/js/safe_output_type_validator.test.cjs):

• Added test coverage for all three validation states: issue_number only (✓), pull_number only (✓), neither (✗)

Example

# Both are now valid:
- type: assign_to_agent
  issue_number: 123
  agent: copilot

- type: assign_to_agent
  pull_number: 456
  agent: copilot

# This correctly fails validation:
- type: assign_to_agent
  agent: copilot  # Error: requires at least one of 'issue_number', 'pull_number'

The validation now matches the handler's actual behavior, preventing false negatives while maintaining safety guarantees.

Original prompt

Fix error in latest campaign generator run safe output (assign-to-agent):
https://github.com/githubnext/gh-aw/actions/runs/21065370327/job/60581785114
Do not call update_issue with empty payloads—always supply at least one valid field (body, title, or status).
Do not call assign_to_agent without specifying issue_number or pull_number.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.