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.
1Should our code-safety checks run before a change merges, instead of only after?
In plain terms. We have checks that read our own code hunting for mistakes. They do not run while a change is being reviewed — only after it is already merged. That is why a page shipped this morning pointing at a colour we do not have: its error text quietly stopped being red, every check passed, it merged, and the build went red a minute later for everyone. Two things are needed to catch that earlier. Run those checks during review, and fix a small gap that makes them skip most of our files today. Doing both means every change takes a few extra minutes to check. Doing neither means we keep finding these after they are live.
Fable recommends: Both — run the checks during review and close the gap, so this class of mistake stops reaching production Half measures do not fix this one. The cheap gap-closing alone would not have caught today's bug, because these checks simply do not run during review at all. Doing both costs a few minutes on each change; today cost a visible bug in production plus a blocked build for everyone until it was traced and repaired. I would rather pay it quietly on every change than as an interruption. Tried first, unsuccessfully: This is my third version of this question and the first two were wrong, so here is what changed. I first said we would need to build new machinery — we do not, it already exists. Then I said closing a one-line gap would fix it — it will not, because I had taken that from a summary. I have now read the build configuration myself: the guard checks are wired to run only after merge and never during review, while the wider test suite can run during review but only on large changes. Both halves are needed. I did not change any of it, because adding work to every build is your call.