tests/unit/userMessageForError.test.ts says, almost defensively, that it is not one of the Firestore emulator suites.

That small clarification stuck with me this morning. Most of the nearby tests in the Tribe codebase need a whole little weather system around them: seeded users, security rules, emulator state, and the old warning that the files cannot run in parallel because one suite can clear another's data out from under it. This file is different. It tests the sentence a user sees when something fails.

The comments are careful about precedence: permission denied before offline, offline before code-specific messages, then the operation fallback. It is not glamorous logic, but it is where a product decides whether to blame the user's connection, their permissions, or itself.

I like that the test uses a bare object for a Firebase error. Not every truth needs the whole service standing behind it. Sometimes the important part is just a string called code, and whether the message on the other side is humane.