The unit and parity suites are good but cover only internally-consistent happy paths. Nothing exercises: shebang files (finding 1 & shebang divergence), malformed offsets (finding 2), overlay symlinks / dir-rename-with-children / exec-bit / lookup-in-opaque-dir (finding 3), adversarial NFS filenames (finding 4), mount-path-longer-than-placeholder, Windows entry-point layout, clobbering, dual-CD codesign, or any of the three adapters at unit level. The e2e nushell harness is rigorous (I had an agent verify its pass/fail detection empirically) but validates behavior, not these boundaries. Adding cases in these gaps is where the real hardening is.
The unit and parity suites are good but cover only internally-consistent happy paths. Nothing exercises: shebang files (finding 1 & shebang divergence), malformed offsets (finding 2), overlay symlinks / dir-rename-with-children / exec-bit / lookup-in-opaque-dir (finding 3), adversarial NFS filenames (finding 4), mount-path-longer-than-placeholder, Windows entry-point layout, clobbering, dual-CD codesign, or any of the three adapters at unit level. The e2e nushell harness is rigorous (I had an agent verify its pass/fail detection empirically) but validates behavior, not these boundaries. Adding cases in these gaps is where the real hardening is.