## 1. Backend delete confirmation

- [x] 1.1 Add a server delete request DTO and extend the service/API contract to accept the current session password on delete.
- [x] 1.2 Verify the current session password in the server deletion flow after owner/admin authorization and keep the existing deleted-state behavior.
- [x] 1.3 Update API handler docs and backend tests for owner/admin success, password failure, and unsafe-state rejection.

## 2. Frontend delete flow

- [x] 2.1 Update the server detail delete confirmation dialog to collect a password and submit it with the delete request.
- [x] 2.2 Rename the user-facing action copy from archive to delete where the destructive action is exposed.
- [x] 2.3 Update the API client, contracts, and frontend tests for the new delete payload and confirmation state.

## 3. Verification

- [x] 3.1 Run the structure check and focused backend/frontend tests for the delete flow.

## 4. Follow-up UI placement

- [x] 4.1 Move the delete confirmation entry from server detail metadata to the server list runtime action popover.
- [x] 4.2 Update frontend tests and verification for the new delete entry placement.