reason Field Contains a Hardcoded Duration (22s) That Mismatches timestamp_ms Arithmetic

[soumyaranjan77-web]

@Devnil434 Where: reason = "Repeated keypad interaction over 22s ..." and timestamp_ms = 1718000022000.0

What's wrong:

• 1718000022000 ms = Unix epoch 22.000 seconds past 1718000000000. This makes it look intentional — but if Phase 5 alert endpoints compute duration dynamically from timestamp_ms - event_start_ms and compare it against the text in reason for audit logging or NLP assertion tests, the 22s in the string becomes a magic number coupled to the timestamp. If any test changes timestamp_ms for a different scenario (e.g. testing midnight boundary), the reason string silently lies. The fixture creates an invisible coupling between two independent fields.

Fix:

• Decouple the duration from the timestamp

• reason = "Repeated keypad interaction over extended period suggests unauthorised entry attempt."

• Duration should be derived at runtime, not hardcoded into a fixture string

[Arjita-2B-18]

Hello @soumyaranjan77-web,
I am a GSSOC 2026 participant and would like to work on this issue.
I have understood the problem and would like to contribute a fix.
Kindly assign this issue to me. Thank you!