KLooks like today is docs day for me, so tracking stuff I need to put in user documentation here:
- How default includes are resolved
- Default Clang parameters (lang version and such)
- Configuration parameters for ClangScraper
Pi think on the user docs until we have that magical
silktouch command you can just invoke again i wouldn't worryPjust keep notes of things to include
KYeah I wasn't too sure how I'd do things here, but I also need to somehow track things
KIdk I can probably write these things down already
Poh one other thing btw
Pi still have no idea how TypeId works from the documentation
Pe.g. i have no idea where the GUID comes from, what meaning it has, etc
Pi get it's something to do with resolution, but how a TypeId links to a real type is still a mystery to me
KI tried explaining that in type store.md 
will look at that again
will look at that againPthanks. i think it's more the where it comes from that i'm struggling most with, but yeah worth making very obvious words how it links back to a real type.