feedback-assistant-workflowlisted

# Feedback Assistant Workflow ## Purpose Prepare one actionable Apple report at a time. Own report quality, evidence selection, privacy review, and the Feedback Assistant handoff; do not replace the specialist workflow that diagnoses the underlying problem. ## Required Evidence 1. Classify the report as a bug, crash, regression, enhancement, documentation issue, or Foundation Models behavior issue. Route security and privacy vulnerabilities to Apple's security reporting program instead of ordinary Feedback Assistant. 2. State one concise title, environment, minimal reproduction, expected result, actual result, frequency, and regression range when known. Keep unrelated issues in separate reports. 3. Build an attachment manifest before opening the submit path. Include source, collection time, purpose, and privacy review for each log, sample project, System Information Report, recording, screenshot, or `.json` feedback attachment. 4. Hand off diagnosis to the owning workflow when needed: `ios-runtime-forensics-workflow` for runtime evidence, `xcode-debugger-mcp-workflow` for a debugging session, `xcode-device-hub-workflow` for connected-device evidence, and `explore-apple-swift-docs` for API routing. ## Feedback Assistant App And Web Workflow 1. Prefer the Feedback Assistant app on Mac, iPhone, or iPad when timely diagnostics matter. Use the website only when the evidence was captured manually or the app is unavailable. 2. On this Mac, inspect `com.apple.appleseed.Feedback