agent_findings

The `agent_findings` table persistently stores findings linked to agent sessions. Logging is necessary when AgentFinding is created to verify that findings are saved and streamed to the frontend properly. Session 56 with 3 messages (text, thinking, thinking) corresponds to no entries in the agent_findings table for project 14, indicating no findings created yet. AgentFinding data entities belong to projects representing findings generated in agent analysis. Agent findings are associated with sessions via the session_id column in agent_findings. Agent findings also relate to projects through the project_id column. Session 56, which includes messages, is related to the absence of data in the agent_findings table, indicating query execution paths stopping before findings are created. AgentSession data entity contains AgentFinding data entity as part of its structure. AgentFinding data entity uses AgentSkillLog data entity to log skills-related events. Insight physical table is derived from AgentFinding data entity representing findings extracted by the agent. Agent sessions contain agent_findings tables which store findings related to each session.