fix: reset gateBlockCount on deliverableType change

Root cause: gateBlockCount was only reset when assignee or status
changed, but NOT when deliverableType changed. When agents patched
deliverableType to fix missing verification gates (e.g. setting
deliverable_type_required), the gateBlockCount kept incrementing
without reset — causing agents to be skipped on subsequent wakeups.

Fix:
- Add deliverableType to updateIssueSchema so it can be patched via API
- Add gateBlockCount reset when deliverableType changes (mirrors existing
  resets for assignee and status changes)

DLD-3465

Author: Senior Platform Engineer

packages/shared/src/validators/issue.ts

@@ -74,6 +74,7 @@ export const updateIssueSchema = createIssueSchema.partial().extend({
   reopenEvidence: z.string().min(1).optional(),
   interrupt: z.boolean().optional(),
   hiddenAt: z.string().datetime().nullable().optional(),
+  deliverableType: z.string().optional().nullable(),
 });
 
 export type UpdateIssue = z.infer<typeof updateIssueSchema>;

server/src/routes/issues.ts

@@ -2819,6 +2819,13 @@ export function issueRoutes(
       (updateFields as Record<string, unknown>).gateBlockCount = 0;
     }
 
+    // Reset gate-block counter when deliverableType changes — the issue may now satisfy
+    // previously-blocked gates (e.g. deliverable_type_required or verification_target_required).
+    const existingDeliverableType = (existing as unknown as { deliverableType: string | null }).deliverableType ?? null;
+    if (req.body.deliverableType !== undefined && req.body.deliverableType !== existingDeliverableType) {
+      (updateFields as Record<string, unknown>).gateBlockCount = 0;
+    }
+
     let issue;
     try {
       issue = await svc.update(id, updateFields);