Create a Jira ticket for every open commitment from an active deal

<context>
I have open commitments from active deals that need to be tracked properly — not in my head or in a Slack message, but as real Jira tickets that are assigned, due-dated, and visible to the team. When I promise a prospect something, I want it in the system before I forget it.

My deals:
- Active deals with open commitments: [PASTE DEAL NAME, COMPANY, PRIMARY CONTACT — one per line]
- Jira project key: [e.g. SALES or CS or DEALS]
- Default assignee: [MY NAME OR "assign to me"]
- Timeframe to check: [e.g. "last 60 days of Gmail threads"]
</context>

<task>
1. Search Gmail for every active deal thread in the specified timeframe:
   - Every commitment made by the rep — "I'll send X", "I'll check on Y", "I'll introduce you to Z"
   - Every question asked by the prospect that wasn't fully answered
   - Every next step agreed on a call but not yet actioned
   - Date the commitment was made or implied

2. Use Lusha to validate the primary contact for each deal:
   - Still at the company in the same role?
   - Any title change since the commitment was made?

3. For each open commitment, create a Jira ticket:
   - Title: [Action] for [Company] — [Contact name]
   - Description: what was promised, when it was promised, the original email context (one sentence)
   - Assignee: as specified
   - Due date: 3 business days from today unless a specific date was mentioned in the thread
   - Label: deal-commitment
   - Priority: High if the commitment is more than 7 days overdue, Medium otherwise

4. Return:
   - List of Jira tickets created with ticket numbers
   - Any commitment where Lusha flagged a contact issue — flag before creating
   - Summary: X tickets created across X deals
</task>

<constraints>
- Only create tickets for genuinely open commitments — not things already delivered.
- If a commitment was mentioned and then fulfilled in a later email: skip it.
- Overdue commitments get High priority automatically — flag in the summary.
- One ticket per commitment — don't bundle multiple commitments into one ticket.
</constraints>

The situation: An AE runs this across 4 active deals, last 60 days of Gmail. Several commitments made, most not tracked anywhere.

Jira tickets created — project: SALES

5 tickets created across 3 deals

High priority flags (overdue):

⚠ SALES-204 — ZoomInfo comparison for Ashford promised on May 14 call — 21 days overdue ⚠ SALES-206 — DPA link for Ashford legal review — flagged by D.R. on May 27 — 8 days without action

Contact validation (Lusha):

All primary contacts confirmed at company in same role. No title changes detected. No contact flags.

Greenway Cloud — no tickets created: Gmail search found no open commitments for this deal. Last touch was 8 days ago — thread is active but clean. No action needed.

Illustrative example — fictional company names used. Run with your own deal data to see live results.