AGENTS.md@crates/senpi-socket-secret · git:20261026.0afbce4 · 2026-10-26 · sha256 d9637a6fc9d66910
AGENTS.md@crates/senpi-socket-secret git:20261026.0afbce4A
Immutable. This exact content never changes and is served at /api/v1/blob/d9637a6fc9d66910.
# crates/senpi-socket-secret
Rust/N-API Windows adapter for the socket-secret lifecycle of sisyphuslabs/omo-desktop-app#4199: the storage-locality classification and the kernel-session identity that decide when presence-lock and process evidence may count.
## STRUCTURE
```text
src/answers.rs Revision 8.2/8.3 raw query answers -> facts; the exact accepted codes, raw codes kept
src/classify.rs Pure Revision 8 locality rule over the volume facts (unit-tested with fakes)
src/session.rs PID-4 creation FILETIME; `Unverified` never matches anything
src/volume.rs Volume facts read from ONE handle that follows reparse points
src/publish.rs First publication: CREATE_NEW staging with the owner-only DACL, flush, FileRenameInfo ReplaceIfExists=FALSE
src/owner_dacl.rs Protected DACL for the current user, SYSTEM and Administrators
src/lib.rs N-API exports and the `__senpiSocketSecretAbi1` ABI sentinel
tests/native_receipts.rs Native receipts 27 and 28; real Windows only
```
## CONTRACTS
- Locality comes from the kernel driver in the volume's I/O path (`FileFsDriverPathInformation`), never from the reported file-system name alone. Local needs the full conjunction (driver in path, `FILE_REMOTE_DEVICE` clear, no remote-protocol information, neither driver query failed). Any query failure, from either driver query included, is `not_local`; only the exact codes in `src/answers.rs` (design Revisions 8.2/8.3) are answers, and a new code joins that list only with a primary-source meaning and a receipt.
- The classifying handle follows reparse points. Never open it with `FILE_FLAG_OPEN_REPARSE_POINT`.
- `SessionIdentity` has no `PartialEq` on purpose; compare with `same_session`, under which `Unverified` matches nothing.
- Publication never writes the final path, never copies or truncates, and a collision is only ERROR_ALREADY_EXISTS/ERROR_FILE_EXISTS. One handle (`GENERIC_WRITE | DELETE`, share read only) writes, flushes and renames the staging file, and on any outcome but `Published` deletes it through that handle; nothing is reopened or deleted by path. A failed delete is part of the result (`Publication::staging_left_behind`, N-API `stagingLeftBehind { path, windowsError }`), never a log line, and never carries the bytes.
- Prebuilds and the loader are not wired yet; this crate ships no artifact until the packaging change lands.
## VALIDATION
- `cargo test -p senpi-socket-secret --locked` (classifier and session units on every host; the receipts are ignored off Windows).
- Native receipts run only in `ci.yml` `socket-secret-native-windows`, which mounts the WinFsp, Dokany, SMB and VHDX fixtures and runs the ignored cases; its `RECEIPT_` lines are the receipt. Never run them in a VM.