The issue is /akkoma is an API route prefix, so the frontend plug skips over the request. Ironcially the thing which makes /akkoma an API prefix is the frontend picker browser UI added in de64c6c while the preferred frontend override apparently (though no idea how) makes it accessible anyway?
*oma allows profiles to be fetched on /<username>, so adding something directly on the root will 100% cause conflicts there. Imo that’s a behaviour that should’ve never gotten in, but that’s another discussion (which also kinda relates to #279 - Add /@<username> route - AkkomaGang/akkoma - Akkoma Development ).