Adding a check against Chromium code to ensure features are shipping could solve some data accuracy issues #5517
Description
Features are enabled in either runtime_enabled_features.json5 or content_features.cc. It may be possible to reference these files in Chromium to check that the current milestone data is accurate and features are indeed shipping in a specific milestone. This may allow us to only consider a feature as shipped if it exists in these files, or to ask feature owners to confirm their shipping milestone if the feature's name is not detected in these files.
I would imagine corner cases exist here, and more exploration on that would be useful. For example, it could be possible that a feature is enabled, but finch is overriding it.