preloaders/metadata

Would love to make the metadata functionality more elegant, using the fact that generating metadata should follow a pre-defined algorithm in all clients (e.g. instanceID is always 'uuid:'+uuid()).

~~Is metadata currently always (or almost always) placed inside a `` block as direct child of the root node?~~

No file, test, or entry point is named in the issue. Start by locating the specification's existing metadata and preloader definitions, then compare how metadata is generated across clients; done means an agreed algorithm and placement are documented.

Written by the indexing model from the issue text.