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
@@ -62,6 +62,7 @@ describe("execution step cards", () => {
 });

 const taskBase = {
+  execution_scope: "production",
  project_id: "11111111-1111-4111-8111-111111111111",
  task_id: "22222222-2222-4222-8222-222222222222",
  task_type: "event_investigation",