Run python3 scripts/probe_providers.py --apps notes reminders --output <new-private-receipt.json> from this skill's directory. The helper sends bounded read-only AppleScript queries and prints safe status codes. It may launch an app or show a macOS Automation prompt. It creates no notes/reminders and changes no permissions. Record caller context; a shell probe does not establish launchd/SSH permission.
Identify the real caller executable, launchd owner, target account/folder/list, and existing delivery ledger. Recheck from an equivalent installed caller context if results differ. Loading environment variables alone does not reproduce its Automation identity. Keep credentials and provider content local.
For an outstanding effect, read its existing marker/provider ID in its original target and compare stored payload identity. Preserve success, failed-cap, uncertain, and quarantined history. An absent marker is not a delivery receipt; a different account or folder can give a false absence. Do not write a test item into personal data unless that narrow action is authorized.
Choose recovery from the measured failure. permission_denied (-1743) calls for inspection of the actual caller's Automation grant. A process timeout or Apple-event timeout (-1712) is not evidence of denied permission. An unanswered privacy prompt can also appear as a process timeout. Reminders has a separate Privacy & Security > Reminders data grant in addition to Automation; inspect the actual responsible caller (terminal, Python, SSH or runner). Successful name/version queries do not prove list/data access. If those succeed but list queries hang, inspect UI prompts and TCC decision metadata before a restart. Recheck fresh requests after a user changes a grant; older pending calls may still be blocked. Never widen data access without specific authorization. Check an independent target before blaming system-wide transport. Use ordinary app quit/reopen only when active work is safe; then rerun the same probe. The protected system Apple Events kickstart is rejected with error150 under SIP on this Mac even after sudo authentication. Do not recommend disabling SIP, resetting TCC, or killing protected daemons to bypass that failure. A normal Mac restart is a candidate for persistent transport failure, after coordinating shared ASR jobs and other active work; it is not a proven fix.
Retry only the particular effect when its caller permission, exact target, payload identity, absence/presence, idempotency policy, and existing task authorization support it. Never reset a retry cap or uncertain/quarantined row merely to make readiness green. Do not replay a capture to repair one projection. Confirm provider ID/marker readback and durable receipt separately.

For GUI inspection, native computer-use accessibility can work while AppleScript System Events enumeration hangs. Peekaboo local-binary, Bridge-host, and CUA permissions are separate: inspect its actual execution route before interpreting an ungranted local permission as an unavailable tool. Prefer read-only UI state first; obtain required handover/permission confirmation before input or grants.

Report app-by-app live probe results, caller context, ledger disposition, item readback, mutations performed, and the next unresolved boundary. For project binding or receipt design, read the shared contract. For Penny only, read its existing adapter binding; keep that integration and ledger rather than creating a second delivery path.

Validate reachability with the same bounded probe after recovery. Close delivery only after the requested target/item and durable receipt agree. Do not generalize one successful probe to permanent macOS reliability.

References: Apple SIP, Apple Automation permissions, Reminders data permissions, normal restart.

apple-effects-reliability