App reports "Exit Allowed" and sends notifications for denied transits during curfew

[simonstephens]

When a curfew policy denies a cat exit, the app still labels the event "Exit Allowed" and sends a push notification as if the cat went outside. At 2am during a curfew, I get a notification telling me my cat is out — when the flap was locked and the cat never left. This is misleading and defeats the purpose of having a curfew.

Steps to reproduce

1. Create a curfew policy that denies exit during certain hours (e.g. 20:00-07:00)
2. Cat approaches the flap from inside during the denied window
3. Flap correctly locks — cat is denied exit
4. App shows the event as "Exit Allowed" in the event feed
5. Push notification arrives as if the cat went outside

Expected behaviour

• Event should be labelled "Exit Denied" (or similar)
• Push notification should either not fire for denied transits, or clearly indicate the exit was blocked

Impact

This makes the event feed and notifications unreliable for anyone using curfew policies. You can't trust the app to tell you where your cat actually is overnight. The whole point of a curfew is peace of mind that the cat is inside — but the app actively undermines that by reporting the opposite.

Root cause (from API investigation)

The getEvent and getDeviceEvents API responses contain no field distinguishing a denied transit from a successful one. The event objects are identical — same eventClassification, same fields. The onlycat-shared-models TypeScript repo defines an EventSummary model with transit outcomes (TRANSIT, DENY, PEEK, BREACH), but this data isn't present in the Socket.IO API responses. The app appears to be labelling events without knowing the actual outcome.

This likely also explains onlycat-home-assistant#44, where presence detection is wrong for cats that aren't allowed out — the Home Assistant integration has the same problem because the API doesn't expose the transit outcome.