Everything I could decide myself is decided. What's left needs
you. Each one has a recommendation from Fable — if you agree, pick it and
press Done. "I'm not sure" is a real answer and becomes work for me.
You don't need to open the session — pressing Done sends your answer back and it picks up.
1The vendor sync cron retirement (propflowai#7883, held by hold-for-review) is ready. The Zoom ruling of 2026-09-11 settled the vendor LIST — catalog, not sync. It did not settle whether the curated preferred-vendor set should keep refreshing contact details. Both schedules[11] vendors (rate 1 hour) and schedules[12] vendor_contact (4x daily) are in the PR. Note ensure-schedules.sh ONLY upserts and calls put-rule --state ENABLED every deploy, so neither deleting the entry nor disabling the rule by hand is sufficient — explicit deletion in code is the only way to stop it.
In plain terms. You and Fede agreed the vendor list should be a catalog we import once, not a roster we maintain — so the hourly job that re-reads every vendor from AppFolio is ready to be switched off. The part that was never settled: the handful of vendors a property actually calls also have their phone numbers and emails refreshed by that same job. Switch it all off and those details stop refreshing, so they slowly go stale until someone presses the per-vendor sync button. Keep a narrow version running and the vendors you actually dispatch to stay current, at the cost of one more small job to maintain. No vendor data is deleted either way, and either answer is one PR.
The session raising this recommends: The roster — both crons go, and contact freshness reverts to the per-vendor 'Sync from AppFolio' button. Merge #7883 as-is. Either answer merges #7883 unchanged; the roster reading matches your own words in the transcript, and the narrower sweep can be added later if decayed contact data actually causes a dispatch failure. Tried first, unsuccessfully: fable-decide was running on the sibling CI question when this was raised; this one is a customer-risk and business-scope call that the manual's own list (customers, risk) reserves for a human regardless of what a model rung would answer, so it is raised directly rather than waiting on a turn that cannot settle it.