ADORSYS-GIS / ADORSYS-GIS/lightbridge-governance
[Story]: Cursor Admin/Analytics API connector
- Lingua principale
- Rust
- Stelle
- 1
- Fork
- 2
- Merge medio
- 14h 36m
- PR unite (30g)
- 107
Descrizione
## Summary
Build a connector against Cursor's Admin/Analytics API for per-user, per-day suggestions shown vs accepted, lines added/deleted, and active status, with CSV export. This is gated on the customer holding a Cursor Enterprise plan — the Admin API is not available on lower tiers.
## Intent / Source of truth
Cursor's documented Admin/Analytics API (Enterprise tier). 2026-08-13 backlog consolidation.
## Scope
- [ ] Scheduled connector pulling per-user, per-day suggestions shown/accepted, lines added/deleted, active status
- [ ] CSV export support (matching Cursor's native export shape where useful)
- [ ] Map into the schema from story 1
- [ ] Gate the connector's activation on confirming the customer holds Cursor Enterprise (fail gracefully with a clear message otherwise, not a silent empty dashboard)
## Out of scope
- Any Cursor tier below Enterprise (no Admin API access exists)
- Cursor's own in-editor analytics UI — this connector only covers the Admin API pull
## Verification
Live pull against a real Cursor Enterprise org showing per-user daily records; a clear, tested failure path when run against a non-Enterprise account.
## Risk assessment
Low technical risk (documented API); commercial risk is customers without Enterprise expecting this to work — the gating message must be unambiguous.
## AI Usage Declaration
Drafted with AI assistance during the 2026-08-13 cross-repo backlog consolidation. A human owns intent, verification and consequences; acceptance criteria must be verified against the live system before this is closed.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by locating the schema from story 1 and the connector entry points in this repository, then review Cursor's documented Enterprise Admin/Analytics API. Confirm the per-user daily fields, CSV shape, and Enterprise availability before implementation. Done means a verified live pull for an Enterprise organization and a clear tested failure path for non-Enterprise accounts.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- rust
- Ambito
- analytics, api
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Tranquilla
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 35/100