USR369 reported several instances of data appearing missing or lost in the Android app (stretching after quit/reopen, stretching again after Load-into-Current, full workout detail, and Info/Swimming/Recovery sections in History). In every case, direct comparison against the live gym.db backend showed the data was fully intact and correct -- these are UI/display or Load-into-Current transfer bugs, not real data loss. Filed each as a bug with the backend-verified state included, so whoever fixes it knows to look at rendering/transfer logic, not data persistence.