Files
meeting-assistant/openspec/changes/attach-calendar-metadata-to-active-meeting/tasks.md
T
codex 1a341f1eaa
PR and Push Build/Test / build-and-test (push) Successful in 15m2s
feat: attach calendar metadata to active meetings
2026-08-05 11:58:25 +02:00

1.9 KiB

1. Calendar Selection Contract

  • 1.1 Verify the standalone Outlook selector covers a meeting started one minute early and remains ambiguous for concurrent upcoming meetings.

2. Prompt Attach Action

  • 2.1 Add a failing scheduler behavior test that an active-recording prompt exposes metadata attachment and routes the exact appointment metadata without stop/start.
  • 2.2 Implement the prompt request/response and recording-controller attach contract to pass the scheduler behavior test.
  • 2.3 Add the conditional Add metadata to current meeting Windows toast action and activation mapping while preserving Yes/No behavior.

3. Active Meeting Metadata

  • 3.1 Add a failing coordinator behavior test for attaching title, eligible transformed attendees, agenda, and scheduled end to active meeting, assistant-context, and transcript artifacts without interrupting recording.
  • 3.2 Implement synchronized active-run metadata attachment through the shared metadata application path.
  • 3.3 Add a failing race behavior test proving explicit prompted metadata wins over a delayed standalone lookup, then implement the run-level explicit-assignment guard.
  • 3.4 Add a stale-action behavior test proving attachment is a no-op after capture stops.
  • 3.5 Add a failing attachment behavior test proving a persistence failure does not suppress the fallback Outlook lookup, then mark metadata explicit only after successful persistence.

4. Verification

  • 4.1 Run focused calendar and recording coordinator tests, then the full test suite and Windows-target build.
  • 4.2 Run openspec validate attach-calendar-metadata-to-active-meeting --strict and verify the change task list is complete.
  • 4.3 Perform the required DRY, SOLID, and KISS refactoring passes with tests after any changes.
  • 4.4 Verify the notification and active-recording behavior through the safest available operational surface without interrupting live meeting work.