fix(docs): point repo card Stars link to repo home

[vinodmut]

Problem

The GitHub Pages repo card (linked from https://agenttoolkit.github.io/altk-evolve/) has a Stars stat that links to /stargazers. GitHub gates that page behind login — logged-out visitors get a 404, so the link is dead for anyone browsing the public site while signed out.

Fix

Point the Stars stat at the repo home page (data.html_url) instead. There is no anonymous stargazers view to link to.

Verified against the live repo while logged out:

Path	Status
/stargazers	404
/forks	200
/graphs/contributors	200
/issues	200

The other three stat links already work anonymously and are unchanged.

Summary by CodeRabbit

• Bug Fixes
  • Updated repository star links to open the repository’s main page, avoiding unavailable pages for signed-out visitors.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 613684ce-6c28-4978-8723-fa97977d5276

📥 Commits

Reviewing files that changed from the base of the PR and between f94af42 and 9dfd6a7.

📒 Files selected for processing (1)

• docs/components/github-repo-card.js

---

📝 Walkthrough

Walkthrough

The GitHub repository card’s Stars link now points to the repository homepage instead of the /stargazers endpoint, with a comment documenting the logged-out 404 behavior.

Changes

GitHub Repository Card

Layer / File(s)	Summary
Update Stars link target docs/components/github-repo-card.js	The Stars anchor now uses the repository home URL and documents why the /stargazers URL is avoided.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: redirecting the repo card Stars link to the repository home page.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[vinodmut]

@illeatmyhat now that this is merged to main, the change isn't showing up on https://agenttoolkit.github.io/altk-evolve/ yet. The site is served from the gh-pages branch, which appears to be updated manually (last build was April 10) — there's no GitHub Action that rebuilds/deploys the docs on merge. What's the process for deploying the docs site? Is it a manual mkdocs gh-deploy, or is there a step I'm missing?