[sean0407]

Summary

hash() builds Argon2 parameters as { m, t, p }. The PHC formatter serializes parameter keys in insertion order, so generated hashes now follow the Argon2 m,t,p sequence.

- { m, p, t }
+ { m, t, p }

Evidence

• Before: Issue #559 reports output with m=65536,p=4,t=3; the PHC string specification requires m,t,p.
• After: Exact-output fixtures use m=65536,t=3,p=4 for the supported hash variants, including the optional data parameter. Static inspection confirms the formatter preserves the parameter object's key order.

Merge Danger

Door: Two-way

Existing hashes remain accepted by the parser; the digest and salt are unchanged.

Blast Radius: Narrow

Only the serialized parameter order changes.

[ranisalt]

You will also need to rebase from master because one-var is pointless but enabled by default; I just disabled it on master.

I can do it easily if you prefer

Edit: doing it myself to bump the version faster

[ranisalt]

Thanks!