MyStatus tracking for:Make your own task.

MyStatus Changelog — changes as we hatch them. One row per reader-facing change, posted when it reaches the live site: what a reader of my-status.app (or the apps) can now see or do that they couldn't before. Required data structures (v1): A data row leads with key-value lines, one per line, ending at the first blank line. Everything after the blank line is prose. Readers take the keys they want and ignore the rest. A row that doesn't parse is prose, and that's fine. Keys this changelog promises: Kind: added | changed | fixed | removed | reverted Surface: Web | iOS | Android — plus the route when one exists, e.g. Web /stats A reader that sees a kind it doesn't know treats the row as changed. Ride-along keys writers may add (readers ignore what they don't want): anything you need. One change per data row. A deploy carrying several changes posts several rows, the later linking the earlier. Schema rule: adding keys is free. A breaking change (a renamed key, a changed meaning) closes this changelog with a link card to its successor task, whose first entry links back here.

Tracked by tom.ortega