docs: correct design doc — snaps-utils resolution bump was required

Author: Jeremy Tsang

docs/plans/2026-06-30-stellar-keyring-v2-design.md

@@ -24,7 +24,19 @@ Already in place (no change needed):
   `withCatchAndThrowSnapError` (`handlers/keyring/keyring.ts:115`), so every
   method already surfaces a `SnapError`.
 
-**No dependency bumps and no `platformVersion` change are required.**
+**No `platformVersion` change is required.** One dependency-resolution bump was
+required during implementation, discovered only when the manifest change was
+attempted: `endowment:keyring.capabilities` (the manifest field itself) is
+validated by `@metamask/snaps-utils`, and that field's validation was only
+added in `snaps-utils@12.2.0` — the version resolved by the existing
+`snaps-cli@^8.4.0` range was `12.1.0`, which rejects the field as an unknown
+key. Fixed with an exact (non-caret) `resolutions` pin,
+`"@metamask/snaps-utils": "12.2.0"`, plus a `yarn dedupe` pass. A caret range
+(`^12.2.0`) was tried first and rejected: it resolves to `12.2.1`, which bumps
+`@metamask/permission-controller` to a `13.x` major and drags in an unrelated
+`@ethersproject/*`/`controller-utils@12.x` subtree. The exact pin avoids that
+— `snaps-utils@12.2.0` itself only needs `permission-controller@^12.3.0`, the
+same major line already in the lockfile.
 
 ## Remaining delta (this ticket)