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.
1What counts as DONE for your collections session, so I know when to stop watching it? It has been running about 18 hours and has moved from writing up the program to shipping it: the ADR amendment is merged, the email parsers are up for review with changes requested, and the demand builder is open but conflicting. My predecessor asked this when the session was still writing a document, so its options were stale and I withdrew them. Fastest answer: type /drive "<what done means>" in your own session — it writes straight to me. This page is the fallback.
In plain terms. Your collections session has been going about 18 hours and has quietly turned into a build: the write-up is done, one change is merged, and there are two pieces of code waiting — the email readers and the demand builder. Nobody has told me where it is supposed to stop, so I am watching it with no finish line. Pick the finish line and I will hold it to that and tell you when it is there.
Fable recommends: The collections PRs that are open now land — the parsers (#5939) and the demand builder (#5930) merged and green. I verify they merged and close. It is the only one that is both bounded and checkable today — I can read the PRs. Option 2 is the honest end state but nothing says when it goes live, and option 3 means I never close. Tried first, unsuccessfully: Not run — this is your preference about what your own session is for, which an operator may never decide.
45997cd7 is parked on this.
2The collections session is inert waiting on one call from you: whether to write the collectionsCorrespondents config onto the live property in production. This is the per-property half of the email parsers that just merged (#5939) — which eviction counsel and assistance programmes a property corresponds with, how its unit numbers are written, and the landlord entity on court filings. Without it the parsers run but claim nothing for that property, which is the safe-but-useless state. You said two hours ago to always ask before prod writes, so I am asking.
In plain terms. Your collections session has stopped and is waiting on one yes-or-no from you. The email readers you just merged need a small piece of per-property setup written into the live system before they actually do anything. Nothing breaks either way — without it those readers simply stay quiet for that property. My suggestion is to look at the exact values first, which writes nothing, then say go.
Fable recommends: Show me the exact config first. It stays a dry run until you have seen the property, the current value and the intended one side by side. It costs one command and nothing is written. The script's own notes warn that a bad unit pattern lands and is silently inert, and that a property edit in the same minute can wipe the field — so seeing the actual values before applying is cheap insurance, and 'yes' stays available straight after. Tried first, unsuccessfully: Not run — you gave a standing instruction to always ask before prod writes, so this is yours by your own rule, not a question an operator may settle.