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
@@ -1267,6 +1267,7 @@ test.describe("外围系统", () => {
      if (request.method() === "POST" && url.pathname.endsWith("/operational-tasks")) {
        const input = request.postDataJSON() as Record<string, unknown>;
        operationalTask = {
+          execution_scope: "production",
          project_id: projectId, task_id: "70000000-0000-4000-8000-000000000001",
          task_type: "event_investigation", workflow: "water_quality_complaint",
          lifecycle_status: "waiting_human", active_run: null,