tmmot-resultslisted

# tmmot-results — the data + analysis layer **You give it one thing: the team you were following.** It fetches the rest — every played game, the group standings, and a full-tournament analysis — straight from the official results feed. No invented data; only games that were actually played. This is **Skill 1 of 2**. It produces the `data.json` data layer that **`tmmot-album`** (Skill 2) turns into a site + PDF memory book. ## Inputs - **Team name** (exactly as it appears on the feed, e.g. `KA-2`). - **Results URL** (the official feed, e.g. `https://urslit.tmmotid.is`). The day pages are scraped (`?day=A/B/C`), only rows with a final score count. - (optional) **Heart-rate window** — if the owner wore a Garmin and you have their HR in InfluxDB, `puls-magnus.py` adds a "how excited was the parent" series per game. ## What it writes into `data.json` - `matches[]` / `games[]` — the team's games (day, time, venue, opponent, score, result). - `groupResults[]` + `analysis.ka_family[]` — the group table + the team's siblings (e.g. all KA-1..KA-4) with per-game form. - `analysis` — tournament-wide stats (games played, goals, average, number of teams) and the team in context (goals for/against, defence percentile, etc.). - `wrapup.record` — the final W/L/GF/GA once the tournament is done. ## Tools - `tools/refresh-urslit.py` — scrape the official feed, write CSV + compute the analysis into `data.json`. **Idempotent:** exit `0` = unchanged, exit `3` = changed (so a cr