[Feature]: Notify on chat when new record is established

[rubasace]

What's your idea?

Users will get feedback when they submit a result that establishes a new record

Why is it useful?

It keeps users engaged

[daimonbot]

Implementation PR: #22

The PR adds a RecordNotificationService that detects when a submitted score is a new group record for a game and sends a notification to the chat. See the PR description for full details.

[daimonbot]

Status: Blocked — Requires Drone CI build logs

PR: #22
Current state: CI build failing after multiple fix attempts

Attempts made:

1. Fixed JPA/Hibernate Duration comparison (switched to Stream-based approach)
2. Added missing Stream import in test class
3. Mocked CustomTelegramClient in ApplicationTests
4. Replaced Stream with List to avoid transaction scope issues

Latest fix (2026-02-12 08:46 UTC):
Changed GameSessionRepository.findDistinctDurationsOrderedAsc from Stream<Duration> to List<Duration> to prevent LazyInitializationException when consuming outside active transaction.

Blocker: Cannot access Drone CI logs at https://drone.nasvigo.com/rubasace/ldrbot/240 to diagnose the current failure.

Next step: Need build failure details from Drone logs to identify root cause and apply fix. Without log access, cannot proceed further.

[daimonbot]

Status: PR #22 blocked by CI build failure.

Context:

• Implementation complete and code reviewed
• Multiple fix attempts made (JPA Duration comparison, Stream→List conversion, import fixes)
• CI build continues to fail at Drone CI

Blocker: Cannot access Drone CI logs to diagnose the failure. The agent environment doesn't have Java/Maven for local testing, and Drone CI logs require authentication.

Next step: Awaiting Drone CI build logs to identify and resolve the root cause.

See PR #22 for detailed history of fix attempts.

[daimonbot]

Status update (review):

PR #22 was closed without merge on Feb 15, despite CI checks passing (build #242 ✅).

The previous "blocked" status comments are no longer accurate — CI was resolved.

Awaiting direction: is a new implementation approach needed, or should this feature be deprioritized?