feat(trace): isolate chat runs

openspec/changes/session-run-trace-isolation/specs/session-run-trace-isolation/spec.md

@@ -61,6 +61,7 @@ The system SHALL allow callers to query a diagnosis trace by `sessionId` alone f
 - **WHEN** a caller requests `GET /api/diagnosis/{sessionId}/trace?runId=run-xxx`
 - **THEN** the system SHALL validate that `runId` belongs to the path `sessionId`
 - **AND** it SHALL return only the session summary, run summary, agent steps, tool invocations, self-evaluation, answer, and feedback for that run
+- **AND** the session summary SHALL come from `chat_session` metadata when available, while the run summary SHALL come from `diagnosis_run`
 
 #### Scenario: Trace rejects run from another session
 - **WHEN** a caller requests a `runId` that belongs to a different `sessionId`
@@ -101,6 +102,7 @@ The system SHALL create and expose a diagnosis run for every valid `/api/ai_ops`
 - **WHEN** `/api/ai_ops` starts a valid execution
 - **THEN** the system SHALL create a `diagnosis_run` with `agent_flow=AI_OPS`
 - **AND** AIOps agent steps, tool invocations, and rule evaluation SHALL be associated with that `run_id`
+- **AND** AIOps rule evaluation SHALL be stored under `diagnosis_run.self_evaluation.aiops_rule_evaluation` for the current run
 
 #### Scenario: AIOps SSE exposes runId
 - **WHEN** `/api/ai_ops` streams response metadata to the caller