[project.scripts] is the PEP621 equivalent, supported by multiple backends including vanilla Setuptools. (When you use [tool.poetry.scripts], it's really the build backend, Masonry, that cares.) So that's the uv way, too. Or the "bear skins and stone knives" way.

I don't know what you mean by "without being a package". I guess you mean that Poetry will also run your code without installing it anywhere, and use the marked entry points directly. Per the other replies, apparently uv will get an equivalent soon. But really, the point of having `pyproject.toml` in the first place is to explain how to build an installable wheel and/or sdist for your project, and you basically get it for free. (Even if you don't include a [build-system] table, the standards say to use Setuptools by default anyway.)

(Of course, uv can already `run` your entry point, but this involves installing the code in a temporary venv.)

> without some pretty major refactoring of my internal structure and import declarations. Maybe I've accidentally cornered myself in a terrible and ill-advised structure?

Possibly. Is the code up on GitHub? I could take a look.