fix: use role-specific cursor keys in review_ready and arbiter_requested paths
The review_ready and arbiter_requested paths in processGroupMessages were advancing the default (owner) cursor instead of the role-specific cursor. This caused the reviewer to miss the owner's messages because the owner cursor had already moved past them. Now review_ready advances chatJid:reviewer cursor only, and arbiter_requested advances chatJid:arbiter cursor only.
This commit is contained in:
@@ -631,7 +631,7 @@ describe('createMessageRuntime', () => {
|
||||
|
||||
expect(result).toBe(true);
|
||||
expect(agentRunner.runAgentProcess).toHaveBeenCalledTimes(1);
|
||||
expect(lastAgentTimestamps[chatJid]).toBe('41');
|
||||
expect(lastAgentTimestamps[`${chatJid}:reviewer`]).toBe('41');
|
||||
expect(saveState).toHaveBeenCalled();
|
||||
expect(channel.sendMessage).toHaveBeenCalledWith(chatJid, '리뷰 확인 완료');
|
||||
});
|
||||
|
||||
Reference in New Issue
Block a user