cfctl v1.1.2

Unsigned release; integrity is by checksum. Verify against SHA256SUMS before use.

Changes

• Worker script secret put now succeeds. Cloudflare answers a successful put with 201 Created, while its OpenAPI declares only 200. The derived contract pinned 200, so every real put crossed the boundary, created the secret, and then failed as an unknown outcome requiring rectification — the secret existed and cfctl could not confirm it. A second defect in the same path made the verifier report failure while all eight of its sub-checks passed, because the apply status was echoed as a value rather than compared. Statuses are now reported as accepted=<bool>, and the pin covers the statuses Cloudflare actually returns — 202 is still refused (#89).

Found by exercising the capability against a real account rather than trusting its tests; the fixtures asserted the documented status, not the sent one.

Verification

cargo xtask verify exit 0. Live-proven end to end: scratch Worker deployed through governed wrangler.deploy, secret put verified, three secrets deleted with not-found verification, and a sentinel value planted in each put confirmed absent from every plan, evidence file, and envelope.