Problem

When safe-outputs.create-pull-request is configured with protected-files: fallback-to-issue, the system automatically creates a fallback issue. However, the fallback issue is created by the safe-outputs system (not by the agent), so the separate safe-outputs.create-issue.assignees config is bypassed entirely. The create-pull-request config also does not support an assignees field, leaving no way to auto-assign the fallback issue.

Current Behavior

• safe-outputs.create-pull-request supports reviewers but not assignees
• When protected-files: fallback-to-issue triggers, the auto-created issue inherits no assignees
• The safe-outputs.create-issue.assignees config is not consulted for the fallback path

Expected Behavior

Either:

1. Add an assignees field to safe-outputs.create-pull-request that is applied to the fallback issue when protected-files: fallback-to-issue triggers, or
2. Have the fallback issue creation consult safe-outputs.create-issue.assignees automatically

Example Config

safe-outputs:
  create-pull-request:
    protected-files: fallback-to-issue
    title-prefix: "[ci-coach] "
    reviewers: [mcg]
    assignees: [mcg]   # ← currently rejected by compiler
  create-issue:
    title-prefix: "[ci-coach] "
    assignees: [mcg]   # ← not used for fallback issues

Workaround

None currently available. Users must manually assign fallback issues after the fact.