The amnesia eval's absolute-path guard is a two-string check rather than a path detector, so it misses the leak class it was added to close. It looks for the two fixture roots by name only. Both roots are created under one temporary parent, and planting that shared parent string in the bundle leaves the whole lane green: the byte comparison cannot see it, because both runs carry the same string and therefore still agree, and the subtest is not looking for it. The two-path design exists precisely because a run-to-run comparison in one directory cannot see an absolute path embedded in the output, and this guard reintroduces that blindness one level up. It is also the repository's own privacy rule at stake, not only determinism: no absolute local path may enter an artefact.

The amnesia eval's absolute-path guard is a two-string check rather than a path detector, so it misses the leak class it was added to close. It looks for the two fixture roots by name only. Both roots are created under one temporary parent, and planting that shared parent string in the bundle leaves the whole lane green: the byte comparison cannot see it, because both runs carry the same string and therefore still agree, and the subtest is not looking for it. The two-path design exists precisely because a run-to-run comparison in one directory cannot see an absolute path embedded in the output, and this guard reintroduces that blindness one level up. It is also the repository's own privacy rule at stake, not only determinism: no absolute local path may enter an artefact.

Grounds

• pursued: a leak class one level above a two-string list is closed by a detector rather than by a longer list, because the next level up would need another entry; wrong if a legitimate assembly reports a path it does not carry