As a prelude to TRT-2121 (if we end up going the route of a separate instance), make the initial step of showing an HCM release in our regular Sippy Classic (not CR yet). It will not have payloads or feature gates.

TRT-2130 produced initial spike notes. We discussed further action in our July 9 team sync and determined the path of adding more attributes in the BQ Releases table (and corresponding golang types) so that we can be explicit about where we are treating releases differently and cease special-casing 3.11, Presubmits, or anything else that comes along.

We need to add this release, get it synced, exclude it everywhere we don't want to see it, and let David know it's there to look at.

Note that we believe at least ci-tools makes use of this table; as much as possible, try to avoid causing disruption to other teams/tools with updates to this table. Consult our release branch/GA notes for hints about dependencies.

Stephen B indicated the first release should be named aro-integration.