D-03: Introduce a dedicated add-breaks flow

[roobottom]

Summary

Replace the current expectation that users edit time blocks to create breaks with a more direct break-management flow.

Rationale

Round 1 research showed that users could create sessions with the time builder, but later struggled to edit an individual day or quickly block out time when booking over the phone.

Traceability

• Decision: D-03
• 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

• Design and add an explicit add-breaks flow that is triggered from an "Add break" link next to each empty slot in the daily bookings view
• Ensure the user flow follows the pattern: Add break > Enter start and end times (pre-filled with empty slot(s) times) > Affected bookings (if adding this break affects any bookings) > Check answers > Success (next action return to bookings) (Reuse screens from availability flow)
• Add a new "Change" and "Remove" controls next to breaks in the daily bookings view
• Ensure "change" and "remove" work following pattern above
• Update the relevant routes and templates so users can add breaks without reshaping time blocks manually
• Ensure the "Session times" page in the add/edit availability flow reflects any new breaks added
• Document what to validate in the next round of testing

Rough designs

Note

Live GitHub issue creation could not be completed because GitHub CLI is unavailable in the current environment.