v4.110.1

Deploys

• A lost deploy commit is re-sent on every path (#615). A commit answered 502/503/504, or lost to a dropped connection, is re-sent for the same plan (up to 3 sends, 1s/2s backoff) from apply(), the low-level commit(planId), and the Core target. commit(planId) and the Core target no longer throw on the first 502, and the SDK no longer reads the operation before re-sending. This is safe because the gateway now commits a plan once: a re-sent commit of a running operation answers status: "running" (followed like any in-progress commit) and a finished one replays its result. Run402 Core answers 409 commit_in_progress while another commit of the plan runs, and the SDK re-sends that too.
• Bulk site-removal hint follows the gateway's rename pairing (#614). When the gateway pairs a removed fingerprinted bundle with its replacement, the CLI hint no longer calls the remaining hashed bundles renames, and removed_paths_summary omits by_top_level_dir when the gateway already sends counted_removed_by_dir.

Assets

• BlobSummary declares the list-row URL fields and variants, and assets.rm returns the delete result (kychee-com/run402-private#814).