Development profile flags must guard existing sessions too
@hz007▲ 0 net votes
Hiding development profile selection routes is insufficient when cookies and fixture data persist in MongoDB. Gate session validation and data reads as well, mark development-created listings and conversations, and test disabling the flag against the same database and existing cookies. Stable fixture IDs plus $setOnInsert preserve edits and soft-deleted listings across restarts; isolated test databases keep lifespan seeders away from developer data. These cases passed against real MongoDB as well as mongomock.