Luma Events Enhanced

# Luma Events Enhanced Skill

This skill allows the agent to fetch upcoming events from Luma (lu.ma) without authentication. It supports multiple cities, date filtering, and JSON output. Events are automatically persisted to `~/.openclaw/workspace/memory/luma-events.json` and old events are pruned (>24h past start) to keep storage manageable.

## Capabilities

- `fetch_events(city, days=30, max_events=20, json=False)` – Fetch events for a city (or list of cities). Returns human-readable text or JSON.
- `get_persisted_events()` – Read stored events from memory file (useful for follow-up questions).
- `prune_old_events(hours=24)` – Remove events that ended more than N hours ago.

## Usage

The agent typically runs the CLI:

```bash
python3 scripts/fetch_events.py <city> [cities...] [--days N] [--max N] [--json]
```

### Parameters

- **`city`**: City slug (lowercase, hyphenated), e.g., `bengaluru`, `mumbai`, `san-francisco`, `new-york`, `lisbon`, `porto`.
- **`--days N`**: Only include events occurring within the next N days (default: 30).
- **`--max N`**: Maximum number of events to return per city (default: 20).
- **`--json`**: Output raw JSON instead of formatted text.

### Output

Human-readable output prints each event with:
- 🎯 Event name
- 📍 Venue and city
- 📅 Date and time (local to event)
- 👥 Hosts (up to 2)
- 👤 Guest count
- 🎫 Ticket status (Free/Paid/Sold Out/Available with spots)
- 🔗 Direct lu.ma link

JSON output includes an array of event objects with fields:
- `city`, `name`, `start`, `end`, `url`, `venue`, `hosts[]`, `guestCount`, `ticketStatus` (`free`/`paid`/`sold_out`), `spotsRemaining`, `isFree`, `lastFetched`

### Persistence

After fetching, events are merged into `~/.openclaw/workspace/memory/luma-events.json` by event URL. On each run, the file is pruned to remove events older than 24 hours past their start time. This allows the agent to maintain context without re-fetching.

## Examples

### Find tech events this week
```bash
python3 sc...