Check if this issue is valid — if so, understand the root cause and fix it. At apps/meteor/client/views/room/contextualBar/Info/EditRoomInfo/EditRoomInfo.tsx, line 174:

<comment>Disabling “Hide System Messages” can stop working because `systemMessages` is now sent as `undefined` instead of an explicit clearing value.</comment>

<file context>
@@ -171,7 +171,7 @@ const EditRoomInfo = ({ room, onClickClose, onClickBack }: EditRoomInfoProps) =>
 					...((data.joinCode || 'joinCodeRequired' in data) && { joinCode: joinCodeRequired ? data.joinCode : '' }),
 					...((data.systemMessages || !hideSysMes) && {
-						systemMessages: hideSysMes && data.systemMessages,
+						systemMessages: data.systemMessages,
 					}),
 					retentionEnabled,
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At apps/meteor/app/api/server/v1/rooms.ts, line 755:

<comment>`$ref: '#/components/schemas/IRoomAdmin'` references a schema that is never registered with this `ajv` instance via `addSchema()`. This will cause `ajv.compile()` to throw at module load time, or fail validation in test environments. Use an inline object schema instead (similar to the other endpoints in this file).</comment>

<file context>
@@ -653,334 +671,466 @@ API.v1.get(
+		response: {
+			200: ajv.compile<Pick<IRoom, RoomAdminFieldsType>>({
+				allOf: [
+					{ $ref: '#/components/schemas/IRoomAdmin' },
+					{ type: 'object', properties: { success: { type: 'boolean', enum: [true] } }, required: ['success'] },
+				],
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At apps/meteor/app/api/server/v1/im.ts, line 814:

<comment>`if (!msgs)` is unreachable because `toArray()` always returns an array. This dead branch means the "No messages found" error path never runs.</comment>

<file context>
@@ -743,6 +743,162 @@ const dmCreateResponseSchema = ajv.compile<{ room: IRoom & { rid: string } }>({
+
+		const [msgs, total] = await Promise.all([cursor.toArray(), totalCount]);
+
+		if (!msgs) {
+			throw new Meteor.Error('error-no-messages', 'No messages found');
+		}
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At apps/meteor/app/api/server/v1/rooms.ts, line 1220:

<comment>Typo: `projections` should be `projection` (singular). MongoDB silently ignores the unrecognized option, so the full user document is fetched instead of just `_id`.</comment>

<file context>
@@ -1049,31 +1199,37 @@ API.v1.post(
+		}
 
-			const user = await Users.findOneById(this.userId, { projections: { _id: 1 } });
+		const user = await Users.findOneById(this.userId, { projections: { _id: 1 } });
 
-			if (!user) {
</file context>