-- @database: main
--
-- Drops `topic_translation`: topic wording now lives in the locale catalogues
-- `resources/lang/<locale>/topics.php`, keyed by slug
-- (`topics.<slug>.{label,description}`) and resolved at serialisation time by
-- TopicResourceSerializer.
--
-- Same move already made for badges (`badge_translation` was dropped in favour
-- of `badges.php`): translating a curated, slug-keyed catalogue is versioned
-- content — reviewed in a PR, deployed with the code — not a runtime
-- back-office operation. The read path loses two LEFT JOINs, and the lang file
-- is served from OPcache.
--
-- SAFE: the table was empty (0 rows) — it had been created by the topic design
-- but never seeded, so nothing is lost. Leaving it in place would have
-- recreated the very problem just cured with focus/topic: a dormant table that
-- looks authoritative.
--
-- A topic with no entry in the lang files still renders: the serializer falls
-- back to the raw slug (and the Translator logs `i18n.missingKey`), so a topic
-- created from the future back-office stays usable until its wording ships.

DROP TABLE IF EXISTS `topic_translation`;
