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.
1Maintenance-eval bench tenant: run the final promoteClaim so +17202122112 becomes PRIMARY? It arms ~20-30 real SMS/night to the owned tester line and clears the 3 steady-state SYSTEM reds (handyman-relay, handyman-reverse-relay-roundtrip, handyman-close-with-photo).
In plain terms. The test tenant for the nightly maintenance check still has a fake phone number set as its main one, so three checks fail every night. The real number is already attached, it just is not the main one. Should Smith flip it now?
Fable recommends: Promote now (Smith runs --apply) The claim has been on the bench tenant since 09-06; one promote flips outbound to a PropFlow-owned line nobody reads, cents/night, test property only, #7169 guards in place. Tried first, unsuccessfully: Read-only seed dry-run + smith-db on propflow-prod (09-09): +17202122112 is an ACTIVE SECONDARY claim on pers_653bb3b4 (created 09-06 15:14Z), PRIMARY is still +12065551001, so outbound 555-skips; 09-07/08/09 evals all red on the same 3 presets. I did NOT run --apply: it is a prod write that arms live sends, and the script's own rule says a human go comes first.