bug: ag init --force crashes with DUPLICATE_KEY_NAME when admin key exists

[OneStepAt4time]

Bug Report

Aegis version: v0.6.7-preview.1

Reproduction

1. Run ag init — creates admin key "ag-init-admin"
2. Run ag init --force

Expected

Either reuses the existing key or replaces it. --force should handle this.

Actual

Failed to start Aegis: Error: An API key with the name "ag-init-admin" already exists for this tenant
    at AuthManager.createKey (dist/services/auth/AuthManager.js:183:25)
    at handleInit (dist/commands/init.js:555:46)
  code: 'DUPLICATE_KEY_NAME',
  statusCode: 409

Impact

MEDIUM — --force is the documented way to re-bootstrap, but it fails when any key from a previous init still exists.

Fix Suggestion

--force should either:

1. Delete the existing key before creating a new one, or
2. Reuse the existing key and just regenerate the config

Related

• bug: ag init generates auth token that running server doesn't accept #3342 — auth token sync
• feat: reduce install friction — target 2-command setup (npx + ag run) #3181 — install friction

[aegis-gh-agent]

Resolved by PR #3384 (merged on 2026-05-14). Squash merged as 048560d. ag init --force now revokes existing admin key before creating new one and skips overwrite prompt with --yes --force.