macos-privacy-permissions-workflowlisted

# macOS Privacy Permissions Workflow ## Purpose Identify the protected operation, responsible executable, and current public authorization contract before changing code or asking the person to change Privacy & Security settings. Keep project declarations, user consent, managed policy, and runtime success as separate evidence. ## When To Use - Use for macOS privacy authorization failures, permission prompts, Settings entries, `tccutil reset`, PPPC policy, and responsible-code attribution. - Use for Accessibility, Automation, Developer Tools, screen/system-audio recording, Input Monitoring, camera, microphone, personal data, Files and Folders, Full Disk Access, App Management, and other current macOS privacy classes. - Do not use private TCC APIs or database details as an application implementation contract. ## Single-Path Workflow 1. Record the exact attempted operation, target resource or process, timestamp, user/session, error domain/code/message, and whether the evidence came from the host, a guest, or a physical Mac. 2. Resolve the responsible code: executable path, bundle identifier, Team ID, designated requirement, signing state, parent/launcher, helper or XPC boundary, and whether the artifact changed. Read `references/responsible-code-and-attribution.md`. 3. Apply the Apple docs gate through `explore-apple-swift-docs`. Record the host macOS version/build and selected SDK/Xcode, then verify the current framework API and settings name. Do not promote an internal se