v0.3.1

Fixes to installing either script. Nothing changes in what the functions send or return, apart from the version.

• Both scripts install into a schema whose name needs quoting, such as "ML Funcs" or "Analytics". They
  failed with invalid name syntax or schema "analytics" does not exist.
• Installing sql/drex_http.sql into a second schema no longer breaks an install in the http extension's schema
  (such as public). It dropped that install's _drex_settings(), so every call to it failed with
  function _drex_settings() does not exist.
• Requests identify themselves as drex-postgres/0.3.1 and drex-postgres-http/0.3.1 in X-Nace-Client.

Install: git clone --branch v0.3.1 https://github.com/nace-ai/drex-postgres.git, then follow the README. To upgrade from 0.3.0, check out v0.3.1, reinstall the package (PL/Python variant) and run the same script again.

v0.3.0

The first public release.

• Nine functions in two variants with the same names, arguments and results: drex_noul, drex_choice and
  drex_score (each for text and jsonb input), drex_decide, drex_decide_image and drex_decide_batch.
• sql/drex.sql, for self-hosted PostgreSQL: PL/Python on nace-sdk, with the
  key in the server's environment and drex_decide_batch sending up to concurrency requests at once.
• sql/drex_http.sql, for managed PostgreSQL that offers the http
  extension, such as Supabase: PL/pgSQL, with the key in a drex_settings table only its owner can read. It installs
  as a role that isn't a superuser, and a caller who can't read the key can't loosen how its requests check TLS.
• Both scripts revoke the functions from PUBLIC and from roles that default privileges grant new objects to, such
  as Supabase's anon and authenticated.
• Optional OpenRouter routing, with its own key and app attribution.
• Requests identify themselves as drex-postgres/0.3.0 and drex-postgres-http/0.3.0 in X-Nace-Client.

Install: git clone --branch v0.3.0 https://github.com/nace-ai/drex-postgres.git, then follow the README.