Dealing with missing discovery infrastructure

The default version of CSS is missing a number of things which SolidOS counts on - a settings folder, preference file, typeIndexes, an inbox container , a public container. In Data-Kitchen I pre-provision all of those so a Data-Kitchen CSS does include them all. If we believe that these things are a best practice for pod providers, we should say so publicly so that those intending to offer CSS pods will at least know that these things are missing and hopefully provision new pods with them. If these are not a server best practice and/or we want to handle servers who don't implement them, how should we handle it?

We could have mashlib itself create the settings, inbox, and public folders, and put pointers to them in the profile. If we don't do that it seems like the minimum we can do is a) when preferences are missing, treat the person as in the developer role when logged in - otherwise there is no way to delete any resources (see https://github.com/solid/solidos/issues/47 and https://github.com/solid/solidos/issues/48) and b) have the "got to user X's files" link on the pod root home pane go to the profile instead because it should exist even if there is no /public/ folder.