A parent fetch that fails mid-climb reads as "no parent" (_self_reply_parent is fail-soft), so the climb ends there and the thread refuses coords_missing, the same answer a thread carrying no coordinate gets. During an X outage the bot therefore tells an analyst their thread carries no coordinate when the read was cut short. Carry a truncation flag on AcquiredThread (acquire.py), set when the climb ended on a failed fetch or on the cap, and surface it in the reply so the analyst tags again instead of editing a post that was fine.
Imported from planning/backlog.md.
A parent fetch that fails mid-climb reads as "no parent" (
_self_reply_parentis fail-soft), so the climb ends there and the thread refusescoords_missing, the same answer a thread carrying no coordinate gets. During an X outage the bot therefore tells an analyst their thread carries no coordinate when the read was cut short. Carry a truncation flag onAcquiredThread(acquire.py), set when the climb ended on a failed fetch or on the cap, and surface it in the reply so the analyst tags again instead of editing a post that was fine.Imported from planning/backlog.md.