forked from Manuel/meeting-assistant
25 lines
1.9 KiB
Markdown
25 lines
1.9 KiB
Markdown
## Why
|
|
|
|
macOS can record and process meetings, but several user-decision flows are disabled or block the calendar scheduler. The agreed solution is native actionable notifications plus a menu-bar list of pending requests, so meeting decisions remain accessible when notifications are hidden.
|
|
|
|
## What Changes
|
|
|
|
- Add pending user requests with allowed actions, deadlines, cancellation and one-time responses.
|
|
- Add macOS notification delivery and an actionable pending-request menu, sharing the same decisions.
|
|
- Enable project/workflow approvals and inactivity prompts on macOS; move calendar prompts onto the same non-blocking channel, including attachment to an active meeting.
|
|
- Open a separate interactive agent conversation after an approved workflow-change request without replacing the existing conversation or draft.
|
|
- Package the notification/menu host with a stable application identity and decode the existing numeric recording status correctly.
|
|
- Preserve Windows notification behavior. Microphone device monitoring, audio recovery, sample playback and unrelated agent rendering changes are outside this change.
|
|
|
|
## Capabilities
|
|
|
|
### New Capabilities
|
|
- `desktop-user-requests`: Actionable native notifications and pending-menu decisions, host adapters, lifecycle rules and approved macOS workflow conversations.
|
|
|
|
### Modified Capabilities
|
|
None. Existing approval and calendar behaviors gain a macOS implementation; existing recording-status requirements are repaired without changing the HTTP format.
|
|
|
|
## Impact
|
|
|
|
.NET request lifecycle and existing prompt registrations, read/respond loopback endpoints, Swift AppKit/UserNotifications desktop host, macOS packaging, agent session routing, behavioral tests and operational documentation. Requests and conversations remain process-local; shutdown cancels pending decisions. No remote notification service, new credentials or production deployment is required by this implementation change.
|