Add copy-devices support across client execution paths

[oferchen]

Summary

• thread the copy-devices flag through CLI parsing, client configuration, fallback invocation, and local copy execution so device nodes can be copied as regular files when requested
• extend engine executors and options to honour copy-devices when traversing directories, symlink targets, and queued sources, and add tests for the new behaviour
• document the new CLI support in the feature matrix

Testing

• cargo test --workspace --all-features (fails: golden version output mismatch between upstream-captured fixture and current banner)

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

rsync/crates/engine/src/local_copy/executor/special.rs

Lines 684 to 698 in 60ddf6b

	if is_device(&target_type) {
	if !context.devices_enabled() {
	context.record_skipped_non_regular(record_path.as_deref());
	context.register_progress();
	return Ok(());
	}
	copy_device(
	context,
	source,
	destination,
	&target_metadata,
	metadata_options,
	relative,
	)?;
	return Ok(());

Dereferenced device symlinks ignore --copy-devices

The new copy‑devices flag is respected when a device node is encountered directly in directory traversal or as an explicit source, but the unsafe‑symlink path still requires devices_enabled() and always calls copy_device. When a user runs oc-rsync --copy-devices --copy-unsafe-links link-to-device dest without --devices, the code at this branch treats the target as a special file, records a skipped non‑regular entry, and never copies the device’s contents as a regular file. This makes --copy-devices ineffective for symlinked devices and diverges from the behaviour for direct device paths. The branch should mirror the directory/sources logic by checking copy_devices_as_files_enabled() and delegating to copy_file when set before falling back to copy_device.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".