What we shipped.

How to read this log

This is the product-facing change log, not a raw engineering feed. It records changes a player can feel: faster logging, clearer bankroll numbers, better variance reads, private notes, export, sync and beta workflow. Tiny internal fixes stay out unless they change the public product.

The sequence also shows the product thesis: start with a clean session log, add bankroll and true-hourly context, then build the review loop around leaks, reads and study. If a future change does not support that loop, it should earn its place before it ships.

Each entry is written from the player view. A faster export, a clearer calculator, or a better empty state belongs here because it changes how someone logs or reviews. A refactor that only makes the code nicer does not. That separation keeps the log readable and gives beta users a clean record of what changed before they trust a real sample to the product.

If you are deciding whether the beta is moving in the right direction, read for pattern, not volume. The useful question is whether each release makes the log more complete, the true-hourly number more honest, the variance read clearer, or the study loop easier to keep after a long session.