commented:
I only get a blank page. The DOM is there but I can't see anything.
Using a font for charts is not good for accessibility.
But was it the reason I only got a blank page? Nope: turns out there's
an "opacity: 0;" CSS rule on body.
There's also that opacity rule on other elements.
It turns out I had to disable ublock origin to get because the fonts
file were blocked and then some javascript removed these opacity rules
I guess.
But well, I also have browser rules to force using my font choice (I
hate serifs).
I'm quite parted about all this. Using a font for charts is definitely
the wrong tool. OTOH, the charts values are provided so it's maybe not
that bad (although seeing just the values is rarely expected). There
are some nice things but it's not really usable in practice: there are
too many actual and current issues.

  commented:
"vibecoding" tag disclosure: I was going to write a long comment with
all my findings (if the first paragraph or the article wasn't telling
enough) but guess I don't need to do that at all (I'll probably end up
making a SlopHub account again just so I can use Code Search).

  commented:
I hadn't thought of leaking tool info through .gitignore. I guess this
is one more benefit to just doing blanket ignore for anything starting
with _ or . and then manually exempting specifics.
My standard .gitignore-file starting point for reference:
_*
..*
_*/
..*/
!.gitignore


  commented:
This looks amazing and I like it a lot, but... I think the
accessibility issues are too much
.