Which of your abandoned repos is closest to finished

Build which of your abandoned repos is closest to finished.

Context: Point it at your GitHub. It reads every repo you stopped touching and ranks
them by how close they actually are to shippable — not by how much code is in
them.

Commit history shows where you gave up. Open TODOs and empty test files show
what you knew was missing. A repo with 4,000 lines and no auth is further from
done than one with 400 lines and a working payment flow.

The output is one sentence: this one is about three evenings from launchable,
and here is what's missing.

The hard part is that "close to done" isn't visible in code alone. A project
can be ninety percent built and zero percent shippable because there's no way
to log in, or because the founder lost interest, which no linter detects. It
probably has to ask two or three questions per repo rather than pretend to
know.

Everyone reading this has a graveyard. Most of those projects are much closer
than the person who abandoned them believes.

Requirements:
- Ship the smallest version that delivers the core value above, nothing more.
- Pick a stack you can deploy in a day, and state the choice before writing code.
- Handle the empty state, the error state and the offline case explicitly.
- Pricing to build toward: Free for public repos — that's the hook and it costs almost nothing to run.
$9/mo for private ones, which is where the real graveyards are.

Start by listing the screens, then build them one at a time.