Improve chart readability & fix hover state error

[aboydnw]

Three things in this PR:

1. I played around with fonts and node positioning and made some slight edits for improved readability
2. I addressed the hover error in Bug: Hover area after filtering #46
3. I added two new filters for stars and forks

All the new docs are for a future feature to provide NASA with more visibility into all the repos they are contributing towards.

[gadomski]

All the new docs are for a future feature to provide NASA with more visibility into all the repos they are contributing towards.

Nice! Do you anticipate needing a NASA-specific version of this viz? Or will we just be able to use the "main" version?

[gadomski]

I really like the new filters! The readability is much better as well, and can confirm the hover bug is fixed.

However, I'm 👎🏼 on at least some of the docs. E.g. DECISIONS.md implies that we desinged this app, when in reality its mostly derived from https://github.com/nbremer/ORCA/tree/main/top-contributor-network. What's the minimum you need for the NASA reporting?

[gadomski]

Two questions:

• What's the future value in keeping the plans in the repo?
• Is there another home for 🤖 docs, other than docs? docs feels like a home for user documentation, not robot documentation.

[aboydnw]

I suppose to both questions I don't have strong opinions, it just seemed an easy place to put them to refer agents to in the future. And I assume if it's been useful for me to point agents to those docs then it will be useful for anybody else who comes along and wants to fork the repo and have agents develop on it. But I'm not up to speed on the best practices here, so I'm happy to adjust.

[gadomski]

But I'm not up to speed on the best practices here, so I'm happy to adjust.

I think we're making them up as we go.

Let's put the claude-specific docs into .claude (including the plans). This mirrors IDE configuration, which goes into (e.g.) .vscode. I'd like to keep things vendor-specific, and not assume everyone uses Claude.

[aboydnw]

Sounds good to me! I've been looking up some updated best practices around AGENTS.md files and such to make it more tool agnostic. So we may want to update this in the future. But I think that's a good approach for now.