This describes version 0.2.2. See thesupport record for measured option combinationsand backend limits; accepted options do not establish full compatibility.
Move files and directories with the policy-checked atomic rename operation.Declining an interactive overwrite, including EOF, returns status 1 and leavesboth paths unchanged; other operands are still processed. A no-clobber skipremains a successful no-op.
Supports force/no-clobber/interactive selection (-f/-n/-i), update modes(-u/--update), backup controls (-b/--backup, -S), explicit targetpaths (-T), directory destinations, and verbose output. Cross-filesystemcopy-and-delete fallback is excluded because public APIs cannot preserve allrequired mode/link/time semantics. POSIX EXDEV can now be classified usingasync 0.22.4 host-platform information. The source remains intact when renameor backup commit fails.Classification of EXDEV does not add a cross-device fallback. Windows renameerror classification and the remaining interactive/backup/update combinationsstill need independent validation.
Same-path moves fail before prompting or making backups, except an explicitno-clobber/update-none skip. After rename, the source entry must have disappeared;a same-inode hard-link no-op reports failure and preserves both names. Publicidentity metadata is unavailable before the operation. Equal-time targets with-i or -u therefore reject explicitly: equal timestamps cannot distinguishan alias from a separate file. This includes separate files whose mtimes happento match. Other processes recreating the source during rename also cause apostcondition error; no second deletion is attempted.
Standalone --version prints exactly mv 0.2.2 followed by onenewline. Standalone --help starts with Usage: mv, lists bothmetadata options, and ends with a newline. Both write to stdout, leave stdinunread, and exit with status 0. Exact-version publication and verificationremain recorded separately in the support record.