db/schema.md omits function bodies, so it cannot answer what is installed for any fn

CLAUDE.md and db/schema.md declare schema.md the canonical schema SSOT (PLUTO-63 retired src/db/schema.sql). It does not include pg_proc bodies. Measured 2026-08-17 during the fleet GUC audit (EVO-88 tail): grep for app.user_id / app.archive_reason in db/schema.md returns ZERO, while a prod pg_proc.prosrc read returns 24 matching functions, 23 of them reading both GUCs. Consequence: any agent asked to verify a function-level property from the repo either answers from db/migrations/ source - historical files that are not proof of what is applied - or reports a false negative off schema.md. Both failure modes look like a completed check. Fix: have db/export-db.py emit prosrc (or at minimum name + signature + a body hash) per function into schema.md, or state explicitly in schema.md that function bodies are out of scope and name the authoritative query. Silence is the defect - a reader cannot tell an absent section from an absent function. Related: PLUTO-701 (db:export reads an empty DATABASE_URL), which blocks re-running the export anyway.