process: consumer smoke before moving floating major (v11/v12)

[jleni]

Problem

Same class of risk as Zondax/actions floating v1: moving @v11 (or cutting @v12 and moving it) ships to Kunobi and every other pin without a deliberate smoke.

Proposal

When cutting a new floating major or force-updating v11:

1. Tag first
2. Pilot one consumer (Kunobi) on the explicit tag
3. Then move the float

Mirror the checklist proposed on Zondax/actions.

Acceptance

• Release/pin section in README references pilot-before-float
• Used once on the next major bump

[jleni]

Chose opt-in major: tagged v12 / v12.0.0 at c4ee23c; v11 left frozen. Kunobi can migrate call sites to @v12 when ready (no silent float move).