Safe output was created but no pull request safe output handler happened

[dsyme]

This run is strange, there is a safe output but no safe output handler was invoked for the PR

https://github.com/fsprojects/FSharp.Data/actions/runs/22520621714

[dsyme]

Safe output data looks ok

{
    "body": "🤖 *This PR was created by Repo Assist, an automated AI assistant, working on #1678.*\n\nPart of the documentation effort requested in #1678 — adds XML doc comments to four source files covering the core conversion APIs.\n\n## What changed\n\nAdded `<summary>`, `<param>`, and `<returns>` XML doc comments to all previously undocumented public methods in:\n\n- **`JsonConversions.fs`** — all 11 static conversion methods (`AsString`, `AsInteger`, `AsInteger64`, `AsDecimal`, `AsFloat`, `AsBoolean`, `AsDateTime`, `AsDateTimeOffset`, `AsTimeSpan`, `AsDateOnly`, `AsTimeOnly`, `AsGuid`)\n- **`TextConversions.fs`** — all public static conversion methods (`AsInteger`, `AsInteger64`, `AsDecimal`, `AsFloat`, `AsBoolean`, `AsDateTime`, `AsDateTimeOffset`, `AsTimeSpan`, `AsDateOnly`, `AsTimeOnly`, `AsGuid`)\n- **`CsvExtensions.fs`** — all `StringExtensions` public extension methods (9 methods)\n- **`CsvFile.fs`** — `Parse`, `Load` (stream overload), `Load` (TextReader overload), `Load` (URI overload), and `AsyncLoad` static methods\n\nExisting `///` style comments were retained or replaced with proper XML doc format where arguments were involved. Internal/private members were not touched.\n\n## Test Status\n\n- ✅ `src/FSharp.Data.Runtime.Utilities` — builds successfully\n- ✅ `src/FSharp.Data.Json.Core` — builds successfully (0 errors)\n- ✅ `src/FSharp.Data.Csv.Core` — builds successfully (0 errors)\n- ✅ Fantomas formatting check — all 4 files unchanged (already correctly formatted)",
    "branch": "repo-assist/docs-issue-1678-json-csv-text-conversions",
    "labels": "documentation",
    "title": "Add XML doc comments to JsonConversions, TextConversions, CsvExtensions, CsvFile",
    "type": "create_pull_request",
    "patch_path": "/tmp/gh-aw/aw-repo-assist-docs-issue-1678-json-csv-text-conversions.patch"
}

[dsyme]

Oh it was rejected because of the title-prefix perhaps. Is the title prefix a rejection condition or is it automatically added?

If it's a rejection condition we should not reject an entire PR, we should just add the prefix.

EIther way we should strengthen our generated prompting for all safe outputs that have a title-prefix configuration option.