[WIP] Create philosophical timeline events dataset

[Copilot]

• Create content/timeline directory structure
• Research and compile 45+ philosophical timeline events (600 BCE - 2000 CE)
• Ensure coverage across all 7 traditions (Buddhism, Taoism, Stoicism, Cynicism, Sufism, Vedanta, Modern)
• Include all 5 event types with minimum counts (Birth: 10+, Death: 8+, Work: 12+, Teaching: 8+, Historical: 7+)
• Write 150-250 word descriptions for each event
• Add modern parallels for each event
• Populate all 11 required fields per event
• Use negative numbers for BCE dates, display format with "c." for approximate dates
• Ensure geographic diversity across events
• Add sources for historical accuracy
• Validate JSON structure
• Order events chronologically (earliest to latest)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Create Philosophical Timeline Dataset (45+ events)</issue_title>
<issue_description># Issue: Create Philosophical Timeline Events Dataset

User Story

As a content creator
I want a chronological timeline of key events in philosophical history
So that users can understand the historical context and evolution of wisdom traditions

Acceptance Criteria (BDD Scenarios)

Scenario 1: Timeline event structure includes all required fields

Given I am creating philosophical timeline events
When I structure each event
Then each event should include:
  | Field                    | Description                                  |
  |--------------------------|----------------------------------------------|
  | Year                     | BCE/CE year (negative for BCE)               |
  | Title                    | Concise event name (< 80 chars)              |
  | Description              | 150-250 word explanation                     |
  | Tradition                | Primary tradition(s) affected                |
  | EventType                | Birth, Death, Work, Teaching, Historical     |
  | Significance             | Why this event matters                       |
  | RelatedPhilosophers      | Array of philosopher names                   |
  | RelatedWorks             | Array of text titles                         |
  | GeographicLocation       | City/region                                  |
  | ModernParallel           | Contemporary equivalent or echo              |
  | ImageUrl                 | Relevant image if available                  |

Scenario 2: Coverage across all traditions and eras

Given I am creating a philosophical timeline
When I select events
Then the timeline should include events from:
  | Era                      | Date Range    | Min Events | Key Developments                    |
  |--------------------------|---------------|------------|-------------------------------------|
  | Ancient Foundations      | 600 BCE - 0   | 15         | Buddha, Laozi, Socrates, Stoics     |
  | Classical & Medieval     | 1 - 1400 CE   | 12         | Marcus, Plotinus, Shankara, Rumi    |
  | Renaissance & Reform     | 1400 - 1800   | 8          | Ramanuja, Madhva, Vallabha          |
  | Modern & Contemporary    | 1800 - 2000   | 10         | Vivekananda, Ramana, Krishnamurti   |
And total should be 45+ events
And events should span 2,600+ years (600 BCE to 2000 CE)

Scenario 3: Event type diversity

Given I am curating timeline events
When I categorize by type
Then the collection should include:
  | EventType                | Min Events | Examples                                  |
  |--------------------------|------------|-------------------------------------------|
  | Birth                    | 10         | Birth of Buddha, Marcus Aurelius          |
  | Death                    | 8          | Death of Seneca, Shankara's samadhi       |
  | Work Published/Created   | 12         | Meditations written, Upanishads composed  |
  | Teaching Event           | 8          | Buddha's first sermon, Epictetus's school |
  | Historical Milestone     | 7          | Alexander meets Diogenes, Mongol invasion |
And each event should clearly indicate its type

Scenario 4: Modern parallels and relevance

Given each timeline event
When I add modern context
Then each event should include:
  - Contemporary parallel or echo (similar modern event)
  - Why this historical event matters today
  - How it shaped current thought
And modern parallels should be creative and insightful
And language should bridge ancient and modern contexts

Scenario 5: Chronological accuracy and scholarly rigor

Given I am dating historical events
When I research each event
Then each event should:
  - Use BCE/CE notation (negative numbers for BCE in JSON)
  - Include "c." for approximate dates
  - Cite historical sources
  - Acknowledge date uncertainties where applicable
  - Provide geographic and political context
And dates should be verified against multiple scholarly sources

Data Format (JSON Schema)

{
  "timelineEvents": [
    {
      "id": 1,
      "year": -563,
      "yearDisplay": "c. 563 BCE",
      "title": "Birth of Siddhartha Gautama (Buddha)",
      "description": "Born as Prince Siddhartha in Lumbini (modern Nepal) into the Shakya clan, the future Buddha grew up in luxury, shielded from suffering by his father King Suddhodana. Prophecies predicted he would become either a great king or a spiritual teacher. His father, preferring the former, created an artificial paradise to prevent exposure to life's harsh realities. This sheltered upbringing would later make his encounters with aging, sickness, and death profoundly transformative, setting the sta...

</details>

- Fixes CoforgeInsurance/Kanban-XP-DevProcess#12

<!-- START COPILOT CODING AGENT TIPS -->
---

✨ Let Copilot coding agent [set things up for you](https://github.com/CoforgeInsurance/Kanban-XP-DevProcess/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

⏰ This PR has been inactive for 14 days

PRs should move quickly through the pipeline. This will close in 7 days.

For agent-generated PRs: Consider closing and reassigning issue to agent with improved specs.

For human PRs: Please update or request review to keep active.

[github-actions]

🔒 Closing stale PR

Closed due to 21 days of inactivity. Please reopen if still needed.