fix: use sequential api key nonces

[ibruno]

Summary by cubic

Switches API key generation to sequential nonces derived from existing key metadata across Kuest services. Removes manual nonce input, prevents mismatches and duplicate signing, and makes key creation reliable across services.

• Bug Fixes

  • Compute the next nonce from fetched key metadata; ignore malformed or negative nonces.
  • If creation fails on all services, derive the existing key via /auth/derive-api-key to avoid duplicate errors.
  • Prevent duplicate signature requests during key creation with an in-flight guard.
  • Always allow key revocation; removed the “Different nonce” restriction.

• New Features

  • Added listKuestKeyMetadata and nextKuestNonceFromMetadata; listKuestKeys now returns only active keys.
  • Listing keys now requests metadata and revoked keys, merges metadata across services, and signs using the full path with query.
  • UI: removed the nonce input and added a “Generate another key” button after success.

^{Written for commit f5c0ac2. Summary will update on new commits. Review in cubic}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
auth	Ready	Preview, Comment	May 26, 2026 5:29pm

[cubic-dev-ai]

4 issues found across 3 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/features/keygen/key-generator.tsx">

<violation number="1" location="src/features/keygen/key-generator.tsx:410">
P3: Restore the correct ESLint rule name; otherwise the dependency warning is no longer suppressed.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P3: Restore the correct ESLint rule name; otherwise the dependency warning is no longer suppressed.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/features/keygen/key-generator.tsx, line 410:

<comment>Restore the correct ESLint rule name; otherwise the dependency warning is no longer suppressed.</comment>

<file context>
@@ -411,7 +407,7 @@ export function KeyGenerator() {
     // We intentionally react to connection/chain/signing state transitions.
     // Handler identities are recreated on render and are not used as effect triggers.
-    // eslint-disable-next-line react-hooks/exhaustive-deps
+    // eslint-disable-next-line react/exhaustive-deps
   }, [
     autoProceedAfterConnect,
</file context>

Suggested change

	// eslint-disable-next-line react/exhaustive-deps
	// eslint-disable-next-line react-hooks/exhaustive-deps

[ibruno]

@cubic-dev-ai

[cubic-dev-ai]

@cubic-dev-ai

@ibruno I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

1 issue found across 3 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/features/keygen/key-generator.tsx">

<violation number="1" location="src/features/keygen/key-generator.tsx:410">
P3: Restore the correct ESLint rule name; otherwise the dependency warning is no longer suppressed.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>