fix: migrate management keys to private REST API

[erikchi]

Symptom

Registration still failing after #6:

{"reason":"management_key_create_failed",
 "error_detail":"could not get create action hash, available: map[]"}

#6 migrated account state; the provisioning-key lifecycle was still on the server actions OpenRouter removed. This is the remaining half.

Endpoints

Derived from the authenticated bundle — module 677420, hooks useCreateManagementApiKey / useDeleteWorkspaceApiKey:

op	call
list	GET /api/frontend/v1/private/management-keys?page=N
create	POST /api/frontend/v1/private/workspace-api-keys/management
delete	PATCH /api/frontend/v1/private/workspace-api-keys/{hash}

Delete body:

{"payload":{"deleted":true},"opts":{"is_provisioning_key":true}}

That opts flag is required and must be snake_case — the endpoint answers 403 for opts:{} and for opts:{"isProvisioningKey":true}. It corresponds to the third argument the old server action passed ({"isProvisioningKey":true}), which is how it was found.

Listing now paginates — a correctness fix beyond the migration

The legacy path scraped the settings page and only ever saw the first 20 keys. CleanupProvisioningKeys deletes keys whose name matches a station label, so on a busy account it was silently leaving keys alive and under-reporting the count. The test account holds 164 management keys; the old path could see roughly 20 of them.

Verification

End-to-end against a live account through the exported Go API (not curl), with action hashes: map[] throughout — proving none of it touches the removed actions:

listed 164 keys              ← pagination working
created key sk-or-v1-...
probe key found by label, total now 165
cleanup deleted 1 key(s)
final count back to 164      ← test asserts no drift

The probe key is created under a dedicated label and removed via CleanupProvisioningKeys, so the live test leaves the account exactly as it found it — and it exercises the label-matching cleanup path rather than just the raw delete.

Unit tests cover the list envelope, total_count, hashless entries (which would give cleanup an undeletable target), error/HTML bodies, and the empty page that terminates pagination.

All three exported functions try REST first and keep the legacy server-action path as a fallback, consistent with FetchActivityData in #6.

🤖 Generated with Claude Code