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
@@ -11,6 +11,7 @@ export function investigationFixture(index: number, title: string): OperationalT
  const runId = `93000000-0000-4000-8000-${String(index).padStart(12, "0")}`;
  const requestId = `94000000-0000-4000-8000-${String(index).padStart(12, "0")}`;
  return {
+    execution_scope: "production",
    project_id: projectId, task_id: taskId, task_type: "event_investigation", workflow: "burst_report",
    lifecycle_status: "open", status: "running", priority: "normal", revision: 1, execution_generation: 1,
    execution_request_id: requestId, title, summary: "仅供浏览器测试的合成调查",