docs(claude-md): correct stale 'v2.2+ Tamarin/ProVerif bridge' entry

Investigation found both backends already fully shipped inside the 105
prover count:
- provers/tamarin.rs: 596 LoC, 5 tests, .spthy generation + output parsing
  + interactive tactics (add_rule/add_lemma/add_restriction/add_builtin),
  shells out to tamarin-prover
- provers/proverif.rs: 800 LoC, 8 tests, .pv generation + output parsing,
  shells out to proverif

Both are wired end-to-end: ProverKind variants (mod.rs:168-169), factory
dispatch (mod.rs:1259-1260), FFI codes (ffi/mod.rs 44/45), Idris2
ProverKindInjectivity proof. STATE.md 2026-04-19 confirms 'fully wired'.

Real remaining gaps are Wave-3 tracked: no .spthy/.pv corpus fixtures,
no CI provisioning for upstream binaries.

Author: claude

CLAUDE.md

@@ -137,7 +137,13 @@ The v1.5 trust hardening added:
 **Next (v2.2+)**:
 - Train GNN/Transformer on larger corpus (Flux.jl)
 - Chapel → Rust C FFI bridge
-- Tamarin/ProVerif bridge
+
+Note: Tamarin (`provers/tamarin.rs`, 596 LoC, 5 tests) and ProVerif
+(`provers/proverif.rs`, 800 LoC, 8 tests) are already shipped as real
+backends inside the 105 prover count — an earlier "v2.2+ Tamarin/ProVerif
+bridge" entry was stale doc. Corpus fixtures (`.spthy` / `.pv` samples)
+and CI provisioning of `tamarin-prover` / `proverif` binaries are tracked
+as Wave-3 work in `docs/handover/TODO.md`.
 
 ## Useful Commands