[alexeygrigorev]

Creating a podcast, webinar or workshop Card with a guest email now queues its first invitation automatically. A durable creation stream prepares one linked event and guest form, sends editable type-specific email plus a [Proposed] Calendar invitation, and records provider evidence. --skip-email suppresses both guest-facing channels while preparing the same resources. Only these three types may enable automatic intake, and existing Cards are not backfilled.

The UI discloses both sends, preserves retry keys, and shows evidence-based preparing/sent/failed states. One guest form shows Berlin and local time and collects materials afterwards. Explicit time confirmation is bound to the displayed proposal and independent of bio submission. Guest choices and Google acceptance update the same event, remove the prefix and resolve follow-up work. Staff moves require fresh acceptance. Parked Cards pause and archived/released work cancels pending delivery.

For other Card types without an event policy, event propose accepts explicit date, time, duration and guest email. It checks availability and stores a Calendar-only policy on that event, preserving standard join lead, required attendees and Zoom. It creates no first-contact email or automatic intake. Configured policies remain authoritative.

Validation: targeted backend creation/allocator/contact/form/lifecycle/provider-stub regressions, CLI and frontend tests, TypeScript, infra template tests and cfn-lint. Chromium checks used synthetic full-form fixtures. No live guest email was sent. Operational policy and editable copy remain DataOps records.