Vault100 v2.1.0 — the fine ladder (111 key-turning options)

v2.1.0 — the fine ladder: 111 key-turning options

Requested: "add 100+ options" to the Argon2id key-turning dropdown. Delivered —
111 choices:

• The 3 named presets: standard (64 MiB × 3) · paranoid (256 MiB × 4) ·
  max (auto-tuned & device-verified, from v2.0.4)
• The fine ladder — 108 notches: 18 memory tiers (16 → 1024 MiB) × 6 turning
  counts (1–6), rendered as a graded optgroup, weakest → heaviest
  (№ 001 · 16 MiB × 1 turn … № 108 · 1024 MiB × 6 turns)

Interop by design: ladder choices ride as raw KDF parameters, which Vault100
has always stamped into the vault header — so a vault sealed at any notch opens
byte-exactly in the CLI and desktop app (and vice versa, the proven property).
Pick heavy notches with sense: they cost time and memory on every open, and
small devices may refuse the top tiers (the clerk reports honestly if so).

Verified

Check	Result
Headless-Chromium E2E: 111 options sorted & rendered	✅
Ladder notch 128 MiB × 4: encrypt → download → decrypt	✅ byte-exact
max + cascade still green, zero console errors	✅
CLI: vault100 info reads web-made ladder vault (128 MiB × 4, p=4)	✅
CLI: vault100 decrypt restores it	✅ byte-exact, original filename preserved

No Python engine changes; the 49-test suite and all prior interop proofs stand.