Capped max items in update-discussion safe output

[mnkiefer]

A user reported the following error where max items for update-discussion safe output is capped at 100. This seems to be a hard limit enforced by the schema for safe-outputs which is probably in place to prevent runaway agents from making massive changes in a single execution. From the user-based perspective, this is not ideal since to run more than 100 updates, they would need to run multiple choice.

error: 'safe-outputs/update-discussion' (line 31, col 21): at '/safe-outputs/update-discussion': 'oneOf' failed, none matched
- at '/safe-outputs/update-discussion/max': 'oneOf' failed, none matched
  - at '/safe-outputs/update-discussion/max': maximum: got 120, want 100
  - at '/safe-outputs/update-discussion/max': got number, want string
- at '/safe-outputs/update-discussion': got object, want null. Expected format: {"body":null,"labels":null,"title":null}
28 |   staged: true
29 |   github-token: ${{ secrets.READ_DISCUSSIONS_TOKEN }}
30 |   allowed-github-references: [community/community-ops]
31 |   update-discussion:
32 |     max: 120
33 |     target: "*"
34 |     target-repo: mona-lisa/octocat

✗ compilation failed

[mnkiefer]

• Works as designed. Decided to keep max as 100 to align with other safe outputs caps.