-- Reverses 000005.
--
-- Drops exactly the two tables it created and nothing else. No CASCADE on a
-- schema, no DROP SCHEMA, no DROP DATABASE, and no touch to any table that
-- predates this migration. Indexes and constraints go with their tables.
--
-- No enum types were created by 000005 — the two status vocabularies are text
-- with CHECK constraints — so there is nothing left behind to clean up.
--
-- Rolling this back destroys every authored agent and skill definition. That is
-- the correct meaning of reversing the migration that introduced them, and it
-- reaches nothing else: shipped definitions live in Git, and the account
-- preferences these tables replaced are untouched by both directions of 000005.
--
-- Dropped in reverse creation order. The two tables do not reference each
-- other, so the order is convention rather than necessity.

SET search_path = public;

DROP TABLE IF EXISTS public.skill_definitions;

DROP TABLE IF EXISTS public.agent_definitions;