iachat/db
Rodribm10 95d3e99652 feat(retention): version the Jasmine + Daniela prompts as seed files
The orchestrator prompt (Jasmine) and scenario instruction (Daniela)
live in the database. When we merge this branch to main and deploy to
production, the prod DB will keep its OLD prompts — the new ones would
only exist in staging. That defeats the point of merging.

Fix: commit the current staging prompts as .md files under
db/seed_prompts/ and add a data migration that syncs them into the DB
on deploy. Idempotent (no-ops when content already matches).

From now on, prompt changes follow the same workflow as code: edit the
.md file, migration resyncs on deploy. The DB row becomes a mirror of
the file, not the source of truth.
2026-04-22 11:00:06 -03:00
..
migrate feat(retention): version the Jasmine + Daniela prompts as seed files 2026-04-22 11:00:06 -03:00
seed_prompts feat(retention): version the Jasmine + Daniela prompts as seed files 2026-04-22 11:00:06 -03:00
seeds chore(lifecycle): add demo seed script for manual pipeline testing 2026-04-15 09:31:11 -03:00
schema.rb feat(retention): version the Jasmine + Daniela prompts as seed files 2026-04-22 11:00:06 -03:00
seeds.rb chore: Enable the new Rubocop rules (#7122) 2023-05-19 14:37:10 +05:30