Pick an option on each card and press Done; your answer goes straight
back to the session. The raiser's pick is marked. "I'm not sure" and "Take it to the engineering bridge" are real answers.
Nothing open. Good.
Answered and withdrawn (3)
b89173520 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. — answered: For now, it should be manual only to avoid any sort of rate limit issue.
b89173561 When someone changes a file that no test ever touches, our CI currently reports a green tick having run nothing at all — so untested code merges looking checked. Three ways to handle it. Fail those PRs, which is honest but blocks anyone editing a helper script that has no tests. Run the whole test suite instead, which sounds safer but provably checks nothing here — if no test imports the file, no test exercises it. Or keep merging as today but mark the run differently and print a warning naming the files nothing reached, so the tick stops claiming more than it knows. Nothing in the gate changes under the third option; the first one changes what can merge. — answered: Distinct mode plus a ::warning naming the unreached files, graded identically, changing no gating — roughly one script, one case line in decide-unit-tests-conclusion.sh, and a truth-table test
b89174120 The overnight driver session has a checklist that decides when it is allowed to call itself finished. One line on that checklist can never be ticked — not because the work is hard, but because the checker refuses that kind of line on purpose: it reads a note the session writes about itself, so a session could always tick it. The session can add harder lines to its own list but must not remove one, which is why this is coming to you. Replacing it with per-item checks that read GitHub means done is only reached when the actual pull requests are merged. Leaving it means the checklist never reads complete however much work lands. — folded into b89172040