Routine setup is more deliberate

Shipped

• Updated routine setup so weekly, rotating, and periodized routines ask for the right setup decisions.
• Weekly routines can focus the Builder canvas on the selected training weekdays.
• Rotating routines keep active weekday selection while generating the workout sequence.
• Periodized routines no longer require a global weekday picker before the block is built.
• Improved Builder validation so missing runnable work is easier to understand in one pass.
• Fixed the Add Exercise modal so the selection step keeps Cancel and Next visible.
• Added a Plan-owned Import routine entry that opens Builder review before the imported file can be saved to Library.

Why

Routine building is plan design work. It should not ask the same questions for every kind of plan.

A weekly split, a rotating A/B/C routine, and a periodized block are not the same object in practice. That shows up in the first few minutes of setup: choosing Monday, Wednesday, and Friday for a weekly plan is different from writing a sequence of Workout A, B, and C, and both are different from building a block that can change from week to week. The Builder now respects more of that difference before the user starts filling in exercises.

Import follows the same idea. Plan can be the entry point for acquiring a routine, but Builder should be the place where the imported structure is reviewed, corrected, and saved deliberately.

Notes

• Imported routine files do not become Library routines until the user saves them from Builder.
• Activation remains a separate Plan action after a routine is saved.
• The Builder changes are about setup clarity, not hidden automation.

Next

• Keep making routine creation feel like programming a real plan, rather than filling out a generic workout form.
• Improve the places where creation, activation, and execution hand off to each other.