The profile versions are maintained and selected in ebuild now. The major drawback is the discrepancy between CrOS release builders and simple chrome that people keep complaining about.

Moving AutoFDO profile version control from CrOS to Chromium means:
* Instead of updating chromeos-chrome-9999.ebuild, we update a version controlled file in Chromium repo.
* Instead of downloading profiles when doing emerge, we download profiles when checking out Chromium.

George already implemented it for Android. Some of the logics can be shared with CrOS. Major efforts would be:
* CrOS has 3 sources x 3 uarchs = 9 different flavors of profiles.
* In CrOS, profile versions are updated in master-chromium-pfq / samus-chrome-pre-flight-branch. If we update Chromium in them, the profiles may be slightly older compared to what we have right now.
* Testing

Pros:
* simple chrome will be consistent with ebuild based builds.
* CL:820568 will be solved as a side effect.

Not sure if it worth the efforts. WDYT?