local macOS publish completed and /health passed; recording status was idle
full portable suite: 453 passed, 6 failed; remaining failures are existing Windows path, GDI+, and user-environment assumptions on macOS
## Summary
- detect the host operating system and provide platform-specific agent guidance
- capture macOS microphone and system audio through bundled AVFoundation and ScreenCaptureKit helpers
- add native macOS menu-bar controls, global hotkeys, and workflow-agent access
- add EventKit calendar metadata/prompts, active-window screenshots, OCR integration, and platform capability diagnostics
- preserve the newer upstream OpenAI Responses streaming implementation while rebasing onto current `main`
## Verification
- `dotnet test MeetingAssistant.Tests/MeetingAssistant.Tests.csproj -p:EnableWindowsTargeting=true --filter FullyQualifiedName~MacOs`: 15 passed
- `openspec validate add-macos-desktop-controls --strict`: valid
- `openspec validate add-macos-meeting-integrations --strict`: valid
- local macOS publish completed and `/health` passed; recording status was idle
- full portable suite: 453 passed, 6 failed; remaining failures are existing Windows path, GDI+, and user-environment assumptions on macOS
- Introduced MacOsDesktopControlManifest to manage desktop control configurations.
- Implemented MacOsDesktopControlService to handle the lifecycle of the macOS helper process.
- Created MacOsWorkflowRulesEditorWindowService for managing workflow rules through a native window.
- Developed a Swift helper for macOS that integrates with AppKit and Carbon for menu-bar controls and global hotkeys.
- Added support for recording lifecycle actions via HTTP endpoints, maintaining consistency with existing Windows functionality.
- Enhanced user experience by allowing macOS users to start/stop recordings and access settings through a menu-bar interface.
- Documented design decisions, implementation evidence, and verification tasks for the new macOS features.
Risky change: this is a large native-platform feature, not a routine dependency update: 62 files and roughly +4,600/−235 lines add Swift helpers/C# orchestration for microphone and system-audio capture, ScreenCaptureKit screenshots, OCR/cropping, EventKit/AppleScript calendar access, prompts, menu-bar controls, global hotkeys, and new local HTTP controls including application exit and screenshot routes. Shared Windows calendar/screenshot and dependency-registration paths are also refactored.
Are we affected?Likely on macOS and uncertain on Windows. Author-reported macOS publish/health and 15 focused tests are useful, but recording remained idle, the full portable suite had six macOS failures, and exact-head CI is still waiting/blocked. Existing CI validates only the Windows target under Wine, not native macOS. There is no independent proof of TCC privacy prompts, microphone/system audio, screen/calendar access, native-helper packaging, signing/notarization, hotkeys/menu behavior, or endpoint security.
Risk: high privacy/runtime/platform risk. Unsigned native helpers, local control endpoints, AppleScript fallback, and granted permissions can have effects beyond the app process. Rollback is a code revert/republish, but privacy grants and generated artifacts may persist.
Recommendation: do not automation-merge. Approve and obtain exact-head CI, independently smoke-test Windows, then perform a real macOS 13+ end-to-end session. Merge explicitly outside automations only after validating audio/screen/calendar permissions, hotkeys/menu controls, shutdown/settings/screenshot routes, restart, localhost/auth expectations, and signing/notarization strategy.
## Weekly high-risk assessment (2026-08-06)
**Risky change:** this is a large native-platform feature, not a routine dependency update: 62 files and roughly +4,600/−235 lines add Swift helpers/C# orchestration for microphone and system-audio capture, ScreenCaptureKit screenshots, OCR/cropping, EventKit/AppleScript calendar access, prompts, menu-bar controls, global hotkeys, and new local HTTP controls including application exit and screenshot routes. Shared Windows calendar/screenshot and dependency-registration paths are also refactored.
**Are we affected?** **Likely on macOS and uncertain on Windows.** Author-reported macOS publish/health and 15 focused tests are useful, but recording remained idle, the full portable suite had six macOS failures, and exact-head CI is still waiting/blocked. Existing CI validates only the Windows target under Wine, not native macOS. There is no independent proof of TCC privacy prompts, microphone/system audio, screen/calendar access, native-helper packaging, signing/notarization, hotkeys/menu behavior, or endpoint security.
**Risk:** high privacy/runtime/platform risk. Unsigned native helpers, local control endpoints, AppleScript fallback, and granted permissions can have effects beyond the app process. Rollback is a code revert/republish, but privacy grants and generated artifacts may persist.
**Recommendation:** do not automation-merge. Approve and obtain exact-head CI, independently smoke-test Windows, then perform a real macOS 13+ end-to-end session. Merge **explicitly outside automations** only after validating audio/screen/calendar permissions, hotkeys/menu controls, shutdown/settings/screenshot routes, restart, localhost/auth expectations, and signing/notarization strategy.
Weekly automation status (2026-08-13): this remains high risk and was not merged. The branch adds 4,603 lines across 62 files for native macOS microphone/system-audio capture, screen/OCR, calendar access, global hotkeys and local control endpoints, while also refactoring shared Windows paths. Mac impact is likely and privacy/permission side effects can persist; Windows impact remains uncertain.
The exact-head run is red: 458/459 tests passed, but MacOsMeetingAudioSourceTests.RecordingEndpointsCaptureMixedMacOsAudioAndStopNativeProcesses exposes an introduced SQLite lifecycle/cleanup defect. Gitea also reports the PR non-mergeable, and CI has no native macOS coverage.
Recommendation: explicit attended manual merge outside automations only after fixing the test, rebasing onto current main, and obtaining fresh green current-base CI. Then verify a real signed/quarantine-aware macOS build, TCC permissions, mixed audio, helper cleanup, EventKit/AppleScript, screenshot/OCR, controls/hotkeys and privacy/artifact behavior, plus full Windows regression coverage. Revert/publish rollback is possible, but grants and captured artifacts require manual cleanup.
Weekly automation status (2026-08-13): this remains **high risk** and was not merged. The branch adds 4,603 lines across 62 files for native macOS microphone/system-audio capture, screen/OCR, calendar access, global hotkeys and local control endpoints, while also refactoring shared Windows paths. Mac impact is likely and privacy/permission side effects can persist; Windows impact remains uncertain.
The exact-head run is red: 458/459 tests passed, but `MacOsMeetingAudioSourceTests.RecordingEndpointsCaptureMixedMacOsAudioAndStopNativeProcesses` exposes an introduced SQLite lifecycle/cleanup defect. Gitea also reports the PR non-mergeable, and CI has no native macOS coverage.
Recommendation: **explicit attended manual merge outside automations** only after fixing the test, rebasing onto current `main`, and obtaining fresh green current-base CI. Then verify a real signed/quarantine-aware macOS build, TCC permissions, mixed audio, helper cleanup, EventKit/AppleScript, screenshot/OCR, controls/hotkeys and privacy/artifact behavior, plus full Windows regression coverage. Revert/publish rollback is possible, but grants and captured artifacts require manual cleanup.
Weekly status (2026-09-01): this remains high risk. The 62-file macOS feature adds native Swift audio capture, ScreenCaptureKit, EventKit/AppleScript, OCR/screenshots, controls, HTTP routes, and shared Windows-path refactors. Exact-head run 3183 is blocked and executed no steps, so the previous 458/459 cleanup failure is not proven fixed. Impact is likely on macOS and uncertain on Windows. Because this is a fork and the runner is host-impacting, do not approve the fork workflow directly. Copy the reviewed revision to a trusted same-repository branch, obtain green Windows CI, and perform attended macOS permission/audio/helper/calendar/OCR/signing tests before an explicit manual merge outside automations.
Weekly status (2026-09-01): this remains **high risk**. The 62-file macOS feature adds native Swift audio capture, ScreenCaptureKit, EventKit/AppleScript, OCR/screenshots, controls, HTTP routes, and shared Windows-path refactors. Exact-head run 3183 is blocked and executed no steps, so the previous 458/459 cleanup failure is not proven fixed. Impact is **likely on macOS and uncertain on Windows**. Because this is a fork and the runner is host-impacting, do not approve the fork workflow directly. Copy the reviewed revision to a trusted same-repository branch, obtain green Windows CI, and perform attended macOS permission/audio/helper/calendar/OCR/signing tests before an **explicit manual merge outside automations**.
Weekly high-risk update for exact head 84dc696ce9596030b843aff1358ca97a2903af69: this remains unmergeable and now spans 66 files (+4,779/−245), adding native macOS microphone/system-audio capture, screenshots, EventKit/AppleScript calendar access, global hotkeys/menu controls, WebKit workflow UI, local control routes, and shared Windows-path changes. We are likely affected on the next manual publish through the shared Windows code; macOS impact remains uncertain because there is no native macOS CI. The exact-head run was cancelled without a runner/steps, current main is four commits ahead, and the branch carries an older Agent Framework dependency. Screen-recording privacy metadata, EventKit consent, signing/notarization, unauthenticated loopback controls, and retained WAV/backlog cleanup remain unresolved. Risk includes privacy/permission failure, capture/transcription regressions, stale dependency conflict resolution, and manual artifact/state cleanup. Recommendation: do not merge in automation. Rebase and resolve conflicts while preserving current main behavior, obtain trusted exact-head Windows CI, then perform attended native macOS 13+ audio/screen/calendar/hotkey/helper, auth/loopback, signing/notarization, and recovery tests before an explicit manual merge outside automations.
Weekly high-risk update for exact head `84dc696ce9596030b843aff1358ca97a2903af69`: this remains unmergeable and now spans 66 files (+4,779/−245), adding native macOS microphone/system-audio capture, screenshots, EventKit/AppleScript calendar access, global hotkeys/menu controls, WebKit workflow UI, local control routes, and shared Windows-path changes. We are likely affected on the next manual publish through the shared Windows code; macOS impact remains uncertain because there is no native macOS CI. The exact-head run was cancelled without a runner/steps, current main is four commits ahead, and the branch carries an older Agent Framework dependency. Screen-recording privacy metadata, EventKit consent, signing/notarization, unauthenticated loopback controls, and retained WAV/backlog cleanup remain unresolved. Risk includes privacy/permission failure, capture/transcription regressions, stale dependency conflict resolution, and manual artifact/state cleanup. Recommendation: do not merge in automation. Rebase and resolve conflicts while preserving current main behavior, obtain trusted exact-head Windows CI, then perform attended native macOS 13+ audio/screen/calendar/hotkey/helper, auth/loopback, signing/notarization, and recovery tests before an explicit manual merge outside automations.
Weekly status (2026-09-10): head 84dc696ce9596030b843aff1358ca97a2903af69 and the September3 blockers are unchanged. High risk; blocked. Gitea reports conflicts and main has advanced through further test-package updates. Exact-head run 3206 was cancelled with no runner or executed steps: this is missing validation, not a new test failure. Author-managed rebase/conflict resolution, trusted exact-head Windows CI and attended native macOS/privacy/loopback/signing/audio-recovery checks remain required before explicit manual merge outside automations. This feature branch is not managed by Renovate.
Weekly status (2026-09-10): head `84dc696ce9596030b843aff1358ca97a2903af69` and the September3 blockers are unchanged. **High risk; blocked.** Gitea reports conflicts and main has advanced through further test-package updates. [Exact-head run 3206](https://gitea.schweigert.cloud/Manuel/meeting-assistant/actions/runs/3206) was cancelled with no runner or executed steps: this is missing validation, not a new test failure. Author-managed rebase/conflict resolution, trusted exact-head Windows CI and attended native macOS/privacy/loopback/signing/audio-recovery checks remain required before explicit manual merge outside automations. This feature branch is not managed by Renovate.
<!-- weekly-2026-09-10 84dc696ce9596030b843aff1358ca97a2903af69 -->
Weekly status,2026-09-17: unchanged head 84dc696ce9596030b843aff1358ca97a2903af69 remains HIGH and conflicting. Run3206 now executed: build passed, tests459/461 passed. Failures were locked speakers.db cleanup in macOS mixed-audio endpoint test and a transcript-workflow timeout. This supersedes the prior cancellation-only status. Broad native macOS audio/screenshot/OCR/calendar/privacy/control changes and shared Windows changes still require author-managed conflict resolution, green trusted CI and attended native permission/audio/control checks before explicit manual merge outside automations. Revert/republish cannot automatically undo privacy grants or captured artifacts.
Weekly status,2026-09-17: unchanged head `84dc696ce9596030b843aff1358ca97a2903af69` remains **HIGH and conflicting**. [Run3206](https://gitea.schweigert.cloud/Manuel/meeting-assistant/actions/runs/3206) now executed: build passed, tests459/461 passed. Failures were locked speakers.db cleanup in macOS mixed-audio endpoint test and a transcript-workflow timeout. This supersedes the prior cancellation-only status. Broad native macOS audio/screenshot/OCR/calendar/privacy/control changes and shared Windows changes still require author-managed conflict resolution, green trusted CI and attended native permission/audio/control checks before explicit manual merge outside automations. Revert/republish cannot automatically undo privacy grants or captured artifacts.
<!-- weekly-2026-09-17 84dc696ce9596030b843aff1358ca97a2903af69 -->
Attended review update (2026-09-18), exact head 723298e7203402e1fb266932f62ebb86c329f27e: left open for native macOS validation.
The four integration conflicts are resolved by normally merging current main e011e36 into the existing fork branch Daniel/meeting-assistant:codex/macos-support; no history was replaced. The resolution retains the macOS platform registration alongside main's validated options, Windows NAudio registration, Responses client options and speaker-recognition changes. Both health regressions are retained. A reproduced Windows fixture-cleanup failure was fixed by disposing its test host and clearing only that fixture's SQLite pool before directory deletion. The README now accurately distinguishes the existing Windows and macOS menu controls.
Verification on the exact new tree: focused platform/health/workflow tests 75/75, full solution tests 542/542, Release builds for net10.0 and net10.0-windows10.0.19041.0, and strict OpenSpec validation for add-macos-desktop-controls and add-macos-meeting-integrations all passed. An independent review of the integration diff found no issue. The native Swift helpers are not compiled or exercised by these Windows checks. Exact-head CI run 3910 was cancelled through the supported UI during the reproduced external IPv4 outage on Windows and Roach; cancellation was read back. It must be rerun after connectivity recovers and is not a passing result. The final main run 3900 was also cancelled during this outage; prior green PR checks and local final-tree tests remain valid, but the combined main CI is unverified.
Remaining blocker: this Windows host cannot verify the real macOS Microphone and Screen & System Audio permission flow, sustained simultaneous native microphone/system capture, native desktop integrations, or stopping without orphaned capture processes. Before merging, run the native macOS build/publish and those operational checks on supported hardware, record the results, and require green exact-head CI. Do not treat the simulated capture tests or resolved conflicts as native platform qualification. No local workstation app was restarted and no OpenSpec change was archived.
Attended review update (2026-09-18), exact head `723298e7203402e1fb266932f62ebb86c329f27e`: **left open for native macOS validation.**
The four integration conflicts are resolved by normally merging current main `e011e36` into the existing fork branch `Daniel/meeting-assistant:codex/macos-support`; no history was replaced. The resolution retains the macOS platform registration alongside main's validated options, Windows NAudio registration, Responses client options and speaker-recognition changes. Both health regressions are retained. A reproduced Windows fixture-cleanup failure was fixed by disposing its test host and clearing only that fixture's SQLite pool before directory deletion. The README now accurately distinguishes the existing Windows and macOS menu controls.
Verification on the exact new tree: focused platform/health/workflow tests **75/75**, full solution tests **542/542**, Release builds for `net10.0` and `net10.0-windows10.0.19041.0`, and strict OpenSpec validation for `add-macos-desktop-controls` and `add-macos-meeting-integrations` all passed. An independent review of the integration diff found no issue. The native Swift helpers are not compiled or exercised by these Windows checks. Exact-head [CI run 3910](https://gitea.schweigert.cloud/Manuel/meeting-assistant/actions/runs/3910) was cancelled through the supported UI during the reproduced external IPv4 outage on Windows and Roach; cancellation was read back. It must be rerun after connectivity recovers and is not a passing result. The final main run 3900 was also cancelled during this outage; prior green PR checks and local final-tree tests remain valid, but the combined main CI is unverified.
Remaining blocker: this Windows host cannot verify the real macOS Microphone and Screen & System Audio permission flow, sustained simultaneous native microphone/system capture, native desktop integrations, or stopping without orphaned capture processes. Before merging, run the native macOS build/publish and those operational checks on supported hardware, record the results, and require green exact-head CI. Do not treat the simulated capture tests or resolved conflicts as native platform qualification. No local workstation app was restarted and no OpenSpec change was archived.
Weekly status for bf6e1e7560c6bdfcebf69ad0e3240b4de647adb6: HIGH and conflicting; no automated merge. The prior542passing local tests/fixes covered earlier723298e. Current exact-head validation remains missing.
Run3962 cancelled both Windows and newly added native-macOS jobs after0seconds following required-condition blocking; the red statuses are not new test assertion failures. The PR now DOES define macOS CI using macos:host, but neither job has successful current-head evidence.
Resolve current-main conflicts while preserving earlier fixes, obtain green trusted exact-head Windows/macOS CI, then record attended native permissions, sustained mixed audio, Swift helper cleanup, calendar/screenshot and controls checks before explicit manual merge outside automations. Scope is74files/+5095/-269; older evidence included early recording termination and calendar fallback, so current native behavior needs qualification. Revert/republish does not undo privacy grants or captured artifacts. This is Daniel's feature branch, not a Renovate branch; no checkbox applies.
Weekly status for `bf6e1e7560c6bdfcebf69ad0e3240b4de647adb6`: **HIGH and conflicting; no automated merge.** The prior542passing local tests/fixes covered earlier723298e. Current exact-head validation remains missing.
[Run3962](https://gitea.schweigert.cloud/Manuel/meeting-assistant/actions/runs/3962) cancelled both Windows and newly added native-macOS jobs after0seconds following required-condition blocking; the red statuses are not new test assertion failures. The PR now DOES define macOS CI using macos:host, but neither job has successful current-head evidence.
Resolve current-main conflicts while preserving earlier fixes, obtain green trusted exact-head Windows/macOS CI, then record attended native permissions, sustained mixed audio, Swift helper cleanup, calendar/screenshot and controls checks before explicit manual merge outside automations. Scope is74files/+5095/-269; older evidence included early recording termination and calendar fallback, so current native behavior needs qualification. Revert/republish does not undo privacy grants or captured artifacts. This is Daniel's feature branch, not a Renovate branch; no checkbox applies.
<!-- weekly-2026-09-25 bf6e1e7560c6bdfcebf69ad0e3240b4de647adb6 -->
Some required checks failed
1 workflow awaiting approval
The workflow will only run after approval from the repository maintainer.
PR and Push Build/Test / macos-build-and-test (pull_request) Canceled after 0s
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
mainVerification
dotnet test MeetingAssistant.Tests/MeetingAssistant.Tests.csproj -p:EnableWindowsTargeting=true --filter FullyQualifiedName~MacOs: 15 passedopenspec validate add-macos-desktop-controls --strict: validopenspec validate add-macos-meeting-integrations --strict: valid/healthpassed; recording status was idleWeekly high-risk assessment (2026-08-06)
Risky change: this is a large native-platform feature, not a routine dependency update: 62 files and roughly +4,600/−235 lines add Swift helpers/C# orchestration for microphone and system-audio capture, ScreenCaptureKit screenshots, OCR/cropping, EventKit/AppleScript calendar access, prompts, menu-bar controls, global hotkeys, and new local HTTP controls including application exit and screenshot routes. Shared Windows calendar/screenshot and dependency-registration paths are also refactored.
Are we affected? Likely on macOS and uncertain on Windows. Author-reported macOS publish/health and 15 focused tests are useful, but recording remained idle, the full portable suite had six macOS failures, and exact-head CI is still waiting/blocked. Existing CI validates only the Windows target under Wine, not native macOS. There is no independent proof of TCC privacy prompts, microphone/system audio, screen/calendar access, native-helper packaging, signing/notarization, hotkeys/menu behavior, or endpoint security.
Risk: high privacy/runtime/platform risk. Unsigned native helpers, local control endpoints, AppleScript fallback, and granted permissions can have effects beyond the app process. Rollback is a code revert/republish, but privacy grants and generated artifacts may persist.
Recommendation: do not automation-merge. Approve and obtain exact-head CI, independently smoke-test Windows, then perform a real macOS 13+ end-to-end session. Merge explicitly outside automations only after validating audio/screen/calendar permissions, hotkeys/menu controls, shutdown/settings/screenshot routes, restart, localhost/auth expectations, and signing/notarization strategy.
Weekly automation status (2026-08-13): this remains high risk and was not merged. The branch adds 4,603 lines across 62 files for native macOS microphone/system-audio capture, screen/OCR, calendar access, global hotkeys and local control endpoints, while also refactoring shared Windows paths. Mac impact is likely and privacy/permission side effects can persist; Windows impact remains uncertain.
The exact-head run is red: 458/459 tests passed, but
MacOsMeetingAudioSourceTests.RecordingEndpointsCaptureMixedMacOsAudioAndStopNativeProcessesexposes an introduced SQLite lifecycle/cleanup defect. Gitea also reports the PR non-mergeable, and CI has no native macOS coverage.Recommendation: explicit attended manual merge outside automations only after fixing the test, rebasing onto current
main, and obtaining fresh green current-base CI. Then verify a real signed/quarantine-aware macOS build, TCC permissions, mixed audio, helper cleanup, EventKit/AppleScript, screenshot/OCR, controls/hotkeys and privacy/artifact behavior, plus full Windows regression coverage. Revert/publish rollback is possible, but grants and captured artifacts require manual cleanup.Weekly status (2026-09-01): this remains high risk. The 62-file macOS feature adds native Swift audio capture, ScreenCaptureKit, EventKit/AppleScript, OCR/screenshots, controls, HTTP routes, and shared Windows-path refactors. Exact-head run 3183 is blocked and executed no steps, so the previous 458/459 cleanup failure is not proven fixed. Impact is likely on macOS and uncertain on Windows. Because this is a fork and the runner is host-impacting, do not approve the fork workflow directly. Copy the reviewed revision to a trusted same-repository branch, obtain green Windows CI, and perform attended macOS permission/audio/helper/calendar/OCR/signing tests before an explicit manual merge outside automations.
Weekly high-risk update for exact head
84dc696ce9596030b843aff1358ca97a2903af69: this remains unmergeable and now spans 66 files (+4,779/−245), adding native macOS microphone/system-audio capture, screenshots, EventKit/AppleScript calendar access, global hotkeys/menu controls, WebKit workflow UI, local control routes, and shared Windows-path changes. We are likely affected on the next manual publish through the shared Windows code; macOS impact remains uncertain because there is no native macOS CI. The exact-head run was cancelled without a runner/steps, current main is four commits ahead, and the branch carries an older Agent Framework dependency. Screen-recording privacy metadata, EventKit consent, signing/notarization, unauthenticated loopback controls, and retained WAV/backlog cleanup remain unresolved. Risk includes privacy/permission failure, capture/transcription regressions, stale dependency conflict resolution, and manual artifact/state cleanup. Recommendation: do not merge in automation. Rebase and resolve conflicts while preserving current main behavior, obtain trusted exact-head Windows CI, then perform attended native macOS 13+ audio/screen/calendar/hotkey/helper, auth/loopback, signing/notarization, and recovery tests before an explicit manual merge outside automations.Weekly status (2026-09-10): head
84dc696ce9596030b843aff1358ca97a2903af69and the September3 blockers are unchanged. High risk; blocked. Gitea reports conflicts and main has advanced through further test-package updates. Exact-head run 3206 was cancelled with no runner or executed steps: this is missing validation, not a new test failure. Author-managed rebase/conflict resolution, trusted exact-head Windows CI and attended native macOS/privacy/loopback/signing/audio-recovery checks remain required before explicit manual merge outside automations. This feature branch is not managed by Renovate.Weekly status,2026-09-17: unchanged head
84dc696ce9596030b843aff1358ca97a2903af69remains HIGH and conflicting. Run3206 now executed: build passed, tests459/461 passed. Failures were locked speakers.db cleanup in macOS mixed-audio endpoint test and a transcript-workflow timeout. This supersedes the prior cancellation-only status. Broad native macOS audio/screenshot/OCR/calendar/privacy/control changes and shared Windows changes still require author-managed conflict resolution, green trusted CI and attended native permission/audio/control checks before explicit manual merge outside automations. Revert/republish cannot automatically undo privacy grants or captured artifacts.Attended review update (2026-09-18), exact head
723298e7203402e1fb266932f62ebb86c329f27e: left open for native macOS validation.The four integration conflicts are resolved by normally merging current main
e011e36into the existing fork branchDaniel/meeting-assistant:codex/macos-support; no history was replaced. The resolution retains the macOS platform registration alongside main's validated options, Windows NAudio registration, Responses client options and speaker-recognition changes. Both health regressions are retained. A reproduced Windows fixture-cleanup failure was fixed by disposing its test host and clearing only that fixture's SQLite pool before directory deletion. The README now accurately distinguishes the existing Windows and macOS menu controls.Verification on the exact new tree: focused platform/health/workflow tests 75/75, full solution tests 542/542, Release builds for
net10.0andnet10.0-windows10.0.19041.0, and strict OpenSpec validation foradd-macos-desktop-controlsandadd-macos-meeting-integrationsall passed. An independent review of the integration diff found no issue. The native Swift helpers are not compiled or exercised by these Windows checks. Exact-head CI run 3910 was cancelled through the supported UI during the reproduced external IPv4 outage on Windows and Roach; cancellation was read back. It must be rerun after connectivity recovers and is not a passing result. The final main run 3900 was also cancelled during this outage; prior green PR checks and local final-tree tests remain valid, but the combined main CI is unverified.Remaining blocker: this Windows host cannot verify the real macOS Microphone and Screen & System Audio permission flow, sustained simultaneous native microphone/system capture, native desktop integrations, or stopping without orphaned capture processes. Before merging, run the native macOS build/publish and those operational checks on supported hardware, record the results, and require green exact-head CI. Do not treat the simulated capture tests or resolved conflicts as native platform qualification. No local workstation app was restarted and no OpenSpec change was archived.
Weekly status for
bf6e1e7560c6bdfcebf69ad0e3240b4de647adb6: HIGH and conflicting; no automated merge. The prior542passing local tests/fixes covered earlier723298e. Current exact-head validation remains missing.Run3962 cancelled both Windows and newly added native-macOS jobs after0seconds following required-condition blocking; the red statuses are not new test assertion failures. The PR now DOES define macOS CI using macos:host, but neither job has successful current-head evidence.
Resolve current-main conflicts while preserving earlier fixes, obtain green trusted exact-head Windows/macOS CI, then record attended native permissions, sustained mixed audio, Swift helper cleanup, calendar/screenshot and controls checks before explicit manual merge outside automations. Scope is74files/+5095/-269; older evidence included early recording termination and calendar fallback, so current native behavior needs qualification. Revert/republish does not undo privacy grants or captured artifacts. This is Daniel's feature branch, not a Renovate branch; no checkbox applies.
The workflow will only run after approval from the repository maintainer.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.