docs(nip46): correct stale coordinate format in KDoc

Two doc comments still described the pre-namespacing coordinate
`nip46:<clientPubKey>`; the actual key is `nip46:<signerPubKey>:<clientPubKey>`.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015FHr2mu5SiHwYNR7evYUuF

amethyst/src/main/java/com/vitorpamplona/amethyst/model/nip46Signer/Nip46SignerState.kt

@@ -59,7 +59,7 @@ import kotlinx.coroutines.launch
  *
  * Every request is gated by [Nip46PermissionAuthorizer], i.e. the same
  * "Connected Apps" trust ledger that governs napplets and web origins: a remote
- * client is a connected app under the coordinate `nip46:<clientPubKey>`.
+ * client is a connected app under the coordinate `nip46:<signerPubKey>:<clientPubKey>`.
  *
  * The listener restarts whenever the enabled flag or the relay set changes
  * ([collectLatest] cancels the previous run), so editing inbox relays or toggling

commons/src/commonMain/kotlin/com/vitorpamplona/amethyst/commons/connectedApps/nip46/Nip46PermissionAuthorizer.kt

@@ -46,8 +46,10 @@ import com.vitorpamplona.quartz.utils.TimeUtils
  * [NostrOpDecision]) and surfaced on the same management screen.
  *
  * A NIP-46 client is identified by its transport pubkey, mapped to the ledger
- * coordinate `nip46:<clientPubKey>` (see [coordinateFor]) so it lives in its
- * own namespace next to `browser:<origin>` and napplet `<author>:<id>` keys.
+ * coordinate `nip46:<signerPubKey>:<clientPubKey>` (see [coordinateFor]) so it
+ * lives in its own namespace next to `browser:<origin>` and napplet
+ * `<author>:<id>` keys, and so the same client paired with two accounts on one
+ * device gets independent grants.
  *
  * Authorization mirrors the napplet path:
  *  - each signing/encryption/decryption request maps to a [NostrSignerOp]