Feature Request: Client-side "Live Status" check for stale issues #95
Description
I've noticed that due to the sync interval, many issues listed are actually already closed on GitHub.
I checked the workflow and noticed the site only rebuilds every 8 hours. Since 'Good First Issues' are often claimed within minutes, this gap causes many stale links.
Instead of increasing the backend sync frequency (which costs resources), I propose adding a client-side status check.
A client-side live check would bridge this 8-hour gap without increasing costs.
The Proposed Solution: Instead of increasing the backend build frequency (which uses resources), I propose adding a lightweight Client-Side Live Check.
Logic: When the user loads the page, we trigger a client-side fetch() to the GitHub API for the visible repository/issue.
UI: If the API returns state: closed, we visually gray out the card or add a small "Closed" badge next to the title.
Benefit: This ensures users see real-time status immediately without requiring any changes to the backend architecture or database.
I would love to work on implementing this! Let me know if you're open to this approach.