9ns: --name and /mnt/9p/ mounts, qid.path as inode number, interrupts as Tflush

2026-09-20T02:55:47Z

- --name NAME (default derived from the transport: socket basename, tcp-IP-PORT, spawned command, fdN) mounts at /mnt/9p/; --mount still overrides. ensureMountpoint walks down and creates missing components, shadowing the deepest unwritable ancestor. NINE_MOUNT is the only exported variable. - The inode number reported to the kernel is the 9P qid.path for every node, root included; a server handing qid.path 1 to a file (Pardes /self) no longer collides with the root. - FUSE_INTERRUPT for the request in flight becomes Tflush; a blocked read returns EINTR when the server answers the flush, chunked transfers return short counts, other requests arriving meanwhile are stashed and served next. Servers ignoring Tflush still block until they answer. - 9ns-test now covers nine/bridge/fuse; new adv_bridge_interrupt suite (28); 9ns-itest grows to 88 checks. Co-Authored-By: Claude Fable 5.1

Rename programs: 9player -> 9ns, introspect -> 9proc, app -> web (9web)

2026-09-20T02:28:22Z

Directories, binaries, build options (-D9ns, -D9proc), step names, module name (9proc), thread and fs names, env var NINEPLAYER_MOUNT -> NINE_MOUNT, docs and test scripts. Browser assets move to web/static. Co-Authored-By: Claude Fable 5.1

cloud9.git/9ns/test/adv_bridge_hostile.py, branch main

9ns: --name and /mnt/9p/ mounts, qid.path as inode number, interrupts as Tflush

Rename programs: 9player -> 9ns, introspect -> 9proc, app -> web (9web)