Eliminate duplicate pendingHumanRequests system - use ChatManager only

- Removed pendingHumanRequests Map completely
- Added findPendingRequest() method to ChatManager for cross-session lookups
- Created minimal requestResolvers Map only for Promise resolve/reject functions
- Replaced all 9 calls to old system with ChatManager equivalents:
  * /response endpoint now uses ChatManager.findPendingRequest()
  * Timeout cleanup uses ChatManager.removePendingRequest()
  * Request storage uses ChatManager.addPendingRequest() only
  * respondToHumanRequest() and resolvePendingRequest() updated
- No more duplicate data storage - single source of truth in ChatManager
- All functionality preserved, cleaner architecture
This commit is contained in:
B Harper
2025-10-24 11:44:38 +11:00
parent dc1ee54ecd
commit 0fcc0a7b0e
6 changed files with 501 additions and 1473 deletions
+6
View File
@@ -6,3 +6,9 @@
2025-10-24T00:12:59.592Z - RESPONSE ENDPOINT CALLED - RequestID: 6-1761264773453
2025-10-24T00:13:11.610Z - RESPONSE ENDPOINT CALLED - RequestID: 7-1761264783500
2025-10-24T00:13:26.236Z - RESPONSE ENDPOINT CALLED - RequestID: 8-1761264795145
2025-10-24T00:27:30.026Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761265487845
2025-10-24T00:29:45.556Z - RESPONSE ENDPOINT CALLED - RequestID: 4-1761265750949
2025-10-24T00:30:12.657Z - RESPONSE ENDPOINT CALLED - RequestID: 5-1761265789274
2025-10-24T00:43:00.103Z - RESPONSE ENDPOINT CALLED - RequestID: 3-1761266557759
2025-10-24T00:43:44.783Z - RESPONSE ENDPOINT CALLED - RequestID: 4-1761266590985
2025-10-24T00:44:34.053Z - RESPONSE ENDPOINT CALLED - RequestID: 5-1761266631221