Support meeting preparation, scheduling and follow-through

Priority: P1 (build on the foundation).

Calendar connectivity should help the user organise and prepare their day, not merely list events.

Acceptance criteria

• Prepare a meeting summary from attendees, relevant correspondence, linked documents and previous decisions, with sources.
• Suggest available times respecting working hours, timezone, conflicts and travel buffers.
• Preview invitation/reschedule details and attendees before any action requiring authorization.
• Turn supplied meeting notes or an authorised transcript into decisions and proposed tasks.
• Persist confirmed commitments with owners and deadlines and link them to the meeting.
• Test recurring events, DST, unavailable participants, missing data and duplicate invitations; never claim attendee acceptance without evidence.

Dependencies and boundaries

Depends on connected calendar/email, personal context, trustworthy tasks and action permissions. Start with preparation and scheduling; recording is not implied.

Implementation approach

Audit current main first: some foundations and recent fixes already exist. Close remaining user-visible gaps and preserve working behaviour. This issue records the personal-assistant product backlog, not a claim that every underlying capability is absent. Add focused regression coverage for the behaviour changed.

Start by auditing the current main, as requested, to identify which meeting preparation and scheduling foundations already exist. Trace the connected calendar/email, personal context, task, and action-permission boundaries before selecting one remaining user-visible gap. Add focused regression coverage for the behavior changed, including relevant recurring-event, DST, authorization, or duplicate-invitation cases.