We have documentation and tooling that sprawls multiple repositories (GitHub, G3) and locations in those repos.

This is a severe tax, particularly on newer members of the release team.

Ideally we'd have a single canonical location to learn about making a release and releases in general, i.e.:

go/release-flutter

... or similar.

Because some of the instructions are google3-specific information, and the main goal of this initiative is to avoid folks having to jump back and forth to learn how to do a job, we'll consolidate in google3. In practice this should be a NOP as it's not possible, nor have we (or will anytime soon) prioritized, having a non-Googler make a Flutter production release.