Iraq suspended flights to Iran and closed border crossings after the reported Saudi drone attack, then a separate Reuters account named Shalamcheh as one crossing ordered shut. That sequence supports a narrower finding than the early brief suggested: Baghdad moved from a named border order into a broader restriction posture, but the public Record does not identify every post or exception. [E1] [E2]
Reuters put Shalamcheh at the first clear gate in the response, citing two sources for Iraq ordering that crossing with Iran closed. Iraqi News carried the broader frame of flights to Iran being suspended and border crossings being closed after the attack, without the supplied fragment naming the other crossings or the duration. [E1] [E2]
The authority story is therefore about escalation of control, not proof of the launch path. A government can restrict crossings and air links while still leaving unanswered which unit launched the drones, where the launch began, and whether any suspect trail has been established in the public record. [E1] [E2]
That distinction matters because the restrictions are real enough to change movement, but not detailed enough in the supplied Record to support a map of every Iraqi-Iranian route. The article can say Iraq tightened the border-and-flight response after the Saudi attack; it cannot say from this evidence that specific southern posts beyond Shalamcheh closed or that northern routes stayed open. [E1] [E2]
The firmer reading is a response sequence: Shalamcheh was named, flights to Iran were suspended, and border crossings were closed after the attack. The competing reading is narrower, that officials are signaling cooperation and control faster than they are proving the operational trail; an official list of closed crossings or a civil-aviation notice would decide much of that gap. [E1] [E2]