[Bug] Responses API: compressed transcript not stored in ResponseStore, causing re-compression loop

When context compression fires during a /v1/responses conversation chained via previous_response_id, the compressed transcript isn't stored correctly in ResponseStore, so history keeps growing and re-triggers compression on every subsequent request.