[asukaminato0721]

Which issue does this PR close?

Closes #6479.

Rationale for this change

Passing pathlib.Path as root raises TypeError in the Python operator constructors because keyword values must be strings.

What changes are included in this PR?

Both Operator and AsyncOperator accept strings and path-like keyword values whose os.fspath() result is a string. The constructor annotations and docstrings describe PathLike[str]. Regression tests exercise synchronous and asynchronous Fs writes and reads with string and Path roots, and reject bool and bytes values.

Validation on Nier: 19 focused constructor, from_config, and from_uri cases against the newly built native extension, plus Rust and Python quality checks and regenerated-stub consistency.

Are there any user-facing changes?

Callers can pass pathlib.Path and other PathLike[str] values directly to either constructor.

Breaking changes

AI Usage Statement

• Harness: Codex desktop. Model: gpt-6.1-sol. Effort: max. Role: constructor implementation, regression tests, and integration.
• Harness: Codex subagent. Model: group/deepseek (underlying model version is not exposed). Effort: max. Role: independent source review and validation on Nier.

[asukaminato0721]

ohh, the new clippy warning, I don't want to fix them in this pr.

[asukaminato0721]

tests/test_operator_construction.py::test_operator_new_with_path PASS

[kingsword09]

ohh, the new clippy warning, I don't want to fix them in this pr.

This has already been resolved and merged into main.

[asukaminato0721]

PyErr { type: <class 'TypeError'>, value: TypeError("'PosixPath' object cannot be converted to 'PyString'"), traceback: None }

Need some fix.