afaro-orchestratorlisted

# Afaro data removal: orchestrator Runs one broker opt-out at a time from a manifest, using the person's local profile, and stops for them before anything is sent. --- ## When to use - The user wants to file an opt-out with one or more people-search brokers. - The user has an Afaro profile file and asks to start, continue, or resume a run. - The user asks what Afaro would do for a given broker before running it. ## When NOT to use - The user only wants to know which brokers currently list them. Use `afaro-exposure-scan`. - The user is rechecking a broker they already filed with. Use `afaro-removal-verify`. - A broker reappeared, or a broker needs an account, a payment, or an ID. Use `afaro-followup`. - The user lives in California and wants the single state deletion request. Use `afaro-drop-submit`. --- ## Required inputs 1. **The profile.** By default it is `profile.json` in the workspace folder the person attached for it, a folder outside this repository holding the profile and its `logs/` directory and nothing else. Look in the attached folders for a `profile.json` before asking anything. When two folders are attached, the profile folder is the one that is not the Afaro repository. If no attached folder holds one, ask: the person may have attached the profile to the conversation instead, which works and changes only where the run log goes. Never guess a path, never store the profile in a file inside this repository, and never repeat profile values back in a log.