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
@@ -50,6 +50,7 @@ const operationalTaskRunPageSchema = z.object({
  next_cursor: z.string().min(1).nullable()
 }).strict();
 const taskSummarySchema = z.object({
+  execution_scope: z.string().min(1),
  handling_context: z.record(z.unknown()).optional(),
  project_id: z.string().uuid(),
  task_id: z.string().uuid(),