D-07: Reuse the add-break flow on the session times screen

[roobottom]

Summary

Reuse the dedicated add-break flow from D-03 on the Session times screen in both the add availability and edit availability journeys.

Rationale

Round 1 findings 3 and 4 showed that users understood the session time builder for initial setup, but struggled when they needed to introduce or adjust breaks quickly. D-03 addressed that need in the daily bookings view. The same direct interaction should be available during availability setup and editing so users do not have to learn one model for creating sessions and another for managing breaks.

Traceability

• Decision: D-07
• Source: docs/decisions/round-1.md
• Findings: Round 1, findings 3 and 4
• Related assumptions: A-08 time blocks are understood as availability; A-11 implicit breaks are understood; A-20 splitting time blocks to create breaks is discoverable
• Labels: decision, research, round-1

Implementation checklist

• Add an "Add break" trigger on the Session times screen in the add availability journey
• Add an "Add break" trigger on the Session times screen in the edit availability journey
• Reuse the D-03 break form pattern so adding a break returns the user to the Session times screen
• Support changing and removing existing breaks from the Session times screen so break management is consistent within the journey
• Keep the Session times page state and check answers summary in sync after breaks are added, changed, or removed
• Document what to validate in the next round of testing

[roobottom]

Not sure we need this. Implemented in https://github.com/NHSDigital/mya-provocotype/tree/d-07-reuse-break-flow but interaction between auto and manual break is weird. Needs further user insights.