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
@@ -17,6 +17,7 @@ async function expectPushedOrder(page: Page, failFirstDetail = false) {
    conditions: [], alerts: [], scenarios: [], latest_analysis: null, work_orders: []
  };
  const task = {
+    execution_scope: "production",
    project_id: TEST_PROJECT_ID, task_id: taskId, task_type: "external_work_order",
    workflow: "external-work-order", lifecycle_status: "open", active_run: null,
    status: "queued", priority: "normal", revision: 2, execution_generation: 1,