This seems unnecessary. In EEOP_JSONEXPR_PATH, we can if document or jsonpath is NULL, we can just go to jump_end (return NULL) or jump_eval_coercion (NULL need coerce to constrainted domain), no need to worry about ON ERROR, ON EMPTY.
I considered the same shape earlier: keep the empty/error reset in EEOP_JSONEXPR_PATH and stop skipping that step on SQL NULL. Your version is simpler than adding EEOP_JSONEXPR_RESET. No new opcode, and no JIT or back-branch ABI churn.
The commit message still described a RESET opcode that the diff does not add. I adjusted the subject and body to match what the patch actually does (retarget JUMP_IF_NULL at PATH, drop the CONST NULL pad, handle NULL inside ExecEvalJsonExprPath).
Either approach fixes the reported cases. I am fine with whichever version a committer prefers.
