v4: a remote account's links to its home lead to the home's pages — the settings' "Change it on <host>" button and the profile's "Account on <host>" link went to the host in the handle, which is the home's issuer, its API, not necessarily where its pages are: in development musique's button led to localhost:8000/settings, gerbeur's API, which served a stale build, instead of localhost:3000/settings. GET /api/users/:key/home?path= now redirects to a page of a remote user's home, their profile there by default, at the origin of the home's authorization_endpoint, which its metadata gives (homePageUrl in federation-service.ts), the issuer standing in while the home doesn't answer; a local user 404s, and a path that isn't one 400s. homeUrl links to it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

API.md

@@ -130,6 +130,8 @@ there: those endpoints answer it 400.
 - `GET /api/users/:key/follow/users`, `/follow/playlists` — anyone. What they
   follow.
 - `GET /api/users/:key/invitees` — anyone. The tree of users they invited.
+- `GET /api/users/:key/home?path=` — anyone. Redirects to a page of a remote
+  user's home instance, their profile there by default.
 - `PATCH /api/users/:key/role`, `/username` — `user:manage`. Another user's
   role, or anyone's name, theirs included.