Ecosystem guidance – copilot-plugins vs. awesome-copilot (vs. self-published)? #35

Hi! I’m the author of flutter-slipstream, a plugin and MCP server that gives coding agents runtime inspection and interaction capabilities for Flutter apps. It currently supports Claude Code and Gemini CLI and I'm gearing up to support Copilot.

I'm trying to figure out the best path for distribution and could use some guidance. I like the improved discovery that comes with official marketplaces, but I want to make sure I'm putting the tool in the right place without bottlenecking my release cycle. I have two main questions:

1. Where does a tool like this belong?

What is the philosophical dividing line between copilot-plugins (the official collection) and awesome-copilot? Does a tool like Slipstream / MCP for Flutter belong in the official collection, or is that reserved for general-purpose language tools?

2. How does the release cycle work if I'm listed?

If flutter-slipstream is included in either copilot-plugins or awesome-copilot, how are new versions handled? I know you can reference an external repository, but if I push a v1.1.0 bug fix to my own repo, do I have to wait for a PR review to ungate that release?

Any advice appreciated; thanks!