Everything I could decide myself is decided. What's left needs
you. Each one carries the recommendation of the session that raised it — if you
agree, pick it and press Done. A model's opinion, where there is one, appears on the card
as a receipt line; cards with no receipt were never put to a model. "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.
1About a thousand of Western Slope's finished maintenance jobs are sitting in PropFlow as open work, because their AppFolio closes tickets with wording PropFlow does not recognise and anything unrecognised defaults to open. The wording fix is small and has precedent. The catch is that flipping a ticket to done is what triggers the resident rating text, so the fix could text residents about jobs finished in 2023. How do you want it shipped?
In plain terms. Do you want the fix shipped with the old jobs kept quiet? Their AppFolio marks a job done with wording we do not recognise, so about a thousand finished jobs sit in PropFlow as open work. Correcting that flips them to done, and flipping a job to done is what texts a resident asking them to rate it. Some of those jobs finished in 2023. Shall I make the old ones silent and let only real, recent closures text anyone?
The session raising this recommends: Fix it, and keep the old jobs silent The wording fix is the documented procedure and has precedent (PR #2425, 'Ready to Bill' mapped to completed, 2026-06-17). What makes it not a free merge: run-work-order-sync.ts:250 wires onCompleted to signalMaintenanceRatingDue, and work-order.ts:1469 fires it on any non-terminal to completed flip, so a mirror tick after the merge can send a rating request about a ticket closed in 2023. completionPredatesArchival (work-order.ts:1472) is the existing precedent for silencing a repair-completion while keeping a real one audible. Measured in propflow-prod: 235 of 244 PropFlow-open work orders across four Western Slope properties carry an AppFolio status of 'Completed No Need To Bill'; the unmapped-value ledger has counted that status 110,292 times since the 2026-09-13 onboarding. Separately, the everyday mirror only refetches the last 90 days, so most of these rows need a one-off backfill and will not self-heal. Tried first, unsuccessfully: Traced the enrichment sweep end to end. Its EventBridge rule is ENABLED and firing; the run rows show the syncable population jumping from 21 to 1,070 on 09-14 and every run since 09-15 ending exactly at the 640-second drain deadline. Tied the jump to the Western Slope onboarding on 09-13, then to the unrecognised-status default in mapAfStatus, then confirmed it by sampling four properties' work-order rows in prod against the raw AppFolio status stored on each. What I cannot settle alone is whether to accept outbound texts to real residents as the cost of the repair — that is a customer-communication call.