v0.1.2

norotate is refused again, and the version number now distinguishes the two artifacts.

What changed

norotate was added to the recognised parameter set on 2026-08-21 because it appears in the vendor's proxy generator. It has been taken back out.

Probed from a VPS on 2026-08-26 against the gateway, three ways, each with a negative control carrying a name nobody could have implemented and a positive control on filter:

probe	norotate=true	both controls
junk value	200	200
no sid, 6 draws	6 distinct exits of 6	6 distinct of 6
fixed sid + ttl=1m, sampled at 0/78/157 s	3 distinct of 3	3 distinct of 3

Rotation is what norotate claims to change, and it does not change it. The gateway answers 200 and drops the setting, which is the exact failure this package exists to catch, so the parameter belongs on the refused side.

values and its parser, added in the same commit, stay. Nothing measured since bears on them.

speed has the same provenance and has never been probed for its effect. It stays, with a note in the provider definition saying so. Removing it on inference would be this same mistake pointing the other way.

Why 0.1.2 and not a patch to 0.1.1

Between 2026-08-21 and today, what was published as 0.1.1 and what was on main disagreed about norotate while both reported __version__ == "0.1.1". Nothing outside the repository could tell them apart. This release ends that.

Full Changelog: v0.1.1...v0.1.2