Continue a prepared execution with its owner's transaction signature

Submit the exact priced operation from prepareWorkflow. Accepts only the signature, not caller-supplied UserOperation fields. Rechecks the current owner/account identity, nonce and funding before first relay. Uses SendUserOpV07 without a server signing key or gas/nonce retry. Material changes or bundler rejection require fresh prepare/review/signing. Repeat calls still require a valid signature and reconcile the existing hash without rebroadcasting. Status polling requires the JWT only. A durable submitting marker precedes the send. The relay after that marker keeps running when the client disconnects. A crash before the RPC leaves the id submitting. A retry looks the hash up at the bundler: a hit is stored as submitted; an unknown hash stays submitting until the ten-minute signing window ends, then becomes unsent and requires a new prepare. That prepare uses the same sender and owner nonce key (entity 0, global), read from EntryPoint.getNonce with no session nonce cache, so an unmined operation and its replacement cannot both be included. A lookup error leaves the marker submitting. A post-send storage failure also preserves the marker. Poll the prepared hash. An empty bundler result during the window is unresolved. Uncertain and submitted records are retained for 24 hours and do not count toward the 64 prepared-record cap. A response is not a receipt; reuse GET /userops/{userOpHash} for confirmation.