A lockless uv project with a Poetry plugin table loses its UV_PROJECT_ENVIRONMENT packages: "is this Poetry" is read three ways #1916

[agent] Filed by the scheduled architecture audit (audit-core). Register: A47.

Kind: bug. Register ID: A47.

Problem

Three rules decide whether a pyproject.toml declares [tool.poetry], and they disagree:

• python_crawler::declares_tool_poetry parses the TOML and says a plugin table such as [tool.poetry-dynamic-versioning] alone does not make a project Poetry's (python_crawler.rs L2280-L2289).``
• python_crawler::claimed_by_non_uv_manager uses text.contains("[tool.poetry"), which matches the plugin table, and also matches a comment (L1049-L1065).```
• utils::toml_edit_ext::has_table is a third table probe (L25-L42).````

claimed_by_non_uv_manager gates the lockless-uv branch at L1038,````` so a uv project without uv.lock that uses `poetry-dynamic-versioning` (a common plugin used with non-Poetry backends too) is treated as Poetry's, and its `UV_PROJECT_ENVIRONMENT` env is never crawled.

Executed on main @ cbbbdb9 (probe binary calling find_local_venv_site_packages, UV_PROJECT_ENVIRONMENT=env, env/lib/python3.12/site-packages present, no uv.lock):

• [tool.poetry-dynamic-versioning] → the env/…/site-packages path is missing;
• [tool.other-plugin] → it is returned.

With a uv.lock both return it, so the drift only bites lockless projects.

Proposed change

claimed_by_non_uv_manager calls declares_tool_poetry (or one shared pyproject_declares_tool(text, "poetry") helper beside toml_edit_ext::has_table) instead of the substring test. Delete the substring copy.

Size

1 file, ~10 lines plus one unit test.

Acceptance criteria

• A unit test: lockless pyproject with only [tool.poetry-dynamic-versioning] and UV_PROJECT_ENVIRONMENT set yields the env's site-packages; [tool.poetry] still does not.
• Existing python crawler tests and tests/crawler_python_e2e.rs pass unchanged.