The build process for Core currently makes use of the tool.build.poetry.script option as a hook to compile our C dependencies during the build process. As the name suggests, this option is specific to Poetry (or more specifically, Poetry's build backend). Thus, switching from Poetry to uv would require us to do one of the following:

• Use an equivalent option for uv -- it seems likely that Hatch's build hooks would work for us with minimal fuss, but we'll have to try it. uv is writing a build backend of their own, but it's still in alpha right now, and presumably Hatch will remain a well-supported option even after it is done.
• Figure out how to continue using Poetry's build backend with uv. This should be possible, but again requires some investigation.
• Rework our build process to compile the C libraries outside of the Python build process. This option isn't ideal because it would allow uv build to package stale versions of the C libraries/fail to package correctly at all on a fresh environment without running some extra steps beforehand.