fix: in-flight request payload sync

[rdself]

Summary

Fixes stale payloads in active in-flight request details by keeping the pending detail queue and the ID lookup map synchronized when request metadata is updated.

Root cause

trackPendingRequest() stores the same pending request detail in both the per-connection queue and pendingById. updatePendingRequest() later replaced the queue entry with a new object, leaving pendingById pointing at the original registration-time snapshot. The active log detail endpoint reads pendingById, so in-flight details could show an outdated provider request while completed logs showed the final sanitized provider payload.

Impact

Active request details now reflect updates such as provider payload normalization before the request completes. The original client request remains unchanged, while the provider request view can update from the initial payload to the final provider-bound payload.

Validation

• node --import tsx --import ./open-sse/utils/setupPolyfill.ts --test tests/unit/request-logger-endpoints.test.ts
• node --import tsx --import ./open-sse/utils/setupPolyfill.ts --test tests/unit/active-request-stream-chunks-lifecycle.test.ts

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[diegosouzapw]

Obrigado, @rdself! 🙏 Boa pegada na causa-raiz: o updatePendingRequest() recriava o objeto e deixava o pendingById apontando pro snapshot de registro, então o detalhe in-flight mostrava o payload antigo. O Object.assign in-place mantém as duas views na mesma referência, e o teste que assere a identidade (getPendingById().get(id) === queueDetail) é exatamente a regressão certa. Integra limpo com o #3937 (funções distintas no mesmo arquivo). Validei junto: typecheck:core limpo, 42/42 testes, eslint 0 erros. Entra no próximo release. 🚀