D-05: complete single-session changes within each edit subflow

[roobottom]

What changed

Removed the final save step from the change session overview and completed each single-session edit within its own subflow.

Session edits now move from the selected edit path to an affected bookings warning when needed, then to a dedicated check answers page and success page. The check answers page now uses a standard summary-list structure, shows the booking action when bookings are affected, and uses a destructive confirmation button when the user chooses to cancel affected bookings.

Why it changed

Round 1 research showed that some users stopped early because they thought their change had already been applied when they returned to the overview screen. Completing each edit within its own journey makes the end of the task expli

What changed

Removed the final save step from the change session overview and completed each single-session edit within its own subflow.

Session edits now move from the selected edit path to an affected bookings warning when neassumption was recorded for this behaviour

Validation

• Checked workspace errors for the edited route and templates
• Confirmed the branch diff includes the D-05 subflow save implementation and the corrected flow order

Remaining uncertainty

This has not been exercised through a full browser journey in this session, so the remaining uncertainty is whether the warning, check answers, and success transitions feel fully clear in use for all edit paths.

What to test next

Test that users changing session times, booking length, and services all understand that their change is only applied after the end-of-subflow confirmation page.

Closes #9