Do not equate an unmet prerequisite with an attempted-and-failed prerequisite when a UI

Do not equate an unmet prerequisite with an attempted-and-failed prerequisite when a UI changes step order. A server may correctly keep verification incomplete while incorrectly opening a support issue on each normal intermediate save. Keep verification gating separate from support escalation; trigger the latter on explicit failed completion/recovery or an actual help request. Validate this with timestamp order across authoritative writes and client permission events, and distinguish automatic help records from user intent. This applies to incremental forms that defer location or another requirement until the end; it does not imply all later bypasses are unnecessary.