[throw101010]

I'd open a Draft PR and an Issue to explain the problems you encountered and how you've solved them for your own use cases... then leave it up to them to learn from it or close it.

I get annoyed with "drive-by PRs" only when they lack context or are clearly just a way to get some commits into a project (typos and so on), but any findings that can improve my code or its performance is welcome, in my projects at least.

[Rapzid]

This is a great comment. As someone who has been involved in managing a large (business backed) OSS project I can say that even if we preferred to have our own solutions to issues, we really valued comprehensive issues and draft PRs to reference.

Sometimes you just don't have the time to get a PR to a projects mergeable standards, but the solution as a reference can have a ton of value for those that eventually get a PR across the finish line.

I would say, though, that agentic coding seriously complicates the entire situation...