prefixDenied in the reading assembler compares case-sensitively while segmentDenied folds case, and deny.go's own header comment claims the deny binds every path component case-insensitively, so the comment is wrong about the boundary it documents

prefixDenied in the reading assembler compares case-sensitively while segmentDenied folds case, and deny.go's own header comment claims the deny binds every path component case-insensitively, so the comment is wrong about the boundary it documents

Grounds

• pursued: the asymmetry admitted nothing while the walk was the only consumer, but a second consumer now rests on the lexical claim alone, and on a case-insensitive filesystem that claim was all that held. What would show this wrong is a denied prefix whose case genuinely distinguishes two different paths, which would make folding it the error instead.