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.
1Clara's free-month answer is built, reviewed and tested. Two things are left and both are yours: set Camellia's value, then merge. They have to happen in that order — if it merges first, a resident asking about the free month can be told which month it is by one of Camellia's two specials and not by the other, in the same conversation. How do you want to take it?
The reviewer scoped its own approval, verbatim: '🟢 LGTM — the round-3 🔴 is fixed at the cause; no blocking findings remain. ⚠️ Approves the CODE only: the migration precondition in the PR body is still unmet (dry-run only, no --apply), and the hold-for-review label is what should keep this unmerged until it is applied and verified.' — PR #5553. Note on merging: the branch is behind main. If anyone updates it from main before merging, the Unit Tests check can flip from 'Full suite passed' back to a lane that ran nothing, and the check name does not change when that happens — re-read its title, not its colour.
In plain terms. Camellia has two move-in specials on file. One is written by hand and spells out that the free month is the second month; the other is pulled off their website every day and just says '1 month free'. This change teaches Clara to fill in the missing half — but only once Camellia is marked as a second-month property. Until that mark is set, she explains it properly on one special and not on the other, and a prospect can hear both in one conversation. Setting the mark takes seconds. Merging before setting it is what creates the problem, which is why the order matters.
Fable recommends: Go — set Camellia's value first, then merge It is finished and independently checked: the reviewer approved it, and the full test suite ran and passed on the merged version — all twelve parts, the first time this change has ever been properly tested. The only thing standing between that and a resident getting a straight answer is one setting on Camellia, which takes seconds and is reversible. The order is the whole point: merging first is what creates the inconsistent answer, and nothing warns you when it happens. Tried first, unsuccessfully: Not a design question — the design was already decided by you twice (b86132232, then the reversal to per-property). This is only about doing the two acts and their order. No second model consulted.