Thank you for taking the time to provide feedback 
Talking about a ‘crawler’ is inaccurate terminology in the context of Murmurations.
I chose to use a general term instead of Murmurations-speak, but the equivalent in Murmurations is an Index.
In Federated Murmurations the centralized Index will not exist.
I have been thinking about federation for both ForgeFlux/Starchart and ForgeFlux/Northstar, which are both indexes. I’m trying to understand if federation will make sense in the context of indexing software. Both Starchart and Northstar will publish indexed items periodically, and both will have capabilities to follow and merge items from other instance(configured by instance admins). I’m not sure if federation would require additional features.
ForgeFlux is trying to implement federation externally, so most of the forges that we will deal with won’t have native capabilities
The UX that you are suggesting(POST request with CI) would require repository maintainers to configure and maintain integration, which could cause friction. It might make sense for more sophisticated projects because Starchart will only store and serve minimal information, that is already publicly available(repository link, owner, name, description and tags, if any)
Good idea, but there should be easier ways to do it. I’m torn between asking all interested devs to add another configuration file to their repositories and the simplicity of simply storing configuration files in the repository to makeup for a forge’s lack of features.
P.S apologies for the delayed response, this week was pretty hectic for me.