Apply guided scheduling interface patterns

README.md

@@ -132,6 +132,24 @@ poll-backed scheduling requests:
 - a first Scheduling WebUI package with request creation, slot matrix, Calendar
   actions, decisions, and notification-job creation
 
+## Interface workflow and contextual guidance
+
+The request detail projects the existing backend lifecycle into three stable
+user stages: prepare the request, collect participation, and decide. Draft,
+collecting, closed, decided, handed-off, cancelled, and archived records remain
+the authoritative backend states; the stage rail is only a readable projection
+and does not invent a second workflow state machine. Cancelled requests keep the
+reached stage visible as stopped, while later stages remain locked.
+
+Unavailable Calendar coordination and public guest participation use Core's
+action-blocker pattern. The UI names the reason, required remediation,
+responsible administrator, and destination instead of displaying a generic
+disabled control. Stable help links resolve to the configured Docs module when
+present and to the hosted documentation otherwise. Scheduling contributes the
+`scheduling.find-and-decide-meeting-time`, `scheduling.calendar-coordination`,
+and `scheduling.participation-governance` topics; it does not import Docs,
+Calendar, Poll, Policy, or Access implementation code.
+
 The next slices should add generic self-enrolment links after their abuse and
 identity policy is agreed, Calendar hold cleanup after decision, and advanced
 scoring constraints such as required participants and quorum rules.