Implement meeting assistant v1

2026-05-20 02:06:16 +02:00
parent 90df1edc03
commit 0297bcc0f6
120 changed files with 11883 additions and 180 deletions
@@ -0,0 +1,15 @@
+## Why
+
+Meeting Assistant currently focuses V1 runtime support on Windows capture and Outlook enrichment. We need a separate future change to define macOS and Linux build targets without expanding the V1 scope.
+
+## What Changes
+
+- Define supported macOS and Linux build targets for Meeting Assistant.
+- Keep platform-specific capture, hotkey, calendar, and shell integrations isolated per target.
+- Ensure non-Windows builds compile without Windows COM, WASAPI, or user32 dependencies.
+- Define platform-specific test selection so Windows-only tests do not run on macOS/Linux and future macOS/Linux tests do not run on incompatible targets.
+
+## Impact
+
+- Affected specs: build-targets
+- Affected code: project target frameworks, platform service registration, platform integration tests
@@ -0,0 +1,19 @@
+## ADDED Requirements
+
+### Requirement: Meeting Assistant defines macOS and Linux build targets
+Meeting Assistant SHALL define macOS and Linux build targets separately from the Windows build target.
+
+Windows-only integrations such as WASAPI capture, global hotkeys through user32, and Outlook Classic COM SHALL NOT be compiled into macOS or Linux targets.
+
+#### Scenario: Non-Windows target compiles
+- **WHEN** Meeting Assistant is built for macOS or Linux
+- **THEN** Windows-only source files and package dependencies are excluded
+- **AND** the application compiles with portable service registrations or explicit unsupported implementations
+
+#### Scenario: Windows target keeps Windows integrations
+- **WHEN** Meeting Assistant is built for Windows
+- **THEN** WASAPI audio capture, Windows global hotkeys, and Outlook Classic COM enrichment remain available
+
+#### Scenario: Platform-specific tests are gated
+- **WHEN** tests run for a platform target
+- **THEN** tests for incompatible platform APIs are excluded or compiled only for their matching target
@@ -0,0 +1,11 @@
+## 1. Build Targets
+
+- [ ] 1.1 Add explicit macOS and Linux target framework/runtime build coverage.
+- [ ] 1.2 Keep Windows-only implementations excluded from macOS and Linux builds.
+- [ ] 1.3 Add platform service registration for unsupported or future macOS/Linux capture and hotkey implementations.
+
+## 2. Tests
+
+- [ ] 2.1 Split platform-specific tests by compilation target or runtime guard.
+- [ ] 2.2 Add CI/build commands that verify Windows, macOS, and Linux compile targets.
+- [ ] 2.3 Add at least one portable compile test that proves Windows-only packages are not required by non-Windows builds.