/api/oskiewar-stats answers in one round trip what three collections already knew: rounds and matches from oskiewar-replays, engagement from oskiewar-pops, reel performance from the marketing ledger. Days are drawn in the wall's timezone by Mongo rather than by subtracting hours, so a daylight-saving day is still one day long. Pops only ever kept two days of rows, so a total was unrecoverable. Each pop now also increments a per-day counter that the TTL sweep never touches. It has to start now because a swept day cannot be counted again, and the endpoint reports `since` so the wall never passes it off as all-time. pullInsights had never run. Meta rejects the whole request if any single metric is unsupported -- `reposts` is refused on Instagram Login despite being documented -- so it now reads the rejected names out of the error and retries without them instead of carrying a hard-coded list that rots. Reel figures are marketing data, and lith serves every function publicly, so that block travels only to a caller holding OSKIEWAR_WALL_KEY and is withheld entirely when no key is configured. The wall itself is two Chrome windows, one per monitor: Mutter clamps a single window to one output's work area, which is the same reason the fleet cockpit is two xterms.