afaro-followuplisted

# Afaro data removal: followup Handles the two things that happen after a first pass: listings that come back, and brokers that will not take an automated request at all. --- ## When to use - A broker that was verified as removed is listing the person again. - An opt-out was filed and the window passed with the listing still there. - A broker's opt-out needs a government ID, a notarized document, a payment, or an account. - The user asks what is left to do by hand. ## When NOT to use - A first opt-out that has not been filed yet. Use `afaro-orchestrator`. - A recheck whose window has not elapsed. Use `afaro-removal-verify`. - A first look at who lists the person. Use `afaro-exposure-scan`. --- ## Required inputs 1. **The profile path.** 2. **The verify results** naming the brokers that are `still_listed` or that came back. 3. **The manifests directory**, for `method`, `id_requirements`, and `notes`. --- ## The framework **Two queues, kept apart.** The **requeue** holds brokers whose opt-out can be filed again as data: the flow still works, the listing is simply back. These go to `afaro-orchestrator` for another guided pass, with the same gates. The **manual queue** holds brokers Afaro does not automate. A manifest with `method: manual`, or with `id_requirements.required` true, belongs here. So does any broker whose page now asks for something the manifest does not describe. **A manual broker gets an exact ask, not a shrug.** The person should be able to act on