v0.3.0 — Per-database schema support

Apps that keep tables outside public (a dedicated analytics schema, multi-tenant layouts, …) are now first-class citizens.

✨ New: per-database schema config option

[databases.events]
url = "${EVENTS_DATABASE_URL}"
schema = "analytics"

• All metadata tools target the configured schema — schema, describe, analyze, anomalies, trend, sample, erd, indexes, and foreign keys now parametrize the schema instead of hardcoding public (default remains public; existing configs are unaffected).
• Raw queries work unqualified — for non-public schemas the connection sets search_path=<schema>,public, so SELECT count(*) FROM events just works; public stays second so extensions (pgvector operators etc.) keep resolving.
• Clearer errors — "table not found" and empty-schema messages now name the schema they looked in.

🔒 Safety

• The schema name is validated at config load as a plain lowercase identifier (^[a-z_][a-z0-9_]*\Z) — it is the one identifier-shaped value embedded outside psycopg.sql.Identifier() (in the libpq search_path option), so it is held to a stricter shape than table/column identifiers. Lowercase-only because unquoted search_path case-folds: an uppercase schema would silently diverge from the case-preserving parametrized metadata queries. \Z anchor keeps a trailing newline out of the options string.
• All schema-scoped catalog queries use %s parameters — never string interpolation.

✅ Tests

• Test suite expanded 179 → 199: config validation (uppercase/trailing-newline/non-string rejection), per-tool schema scoping, anti-mutant "no hardcoded public" asserts, search_path option assembly.

Backward-compatible: without schema in the config nothing changes.

Install: pip install dbecho