Update triage rules + TOOLS.md: use delivery upsert endpoint

TOOLS.md

@@ -70,7 +70,8 @@ Things like:
 **Deliveries API:**
 - `GET /api/deliveries` - list active deliveries (excludes delivered)
 - `GET /api/deliveries?all=true` - list all including delivered
-- `POST /api/deliveries` - add delivery
+- `POST /api/deliveries` - add delivery (prefer upsert instead)
+- `PUT /api/deliveries/upsert` - smart upsert: matches by tracking_number or description+retailer, updates existing or creates new. **Always use this for shipping email triage.**
 - `GET /api/deliveries/:id` - get single delivery
 - `PATCH /api/deliveries/:id` - update delivery
 - `DELETE /api/deliveries/:id` - remove delivery

memory/claude-usage.json

@@ -1,9 +1,9 @@
 {
-  "last_updated": "2026-02-13T21:19:34.051622Z",
+  "last_updated": "2026-02-13T22:00:02.638257Z",
   "source": "api",
   "session_percent": 2,
-  "session_resets": "2026-02-14T00:59:59.999919+00:00",
+  "session_resets": "2026-02-14T01:00:00.597034+00:00",
   "weekly_percent": 67,
-  "weekly_resets": "2026-02-14T18:59:59.999945+00:00",
+  "weekly_resets": "2026-02-14T18:59:59.597055+00:00",
   "sonnet_percent": 0
 }

memory/email-triage.md

@@ -176,7 +176,7 @@ Before moving to Trash:
 
 **Workflow for shipping/delivery emails:**
 1. Read the full message
-2. Update delivery tracking via dashboard API (`POST/PATCH http://localhost:9200/api/deliveries`)
+2. **ALWAYS use upsert** (never POST): `PUT http://localhost:9200/api/deliveries/upsert` — matches by tracking_number or description+retailer, updates if found, creates if not. Include tracking_number when available.
 3. THEN move to Trash
 
 This keeps the delivery schedule current without cluttering Shopping folder.