Maintainer direction requested: an upstream-first Canny migration mission

[alibad]

I run SaaSassin, a new coordination project for verified migrations from closed SaaS products to credible open-source projects. We selected Canny → Fider as the first proving mission because Canny documents export paths and Fider is already the credible open project in this category.

This is not a request to begin implementation, and we will not present a fork as a replacement. Fider's contribution guide says new feature ideas should begin as a suggestion before a GitHub issue, so I am asking for direction first.

Our proposed discovery scope is to interview five current or recent Canny users, recruit one design partner with a permissioned export, document a field-level mapping, and produce a dry-run loss report. Only work accepted through Fider's process would be proposed upstream; Canny-specific conversion can remain separate if that is healthier for Fider.

The public charter is: https://saasassin.net/missions/canny-fider

Which channel should we use for the migration proposal, and what constraints or ownership expectations should we record before recruiting builders?