Calendar step: several calendars per person
The onboarding hub's calendar step on a test company still in onboarding, from this branch's dev server
16 Oct 2026 · branch hub-several-calendars · captured against propflow-stage · at 17b724f2e65+local
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · A person with no calendar yet
The leasing agent has no calendar, so the step offers Connect a calendar: Google or Microsoft, one sign-in that also puts them on the tours list.
Asserted in the captured DOM — Calendars for tours · Connect a calendar
Sections 2–2
2 · A person with a calendar who is not on the tours list
Dev Persona Started Co (TEST), signed in as the maintenance teammate, whose Google calendar is really connected on stage. They are not on the tours list, so the step offers Add my calendar. The on-list states (Connect another calendar with its note that tours move to the new calendar, and the Disconnect confirmation) were captured too but are not published here: the persona's real connected calendar is a real mailbox, and the contact scan rightly refuses to publish it. They are described in the PR.
Asserted in the captured DOM — Calendars for tours · Add my calendar
