D-03: add dedicated break flow

[roobottom]

What changed

Added a dedicated break-management flow from the daily bookings view.

Free slots now offer an Add break action, existing breaks now offer Change and Remove actions, and the session flow supports entering break times, reviewing affected bookings, checking answers, and confirming the change.

Why it changed

Round 1 research showed that users expected to manage breaks directly from the daily bookings context instead of inferring break changes through broader session edits. This makes break management explicit and keeps the journey focused on the specific task.

Traceability

• Assumptions: A-08, A-11, A-20
• Findings: Round 1 findings 3 and 4
• Decision: D-03 introduce a dedicated add-breaks flow
• Issue: D-03: Introduce a dedicated add-breaks flow #7

Validation

• Checked edited files for workspace errors
• Verified the branch had a clean working tree before pushing

Remaining uncertainty

This h

What changed

Added a dedicated break-management flow from the daiing uncertainty is whether the add, change, and remove paths feel consistent in the daily bookings screen.

What to test next

Test adding, changing, and removing a break from the day view, including cases where bookings are affected and need to be kept or cancelled.

Closes #7