zoe Shouldn't it be visible on github which patches got into the build?
In a sense. But it's not a simple sense, because Android is fundamentally not simple. The design is that OEMs build their releases by combining some code from Google (in multiple repositories) and some OEM code that is private (in different repositories). So there isn't one repository.
zoe I looked for a tag "2025012701" but could not find it. Which repo should I be looking at?
A lot of them. And which repositories to look at depends on the device, and which version of Android. Some of the code, e.g., firmware, isn't in any GitHub repo: the build process fetches system images from Google, extracts the firmware, and includes it in the system image being built.
Pretty much the only way to understand what's in a particular build of Android is to build it. Archaeology is of course possible, but the effort to develop that kind of skill would be just as useful building and debugging modern GrapheneOS on modern hardware, which would be useful to a lot more people, and can be fairly secure. And some of the modern devices even don't burst into flames very often!