chore(kit): take 0.2.2, which widens what a safe run promises not to invoke

[rldyourmnd]

chore(kit): take 0.2.2, which widens what a safe run promises not to invoke

forbidden_in_safe_conformance was the one hand-written literal in a kit whose
every other closed set is derived from the protocol source. It listed
apply-operation and launch, while pure_commands derives from the read
commands and lists four — so the two lists did not partition the seven, and the
command left out of both was recover-operation, which mutates.

The behaviour was never wrong: the consumer's runner never invoked it. The
promise was, and a provider reading the kit to learn what a safe run might call
was told a mutating command was fair game.

Nothing here changes. This build reads pure_commands, not the forbidden set,
and a wider forbidden set only removes a call that was never made.

manifest.json moves too, by one line: kit_version 0.2.1 -> 0.2.2, as a label
that tracks bytes must. Only conformance-cases.json changed in content.
Aggregate sha256:24609284… -> sha256:f6e4682d…, verified against the kit's
own SHA256SUMS before being read.

Rendered from NDDev-it-com/setup-systems@3fd4439.

https://claude.ai/code/session_011eFMKoUdWcc7Aw9vtMxH2A