Add a click counter. Goal: count every successful redirect of a short link and expose the count at GET /links/{code}/stats. Every GET /{code} that returns 307 counts as one click; a 404 for an unknown code never counts. Each link keeps clicks (int, starts at 0) and last_clicked_at (UTC datetime, null until the first click). GET /links/{code}/stats returns 200 {"code", "url", "clicks", "last_clicked_at"} for a known code and 404 {"detail": "unknown code"} for an unknown one; fetching stats is not a click. GET /links and POST /links keep their current response shapes. Counts stay in memory like the links; no persistence, no per-day breakdown, no new dependencies. The README documents the new endpoint. Plan: one milestone, exactly two tickets: T1 record a click on every successful redirect (store and redirect handler, with tests); T2 add GET /links/{code}/stats with tests and the README line, after T1 is merged. The tares-factory crew builds it, one PR per ticket into main, merged after the reviewer passes it and CI is green; nothing to deploy. Tickets live in Tares only. Everything above is decided: ask only what is still open, then hand it to the crew.