Miscellaneous Fixes (#21208)

* conditionally display actions for admin role only

* only allow admins to save annotation offset

* Fix classification reset filter

* fix explore context menu from blocking pointer events on the body element after dialog close

applying modal=false to the menu (not to the dialog) to fix this in the same way as elsewhere in the codebase

* add select all link to face library, classification, and explore

* Disable iOS image dragging for classification card

* add proxmox ballooning comment

* lpr docs tweaks

* yaml list

* clarify tls_insecure

* Improve security summary format and usefulness

---------

Co-authored-by: Nicolas Mowen <nickmowen213@gmail.com>

frigate/genai/__init__.py

@@ -177,78 +177,60 @@ Each line represents a detection state, not necessarily unique individuals. Pare
         self,
         start_ts: float,
         end_ts: float,
-        segments: list[dict[str, Any]],
+        events: list[dict[str, Any]],
         debug_save: bool,
     ) -> str | None:
         """Generate a summary of review item descriptions over a period of time."""
         time_range = f"{datetime.datetime.fromtimestamp(start_ts).strftime('%B %d, %Y at %I:%M %p')} to {datetime.datetime.fromtimestamp(end_ts).strftime('%B %d, %Y at %I:%M %p')}"
         timeline_summary_prompt = f"""
-You are a security officer.
-Time range: {time_range}.
-Input: JSON list with "title", "scene", "confidence", "potential_threat_level" (0-2), "other_concerns", "_is_primary", "_camera".
+You are a security officer writing a concise security report.
 
-Task: Write a concise, human-presentable security report in markdown format.
+Time range: {time_range}
 
-CRITICAL - Understanding Primary vs Contextual Items:
-- Items with "_is_primary": true are events that REQUIRE REVIEW and MUST be included in the report
-- Items with "_is_primary": false are additional context from other camera perspectives that overlap in time
-- **DO NOT create separate bullet points or sections for contextual items**
-- **ONLY use contextual items to enrich and inform the description of primary items**
-- The "_camera" field indicates which camera captured each event
-- **When a contextual item provides relevant background, you MUST incorporate it directly into the primary event's bullet point**
-- Contextual information often explains or de-escalates seemingly suspicious primary events
+Input format: Each event is a JSON object with:
+- "title", "scene", "confidence", "potential_threat_level" (0-2), "other_concerns", "camera", "time", "start_time", "end_time"
+- "context": array of related events from other cameras that occurred during overlapping time periods
 
-Rules for the report:
+Report Structure - Use this EXACT format:
 
-- Title & overview
-  - Start with:
-    # Security Summary - {time_range}
-  - Write a 1-2 sentence situational overview capturing the general pattern of the period.
-  - Keep the overview high-level; specific details will be in the event bullets below.
+# Security Summary - {time_range}
 
-- Event details
-  - **ONLY create bullet points for PRIMARY items (_is_primary: true)**
-  - **Do NOT create sections or bullets for events that don't exist**
-  - Do NOT create separate bullets for contextual items
-  - Present primary events in chronological order as a bullet list.
-  - **CRITICAL: When contextual items overlap with a primary event, you MUST weave that information directly into the same bullet point**
-  - Format: **[Timestamp]** - [Description incorporating any contextual information]. [Camera info]. (threat level: X)
-  - If contextual information provides an explanation (e.g., delivery truck → person is likely delivery driver), reflect this understanding in your description and potentially adjust the perceived threat level
-  - If multiple PRIMARY events occur within the same minute, combine them into a single bullet with sub-points.
-  - Use bold timestamps for clarity.
-  - Camera format: "Camera: [camera name]" or mention contextual cameras inline when relevant
-  - Group bullets under subheadings ONLY when you have actual PRIMARY events to list (e.g., Porch Activity, Unusual Behavior).
+## Overview
+[Write 1-2 sentences summarizing the overall activity pattern during this period.]
 
-- Threat levels
-  - Show the threat level for PRIMARY events using these labels:
-    - Threat level 0: "Normal"
-    - Threat level 1: "Needs review"
-    - Threat level 2: "Security concern"
-  - Format as (threat level: Normal), (threat level: Needs review), or (threat level: Security concern).
-  - **When contextual items clearly explain a primary event (e.g., delivery truck explains person at door), you should describe it as normal activity and note the explanation**
-  - **Your description and tone should reflect the fuller understanding provided by contextual information**
-  - Example: Primary event says "unidentified person with face covering" but context shows delivery truck → describe as "delivery person (truck visible on Front Driveway Cam)" rather than emphasizing suspicious elements
-  - The stored threat level remains as originally classified, but your narrative should reflect the contextual understanding
-  - If multiple PRIMARY events at the same time share the same threat level, only state it once.
+---
 
-- Final assessment
-  - End with a Final Assessment section.
-  - If all primary events are threat level 0 or explained by contextual items:
-    Final assessment: Only normal residential activity observed during this period.
-  - If threat level 1 events are present:
-    Final assessment: Some activity requires review but no security concerns identified.
-  - If threat level 2 events are present, clearly summarize them as Security concerns requiring immediate attention.
-  - Keep this section brief - do not repeat details from the event descriptions above.
+## Timeline
 
-- Conciseness
-  - Do not repeat benign clothing/appearance details unless they distinguish individuals.
-  - Summarize similar routine events instead of restating full scene descriptions.
-  - When incorporating contextual information, do so briefly and naturally within the primary event description.
-  - Avoid lengthy explanatory notes - integrate context seamlessly into the narrative.
+[Group events by time periods (e.g., "Morning (6:00 AM - 12:00 PM)", "Afternoon (12:00 PM - 5:00 PM)", "Evening (5:00 PM - 9:00 PM)", "Night (9:00 PM - 6:00 AM)"). Use appropriate time blocks based on when events occurred.]
+
+### [Time Block Name]
+
+**HH:MM AM/PM** | [Camera Name] | [Threat Level Indicator]
+- [Event title]: [Clear description incorporating contextual information from the "context" array]
+- Context: [If context array has items, mention them here, e.g., "Delivery truck present on Front Driveway Cam (HH:MM AM/PM)"]
+- Assessment: [Brief assessment incorporating context - if context explains the event, note it here]
+
+[Repeat for each event in chronological order within the time block]
+
+---
+
+## Summary
+[One sentence summarizing the period. If all events are normal/explained: "Routine activity observed." If review needed: "Some activity requires review but no security concerns." If security concerns: "Security concerns requiring immediate attention."]
+
+Guidelines:
+- List ALL events in chronological order, grouped by time blocks
+- Threat level indicators: ✓ Normal, ⚠️ Needs review, 🔴 Security concern
+- Integrate contextual information naturally - use the "context" array to enrich each event's description
+- If context explains the event (e.g., delivery truck explains person at door), describe it accordingly (e.g., "delivery person" not "unidentified person")
+- Be concise but informative - focus on what happened and what it means
+- If contextual information makes an event clearly normal, reflect that in your assessment
+- Only create time blocks that have events - don't create empty sections
 """
 
-        for item in segments:
-            timeline_summary_prompt += f"\n{item}"
+        timeline_summary_prompt += "\n\nEvents:\n"
+        for event in events:
+            timeline_summary_prompt += f"\n{event}\n"
 
         if debug_save:
             with open(