feat: add deadline search on project sync/init

.agents/skills/project-init/SKILL.md

@@ -82,10 +82,40 @@ git log --format="%an|%ae" | sort | uniq -c | sort -rn
 ### Technical
 - architecture-term-1
 
+### Deadline & Timeline Tracking
+- deadline
+- due date
+- target date
+- ETA
+- "by when"
+- "ship by"
+- milestone
+- launch date
+- release date
+- "when will"
+- "when is"
+- pushed back
+- extended
+- slipped
+- delayed
+- ahead of schedule
+- behind schedule
+
 ## Entity Types Priority
 1. threaded_conversation (Zulip)
 2. meeting (recordings)
-3. [Exclude: calendar, email, document if not relevant]
+3. calendar_event (for deadline tracking)
+4. [Exclude: email, document if not relevant]
+
+## Deadline Discovery
+
+During initial data gathering, search for deadline-related discussions:
+- **Direct mentions**: "deadline", "due date", "target", "ETA", "launch date"
+- **Timeline discussions**: When delivery dates are discussed or negotiated
+- **Changes**: Deadline extensions, delays, accelerations
+- **Commitments**: Statements like "we'll ship by X", "targeting Y for release"
+
+Track these with dates, sources, and any context about rationale for changes.
 ```
 
 ## Step 3: Create Project Dashboard (Living Document)
@@ -159,6 +189,23 @@ This is the **entry point** — the living document showing current status.
 
 ---
 
+## Deadline History
+
+Track when deadlines were discussed, committed to, or changed. This shows the evolution of project timeline expectations.
+
+### Current Commitments
+| Deliverable | Current Target | Source | Confidence |
+|-------------|---------------|--------|------------|
+| [Feature/Milestone] | [Date] | [Meeting/Thread] | [High/Medium/Low] |
+
+### Timeline Evolution
+| Date | Change | Previous | New | Reason | Source |
+|------|--------|----------|-----|--------|--------|
+| [Date] | Extended | [Old Date] | [New Date] | [Why changed] | [Thread/Meeting] |
+| [Date] | Committed | - | [Date] | [Initial commitment context] | [Thread/Meeting] |
+
+---
+
 ## Recent Decisions
 
 ### Week [N] (Current)

.agents/skills/project-sync/SKILL.md

@@ -212,6 +212,7 @@ Pass only the sections for this specific week — do NOT pass the full files.
 2. **Technical Work** — Feature implementations, bug fixes, infrastructure changes  
 3. **Team Activity** — Core vs. occasional contributors, role changes
 4. **Blockers** — Issues, delays, dependencies
+5. **Deadline Discussions** — Target dates, commitments, timeline changes
 
 **Milestones:** When documenting milestones, capture BOTH:
 - **WHAT** — The technical achievement (e.g., "PostgreSQL migration")
@@ -219,6 +220,20 @@ Pass only the sections for this specific week — do NOT pass the full files.
 
 Search for business objectives in: meeting discussions about roadmap, Zulip threads about planning, PR descriptions, release notes, and any "why are we doing this" conversations.
 
+**Deadlines & Timeline Changes:** Search all data sources for:
+- **Explicit deadlines**: "deadline is", "due by", "target date", "ship by X", "launch date"
+- **ETAs and estimates**: "ETA", "expected by", "should be done"
+- **Changes**: "pushed back", "extended", "delayed", "moved up", "ahead of schedule", "slipped"
+- **Commitments**: Agreements on when something will be delivered
+- **Uncertainty**: "not sure when", "TBD", "need to figure out timeline"
+
+For each deadline discussion found, record:
+- What deliverable/milestone is being discussed
+- The date mentioned (if any)
+- Whether it's a new commitment, change, or removal
+- The source (which thread/meeting/commit)
+- Any context about why the timeline changed
+
 **Skip unless meaningful:** Routine check-ins, minor documentation updates, social chat.
 
 **Output:** Write `projects/$0/timeline/{year-month}/week-{n}.md` using the week file template from [project-history](../project-history/SKILL.md). Also return a **3-5 line summary** to the coordinator for use in Phase 3.
@@ -248,6 +263,31 @@ This is the **living document** — update it with current status from the week
 3. **Team** - Current contributors and their focus areas
 4. **Milestones** - Update status and add new ones with business objectives
 5. **Recent Decisions** - Key decisions from the last 2-3 weeks
+6. **Deadline History** - Track timeline discussions, commitments, and changes
+
+**Deadline Tracking:**
+- Scan all week summaries for deadline-related discussions
+- Add new entries to the "Timeline Evolution" table showing changes
+- Update "Current Commitments" with latest target dates
+- Note when deadlines are mentioned without specific dates (uncertainty)
+- Capture the reasoning behind timeline changes when available
+
+**Deadline History Format:**
+```markdown
+## Deadline History
+
+### Current Commitments
+| Deliverable | Current Target | Source | Confidence |
+|-------------|---------------|--------|------------|
+| Feature X | Mar 15, 2026 | Sprint planning meeting | High |
+| Beta release | Q2 2026 | Roadmap discussion | Medium |
+
+### Timeline Evolution
+| Date | Change | Previous | New | Reason | Source |
+|------|--------|----------|-----|--------|--------|
+| Feb 10 | Extended | Feb 28 | Mar 15 | Additional testing needed | #dev channel |
+| Jan 15 | Committed | - | Feb 28 | Initial sprint commitment | Sprint kickoff |
+```
 
 **Milestone Format:**
 ```markdown
@@ -319,6 +359,7 @@ Output a brief summary:
 1. Decision: {brief description}
 2. Feature: {what was built}
 3. Team: {who joined/left}
+4. Timeline: {deadline changes or commitments made}
 
 ### Metrics
 - {n} new commits