Add Luma domain skill: internal admin API for events and guest lists

[zachary-ai]

Adds domain-skills/luma/admin-api.md covering the cookie-authed internal API at api.luma.com for calendar admins:

• Fetches must run from a luma.com page context (SameSite cookies) — includes the ensure-tab snippet
• calendar/admin/get-events: period=past|future only; upcoming 400s (field-tested trap)
• event/admin/get-guests: pagination, and the approval_status semantics — invited rows can outnumber real registrations 10:1, so unfiltered lists are wildly inflated
• checked_in_at caveat (registered ≠ attended for casual events), CSV-export fallback, official-API-needs-Luma-Plus note

All field-tested against a real host calendar this week. No user-specific IDs or secrets — placeholders only.

🤖 Generated with Claude Code

---

Summary by cubic

Adds a Luma domain skill documenting the internal cookie-authed admin API and a close_tab() helper. This enables reliable event and guest-list retrieval from a host session and helps agents clean up tabs after running.

• New Features
  • Added domain-skills/luma/admin-api.md covering https://api.luma.com for calendar admins. Includes an ensure-tab snippet since SameSite cookies require fetches to run from a luma.com tab.
  • Documented key endpoints and pitfalls:
    • GET /calendar/admin/get-events with period=past|future (note: upcoming 400s) and pagination via cursor.
    • GET /event/admin/get-guests with pagination, approval_status semantics (filter out invited to avoid 10x inflation), and checked_in_at caveat.
    • Notes on CSV export fallback and that the official API needs Luma Plus.
  • Added close_tab(target_id=None) in helpers.py to close a page via CDP Target.closeTarget and then ensure_real_tab() to keep the session stable.

^{Written for commit ced6422. Summary will update on new commits.}

[browser-harness-review]

✅ Skill review passed

Reviewed 1 file(s) — no findings.

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}