LLM plugin ecosystem exposed by HTTP client migration

The real problem wasn't the httpx2 migration itself, but that it exposed a widespread pattern: plugins built on LLM were never actually declaring their dependencies, just inheriting them invisibly. This suggests the plugin contract around LLM has been underspecified from the start.

This connects directly to the reliability crisis documented across recent LLM deployment studies. Just as the medical device assessment paper found that every commercial LLM deployment produced inconsistent outputs, and the entity extraction work showed confidence signals remain broken even in flagship models, this dependency incident reveals a parallel fragility in the tooling layer. When infrastructure assumptions go undeclared, brittleness compounds. The difference is that plugin developers can fix this through explicit dependency declaration, whereas the measurement and calibration failures in those studies require architectural rethinking. Willison's patch is a tactical fix; the real issue is that LLM's plugin ecosystem grew without enforcing the kind of contract clarity that production systems require.

Monitor whether Simon Willison or the Datasette maintainers publish a plugin development guide that mandates explicit dependency declaration in the next 30 days. If that lands before the next LLM minor release, it signals the ecosystem is treating this as a structural lesson. If it doesn't, expect similar breakage when the next transitive dependency shifts.