Add poll workflow and signed participation support

README.md

@@ -43,9 +43,25 @@ storage, validation, result aggregation, tenant summaries, module migrations,
 and authenticated API routes for:
 
 - single-choice, multiple-choice, yes/no, ranked-choice, and availability polls
+- yes/no/maybe polls for tentative decisions
 - opening, closing, and deciding polls
 - submitting and updating respondent answers
 - listing responses and reading result summaries
+- signed participation links for reduced/no-Access participation
+- context and workflow metadata for modules such as Scheduling
+
+## Scheduling As A Poll-Backed Workflow
+
+Scheduling should use Poll as the reusable response collection primitive, not
+reimplement availability polling. A scheduling flow is modeled as an
+`availability` poll with `context_module="scheduling"`, a scheduling-owned
+context resource id, and workflow steps such as collect availability, rank
+candidate slots, decide, notify participants, and hand off to Calendar or
+Appointments.
+
+Poll stores the shared poll/options/responses/result summary. Scheduling owns
+the domain workflow around rooms, calendars, free/busy checks, reminders,
+appointment creation, and optional Workflow integration.
 
 ## Development Install