Merge pull request #734 from cipherstash/fix/init-placeholder-eql-v3

fix(cli): scaffold EQL v3 encryption client from stash init

Author: tobyhede

.changeset/init-placeholder-eql-v3.md

@@ -0,0 +1,19 @@
+---
+'stash': patch
+---
+
+`stash init` now scaffolds an EQL **v3** encryption client, matching the EQL v3
+database it installs.
+
+The placeholder client (`DRIZZLE_PLACEHOLDER` / `GENERIC_PLACEHOLDER`) and the
+introspection-driven client generator previously emitted EQL v2 authoring
+patterns — `Encryption({ schemas })`, `encryptedColumn(...).equality().freeTextSearch()`,
+and `encryptedType<T>('x', { equality: true })`. Since init installs a v3
+database, this handed the customer's coding agent v2 guidance against a v3
+schema (follow-up to #732 / #705).
+
+Scaffolds now teach the v3 surface: `EncryptionV3` from `@cipherstash/stack/v3`,
+the concrete-domain `types.*` factories (`types.TextSearch`, `types.IntegerOrd`,
+`types.Text`, `types.Json`, …), and the `@cipherstash/stack-drizzle/v3` entry
+(`extractEncryptionSchemaV3`) for Drizzle. The `encryptionClient` export shape
+and the empty-schema "no schemas yet" error path are unchanged.