35 of 100 passing agent solutions break when you change only the order the requirements arrived in.

SpecPath (arXiv 2608.09799) holds repository, final contract, verifier, agent system, and execution budget constant, varying only the revision history by which a spec became final. Same end state, different path there. Thirty-five percent failed on at least one contract-equivalent history, and aggregate accuracy across paths looked nearly identical, which means path sensitivity is completely invisible to standard benchmarking. Agents are partly following surface cues from how a request evolved. Evaluate against messy multi-turn requirement histories, not the tidy ticket you'd write in hindsight.