Routines can finish and restart cleanly
Protocol now treats routine completion and restart as first-class lifecycle moments instead of leaving them as ambiguous saved-routine state.
Shipped
- Added routine cycle completion handling for plans that reach the end of a run.
- Added cleaner restart behavior so a completed routine can start a new cycle without mutating the old training history.
- Improved the post-workout summary surface around routine progress and completion moments.
- Added share-moment groundwork for routine cycle completion without turning sharing into the core product.
- Hardened the lifecycle rules around restarting, scheduling, and preserving completed work.
Why
A routine does not only need a start button.
Real plans have endings. A block finishes. A cycle rolls over. A lifter repeats the plan with new numbers, pauses, changes course, or runs the next cycle with more context. If the app treats all of that as the same saved routine object, the history gets fuzzy fast.
This pass makes routine completion a more explicit product moment. Finishing a cycle should not quietly erase what happened. Restarting should not feel like duplicating a spreadsheet and hoping the old one stays intact. Protocol now has clearer boundaries between the completed run, the next run, and the workout history that progression depends on.
The important part is trust. When a plan ends, the app should show what happened and let the lifter move forward without corrupting the record that got them there.
Notes
- Restarting a routine is not the same as deleting history.
- Completion handling is tied to routine lifecycle, not a generic celebration screen.
- Share moments stay secondary to the training record.
Next
- Keep tightening the end-of-cycle decisions: repeat, adjust, retire, or move to a different plan.
- Make the next cycle feel deliberate without making the lifter rebuild the routine from scratch.