feat(call): opt-in verified gift-wrap selection before encrypted initialization

README.md

@@ -122,6 +122,63 @@ cvmi call weather tool:weather.get_current city=Lisbon
 cvmi call weather tool:weather.get_current city=Lisbon --config ./custom.cvmi.json
 ```
 
+For a server that requires ephemeral encrypted gift wrapping, select it explicitly:
+
+```bash
+cvmi call weather tool:weather.get_current city=Lisbon --encryption-mode required --gift-wrap-mode ephemeral
+```
+
+`--gift-wrap-mode <optional|persistent|ephemeral>` sets the SDK's gift-wrap policy for
+the connection, including its first request. `persistent` uses kind 1059;
+`ephemeral` uses kind 21059. `optional` lets the SDK choose based on peer
+capabilities. Omitting the setting preserves the existing SDK default. This
+setting does not change encryption requirements or signature verification.
+
+For direct calls, the setting resolves in this order: the CLI flag,
+`servers.<alias>.giftWrapMode`, then `use.giftWrapMode`. JSON configuration retains
+the custom > project > global precedence described above. For example:
+
+```json
+{
+  "servers": {
+    "weather": {
+      "pubkey": "npub1...",
+      "encryption": "required",
+      "giftWrapMode": "ephemeral"
+    }
+  }
+}
+```
+
+Use the server's documented policy to select a mode. An announcement advertising
+ephemeral support does not necessarily mean that persistent wrapping is rejected.
+
+### Verified prehandshake selection (opt-in)
+
+```sh
+cvmi call <discovered-server-key> --relays wss://your-configured-relay --encryption-mode required --auto-gift-wrap
+```
+
+This opt-in verifies current kind 11316 metadata for the selected public key before
+sending the first MCP message. Signed presence-only ephemeral support selects 21059;
+a current encryption-only announcement selects 1059. Support is not a requirement
+or a statement about the operator's identity. Display-only legacy tag/prose values
+are never automatic trust inputs. `use.autoGiftWrap` or a server alias may enable it;
+CLI > alias > use precedence applies. `--no-auto-gift-wrap` opts out. Any effective
+explicit `giftWrapMode`, including `optional`, overrides automatic selection.
+Omitting both settings leaves the SDK default unchanged.
+
+All explicitly selected relays must complete their bounded query. Missing, forged,
+expired, more-than-one-day-old, future-dated or conflicting latest metadata stops
+before MCP; it does not trigger a persistent/plaintext retry. This is a conservative
+local freshness policy, not a universal server renewal requirement. Three relays,
+64 candidate events, 64 KiB/event, 1 MiB received frames/relay and four seconds bound
+each lookup. WebSocket frame assembly precedes the application byte check; this is
+not a network/kernel memory or billing quota. No additional URLs in metadata are
+followed, no relay AUTH is signed, and no credential or admission is created.
+Encryption must already be `required`; the option never changes encryption or payment
+policy. A later transport timeout is not proof the server is down or uses a wrong mode.
+
 ### `cvmi cn`
 
 [`cvmi cn`](src/cn/index.ts) is fully integrated into `cvmi` (formerly `ctxcn`). It allows you to generate type-safe TypeScript clients directly from a Nostr MCP server.