chore(deps): loosen library ranges and scope pin rule to example

Library package.json may use ranges so consumers aren't blocked on
exact-version updates. Only the example app needs deterministic pins.

- Loosen @craftzdog/react-native-buffer to ^6.1.2
- Loosen react-native-quick-base64 peerDep to >=3.0.0
- Scope exact-pin rule to example app's package.json

Author: boorad

.agents/rules/code-typescript.md

@@ -17,7 +17,8 @@ Applies to `*.ts` and `*.tsx`.
 - Write explicit return types.
 - Keep functions minimal and modular.
 - Use Bun for package management; do not use npm/yarn/pnpm.
-- Pin dependency versions exactly in `package.json`. No caret (`^`) or tilde (`~`) ranges. Applies to `dependencies`, `devDependencies`, and `peerDependencies`. Use the version `bun.lock` resolved.
+- In the example app's `package.json`, pin dependency versions exactly. No caret (`^`) or tilde (`~`) ranges. Applies to `dependencies` and `devDependencies`. Use the version `bun.lock` resolved.
+- Library `package.json` (under `packages/*`) may use ranges (`^`, `>=`) for `dependencies` and `peerDependencies` to allow consumer flexibility.
 - For React, minimize `useEffect`; use named effect functions if unavoidable.
 
 ## Formatting

packages/react-native-quick-crypto/package.json

@@ -106,7 +106,7 @@
     "registry": "https://registry.npmjs.org/"
   },
   "dependencies": {
-    "@craftzdog/react-native-buffer": "6.1.2",
+    "@craftzdog/react-native-buffer": "^6.1.2",
     "events": "3.3.0",
     "readable-stream": "4.7.0",
     "safe-buffer": "^5.2.1",
@@ -131,7 +131,7 @@
     "react": "*",
     "react-native": "*",
     "react-native-nitro-modules": ">=0.31.2",
-    "react-native-quick-base64": "3.0.0",
+    "react-native-quick-base64": ">=3.0.0",
     "expo": ">=48.0.0",
     "expo-build-properties": "*"
   },