`move` 0.1.0

Rename a file or directory in place, never over an existing name (the kernel refuses it, even if another process creates it mid-move); locked, atomic, idempotent with --if-sha256, with --dry-run. One directory: a move to another is not offered. With --remove and --if-sha256, a file is removed by renaming it to a tombstone, and nothing is deleted.

move [--root DIR] [--if-sha256 HEX] [--dry-run] [--format json|text] PATH NEWNAME | move --remove --if-sha256 HEX [--root DIR] [--dry-run] PATH

output: one JSON document
schema: move.v1
reversibility: irreversible-bounded
guarantees: deterministic, idempotent, atomic, dry_run
concurrency: locked: of writers racing with the same precondition, exactly one wins and the others are refused (M7)
confinement: beneath: with --root, paths are checked lexically against it and then opened beneath it one component at a time, following no symbolic link (path.symlink), so nothing outside the root is reachable through one; without it, a reader opens the path as given, links and all, and a writer still follows no link in the file's own name
reads the environment: no
reads the clock: no
compiler: de4e52fd8180
for an agent: SKILL.md (move skill)

Authority

Derived by cancho authority from the source, embedded in the binary, and checked against tools.toml's ceiling in CI. Every label is bounded.

args
dir_read
dir_write
err_write
file_read
file_write
fs_read("")
heap
io_write

What the row cannot say:

path extent: a path from the command line is checked at run time, so the row says fs_read("")
what a symlink reaches
what standard output carries
resource use beyond the tool's own caps (memory, wall time)
per-invocation behaviour such as --dry-run, which the row cannot see

Operands

Operand	Role	How many	Meaning
`PATH`	`path-write`	1	the file or directory to rename
`NEWNAME`	`none`	0 to 1	its new name: one component, in the same directory, and not one that exists, and none with --remove

Flags

Flag	Kind	Role	Default	Meaning
`--root`	`path`	`root`		resolve PATH relative to this directory and refuse paths outside it
`--if-sha256`	`hex64`	`guard`		the file's current content must hash to this SHA-256, and a retry that already landed then answers changed: false
`--remove`	`bool`	`guard`		remove the file by renaming it to its tombstone .NAME.removed-HASH8 (needs --if-sha256, takes no NEWNAME, and nothing is deleted)
`--dry-run`	`bool`	`guard`		check everything and report planned_actions, exit 9, change nothing
`--format`	`choice:json/text`	`none`	`json`	json for a program, text for a person

Exit codes

Code	Name	Meaning
0	`SUCCESS`	what was asked was done; zero matches is success
1	`GENERAL_ERROR`	the operating system failed mid-operation, or the tool caught a bug in itself
2	`INVALID_ARGS`	the invocation is malformed or names something of the wrong kind; nothing was read
3	`NOT_FOUND`	a named input does not exist
4	`PERMISSION_DENIED`	the operating system refused, or the tool's own confinement did
5	`CONFLICT`	state is not what the caller said it would be
8	`PRECONDITION_FAILED`	the answer is no, or a limit was reached
9	`DRY_RUN`	a --dry-run completed; planned_actions lists what an apply would do

Rules (25)

Match on rule, not on the message. A retry repair is an argv that can be run as it stands, and never widens what the tool may touch.

Rule	Exit	Repair	When
`args.unknown-flag`	2	sometimes	a flag that is not in the tool's table
`args.missing-value`	2	never	a flag that takes a value was given none
`args.bad-value`	2	never	a flag's value is not of the flag's kind
`args.unexpected-value`	2	never	a flag that takes no value was given one
`args.duplicate-flag`	2	never	the same flag was given twice
`args.required-flag`	2	never	a flag the tool needs was not given
`args.missing-operand`	2	never	an operand the tool needs was not given
`args.too-many-operands`	2	never	more operands than the tool takes
`path.empty`	2	never	an empty path
`path.dotdot`	2	sometimes	a path with a `..` component
`path.absolute`	2	always	an absolute path where one relative to --root is wanted
`path.outside-root`	4	never	an absolute path that is not under --root
`path.too-long`	2	never	a path longer than 4096 bytes
`path.symlink`	4	never	a path that runs through a symbolic link, which the tool does not follow
`path.bad-name`	2	never	a new name that is not one plain name in the same directory
`io.not-found`	3	never	a named input does not exist
`io.not-a-directory`	3	never	a path runs through something that is not a directory
`io.is-a-directory`	2	never	a directory where a file is wanted
`io.permission-denied`	4	never	the operating system refused access
`io.read-failed`	1	never	the operating system failed a read
`io.write-failed`	1	never	the operating system failed a write, or a write was short
`precondition.hash-mismatch`	5	never	the file's hash is not the one --if-sha256 named
`conflict.exists`	5	never	--create was given and the path exists
`conflict.locked`	5	never	another writer holds the path's lock
`io.rename-unsupported`	8	never	the filesystem cannot refuse an existing name atomically, so move did not rename

Evidence

each gate is a test in cancho-tools/tests/conformance, run by CI on the commit this binary was built from:

M1 schema conformance
M2 determinism
M3 rule coverage and hint soundness
M4 fault injection
M5 differential against GNU
M6 authority
M7 mutation behaviour
M8 confinement
M9 memory flatness

Agent in the loop: not run: no claim that this tool is more agent-friendly than the incumbents is made (cancho docs/agent-toolbox.md section 7.2).