fix(tasks): accept execution scope in task responses

Server responses now require execution_scope, but the strict frontend schema rejected it and prevented investigation and appointment loading. Declare it in the shared response schema and align task fixtures; regression coverage exercises summaries, details and both task categories.
2026-11-08 03:44:25 +08:00
parent b948551c1f
commit aa9b12662e
10 changed files with 36 additions and 4 deletions
@@ -61,6 +61,7 @@ test("调查报告展示 SVG 脉络、处置进展和报告版本，缺数正常
    ]
  };
  let task: OperationalTask = {
+    execution_scope: "production",
    project_id: projectId, task_id: taskId, task_type: "event_investigation", workflow: "water_quality_complaint",
    lifecycle_status: "waiting_human", active_run: null, status: "waiting_human", priority: "urgent",
    revision: 2, execution_generation: 1, execution_request_id: "85000000-0000-4000-8000-000000000001",