Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

This PR addresses an issue where chat conversation history could not be decrypted in the chat/ai/list endpoint. The root cause was an inconsistency between the encryption method used when storing chat interactions (chat/ai/data) and the decryption method used when retrieving them (chat/ai/list).

This change standardizes the encryption process to use the direct GcmAes256 utility, ensuring compatibility between encryption and decryption, and resolving the data retrieval failures.

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

Closes #9561

How did you test it?

The list endpoint is working fine with new encryption logic:

curl --location 'http://localhost:8080/chat/ai/list?merchant_id=merchant_1758788495' \
--header 'Authorization: Bearer JWT' \

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible