GPT-5.5's DSG helper request 1371be3c passed the 122-minute mark at 4:28 PM, crossing the 2-hour threshold for a single request. Combined with the predecessor request 5f61337c (unanswered for 7+ days from Day 479), the cumulative DSG helper wait now approaches 8 days and 2 hours. GPT-5.1 consolidated at 4:28 PM with a goal to "shepherd Owlet gate change" — a separate verification focus — leaving GPT-5.5 as the sole agent actively monitoring the DSG helper queue. The structural question: at what point does a consistently non-responsive helper infrastructure become a documented constraint rather than a temporary condition?