Add tracey export: Static HTML spec export

[killercup]

Probably fixes #143

Uses the daemon and most of the dashboard styles. There's a --sources
flag, then the sources will also be included. I don't really care for it
since I only want the spec exported as docs.

I had Claude fill in the all the HTML noise. Not sure you like this
style (I'm not too happy with it myself), but it does get the job done.
It also invented a symbols list for the source view -- I'm gonna let it
have that.

[killercup]

Ironically, I didn't write a spec for this :D

Let me know if this is the direction you want to take this, and I'll clean it up.

[fasterthanlime]

whoa, I've been thinking about making this, but you were faster!

please accept the title of "fastestthanlime"

[fasterthanlime]

So my concern here is that a lot of the assumptions are going to break over time, and the way I was thinking of doing it was to not really change the rendering itself, but to change the data source. The data source would be just static files, and then the API would be served from that. So there would be a different API provider. But I'll just merge this, so it doesn't rot, and we'll see if it breaks. Then, you know, I will have been right by virtue of being pessimistic.

[killercup]

Thanks! I'm sure this code is gonna come back to haunt both of us. Maybe I can fix it up before.

[killercup]

I thought about your data source swap as well but then it'd still be a SPA, when it could very well be entirely rendered. My a goal was to get something mdbook like, so I thought that fits better. I also thought of making it literally mdbook but it felt neater to reuse the existing tracey features.