feat: delete OpenProject tickets when creation criteria is no longer satisfied (#1)

feat: delete OpenProject tickets when owner becomes unmapped

When a Zammad ticket's owner changes to someone who is not in the
ASSIGNEES mapping, the corresponding OpenProject work package is now
deleted. This maintains consistency with the creation rule that
prevents creating tickets for unmapped owners.

The deletion logic:
- Checks if an existing task has an unmapped owner
- Deletes the OpenProject work package via DELETE API call
- Returns early to prevent the update logic from running
- Logs the deletion with owner ID for debugging

This ensures that tickets only exist in OpenProject when they meet
the same criteria required for creation (owner must be mapped).

Co-authored-by: Claude <[email protected]>

Author: insertish

main.ts

@@ -111,6 +111,28 @@ if (import.meta.main) {
 
       // (2) create or update
       if (existingTask) {
+        // Delete task if owner is no longer mapped
+        if (!ASSIGNEES[ticket.owner_id]) {
+          console.info(
+            `Deleting task ${existingTask.id} - owner ${ticket.owner_id} is not mapped.`
+          );
+
+          await fetch(
+            `${OP_URL}/api/v3/work_packages/${existingTask.id}`,
+            {
+              method: "DELETE",
+              headers: {
+                Authorization: "Basic " + btoa("apikey:" + OP_TOKEN),
+              },
+            }
+          ).then((r) => {
+            if (!r.ok) throw new Error(`Delete failed with status ${r.status}`);
+          });
+
+          console.info("Deleted task successfully.");
+          return new Response(null, { status: 200 });
+        }
+
         // update existing task
         await fetch(
           `${OP_URL}/api/v3/work_packages/${existingTask.id}?notify=false`,