Enginex0
79e4fe905e
The asymmetric and symmetric result dumps wrote a single fixed filename (teesim-gen-mode-asym.bin / -sym.bin), so each forge overwrote the previous one and only the final reply survived a capture -- which is why a tester's zip showed one app's good chain while the failing chain was already gone. Tag both dumps with uid and tx, matching the request dumps, so every forged chain is retained and correlatable with its request.