David decided: prompt changes must hit prod, seed, and fallback

Kerra uses AI agents whose behavior depends on prompts stored in different places: production database prompts, seed prompts used to repopulate them, and fallback prompt files in the repo.

a prompt fix can appear to work once and then disappear after a deploy or reseed if only one source is changed. David explicitly pushed against that kind of prompt drift.

ensure it updates both the fallback prompt, the seed one and the actual one

this is how David thinks about AI product ops: prompts are not vibes. they are production configuration with regression paths.