API key rotation & lifecycle management

[therealjhay]

ProblemThe developers page creates keys but has no rotate/revoke/expiry UI; initialKeys are static and Math.random fallback leaks mock behavior.

Solution

• Add key actions: rotate (revoke + mint replacement, preserving usage history), revoke with confirmation, set expiry, and scope selection (read-only/read-write).
• Back with /api/keys/:id/rotate, :id/revoke, PATCH /api/keys/:id.
• Show masked keys with single-copy reveal (never render full key in DOM).
• Add an audit entry on every rotate/revoke.

Acceptance Criteria

• Rotating mints a new key and revokes the old immediately.
• Full keys never appear in the DOM text content.
• Scope changes are enforced server-side.
• npm run build passes.

Note for Contributors: Write a clear PR description. Show rotate → new key → old rejected.

[guptakumarranjeet150]

Hi everyone,

I would like to resolve this issue. Here is my proposed execution plan:

• Implementation: Build API key rotation & lifecycle management with clean React/Next.js components, responsive styling, and proper loading/error boundaries.
• Testing & Verification: Add component unit tests and ensure zero TypeScript/ESLint warnings.
• Delivery: Ready to ship a thoroughly tested PR within 12–24 hours with passing CI.

I am ready to start immediately—please assign this to me!