feat(console): pick a persona from a list, or mint one on the spot

[stormer78]

Step three asked a first-time holder to type a DID they did not have. In agent-memory, which publishes none, the field was an empty box with a placeholder and a pointer to another pane — so the guided setup ended there.

The list leads; free text is an option inside it

#165 deliberately made this a datalist over a text field: a persona DID need not be one of the context's published did:webvh identifiers — a v4 holder is a did:key the VTA mints, peers are reached at did:peer — and a <select> would refuse all of those.

That reasoning still holds, and the control was still wrong. It made the unusual case the default question and left the common one unanswered. Now:

• the dropdown carries the context's published identifiers and the personas already known there, each reading as its own last path segment with what it wears beside it;
• "— another DID, typed —" is the last option, revealing the free-text field with a way back to the list.

The unusual identifiers stay reachable. They stop being what the form asks first.

A context with none can make one

This is the part that unblocks the flow. serverId is what a create needs — omitting it means serverless, where the caller serves the log itself at a url, which is not what this flow wants — so the picker asks the agent which hosting servers it can publish through and uses the one when there is one. The new DID lands selected and the suggestion list reloads around it.

Three states, each said plainly:

a server is registered	Create one here, naming the server it publishes through
still asking	Checking where your agent can publish…
none registered	the one case that genuinely belongs in the DIDs pane, said as such rather than failing

The created DID is not portable — it lives where it is published — and the button says so beside itself. That decides once and for all whether the DID may ever move, and a guided flow should not make an irreversible choice quietly; the DIDs pane is where to choose otherwise.

Changing an existing binding

Shows the persona as text rather than a picker. The field was already disabled there, and a disabled <select> reads as a control that failed to load.

Verification

npm run lint, npm run build, npm test — 849 across four workspaces. All six ci.yml assertions against the real build. The now-dead DID_SUGGESTIONS datalist id is removed.

Not exercised: no renderer here, so the create path is reasoned from vta/webvh/dids/create/1.0's contract rather than watched. Worth running step three in a context with no DIDs, which is the case it was built for.