D-02: Support multiple vaccinators within a session setup

[roobottom]

Summary

Add an explicit choice for whether a session has more than one vaccinator, rather than assuming availability is always managed one vaccinator at a time.

Rationale

Round 1 research showed that larger vaccination sites may run a single session with multiple vaccinators, which better reflects their operational model than creating separate sessions per vaccinator.

Traceability

• Decision: D-02
• Source: docs/decisions/round-1.md
• Finding: Round 1, finding 2
• Related assumptions: A-05 availability is managed per vaccinator; A-15 one vaccinator per session matches mental model
• Labels: decision, research, round-1

Implementation checklist

• Add a Yes/No question that captures whether the session has more than one vaccinator
• Update the session setup flow to handle both single-vaccinator and multi-vaccinator cases
• Review any capacity, booking, or display logic affected by the new session model
• Update prototype content so the distinction between vaccinators and sessions is clear
• Identify what should be tested in the next round for larger-site workflows

Note

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