docs: update paykit paths for v0 protocol

Author: JOHN

docs/BITKIT_PAYKIT_INTEGRATION_MASTERGUIDE.md

@@ -1337,8 +1337,14 @@ Reference implementations:
 
 #### 8.2.1 Publishing a payment request (sender flow)
 
-Where it is implemented (iOS): `DirectoryService.publishPaymentRequest(_:)` stores at:
-- `/pub/paykit.app/v0/requests/<requestId>` on the sender’s Pubky storage.
+Where it is implemented:
+- iOS: `DirectoryService.publishPaymentRequest(_:)`
+- Android: `DirectoryService.publishPaymentRequest(...)`
+
+Storage path (on the **sender's** Pubky storage):
+- `/pub/paykit.app/v0/requests/{recipient_scope}/{requestId}`
+
+Where `{recipient_scope}` = `hex(sha256(normalize(recipient_pubkey_z32)))`.
 
 End-to-end steps:
 
@@ -1349,8 +1355,10 @@ End-to-end steps:
    - Preferred: `PubkyRingBridge.requestPaykitSetup()` (session + noise keys)
 3. Import/restore the session into the Pubky SDK layer.
 4. Configure `DirectoryService` with the session.
-5. Publish the request JSON to `/pub/paykit.app/v0/requests/<requestId>`.
-6. Generate a receiver deep link:
+5. Compute `recipient_scope` from the recipient's pubkey.
+6. Encrypt request JSON with Sealed Blob v1 (recipient's Noise public key).
+7. Publish the envelope to `/pub/paykit.app/v0/requests/{recipient_scope}/{requestId}`.
+8. Generate a receiver deep link:
    - `bitkit://payment-request?requestId=<requestId>&from=<senderPubkey>`
 
 #### 8.2.2 Receiving + processing a payment request deep link (receiver flow)

docs/COMPONENT_ROLES.md

@@ -170,11 +170,15 @@ User taps "Connect with Pubky-ring"
 
 ### Paykit Data (paykit.app namespace)
 
-| Path | Purpose | Auth Required |
-|------|---------|---------------|
-| `/pub/paykit.app/v0/endpoints/{method}.json` | Payment endpoint | Write: Yes, Read: No |
-| `/pub/paykit.app/v0/requests/{requestId}` | Payment request | Write: Yes, Read: No |
-| `/pub/paykit.app/v0/subscriptions/{id}` | Subscription data | Write: Yes, Read: No |
+| Path | Purpose | Storage Location | Auth Required |
+|------|---------|------------------|---------------|
+| `/pub/paykit.app/v0/{method}.json` | Payment endpoint | Payee's storage | Write: Yes, Read: No |
+| `/pub/paykit.app/v0/noise` | Noise endpoint | Payee's storage | Write: Yes, Read: No |
+| `/pub/paykit.app/v0/requests/{recipient_scope}/{requestId}` | Payment request | Sender's storage | Write: Yes, Read: No |
+| `/pub/paykit.app/v0/subscriptions/proposals/{subscriber_scope}/{proposalId}` | Subscription proposal | Provider's storage | Write: Yes, Read: No |
+| `/pub/paykit.app/v0/handoff/{requestId}` | Secure handoff | Ring user's storage | Write: Yes, Read: No |
+
+**Note**: `{recipient_scope}` and `{subscriber_scope}` are SHA-256 hashes of the normalized pubkey (not the raw pubkey).
 
 ---
 

docs/SUBSCRIPTIONS_LOCAL_TESTING.md

@@ -58,7 +58,9 @@ adb shell am broadcast -a android.intent.action.RUN \
 **Expected Result:**
 - Toast shows "Proposal sent successfully"
 - The proposal is published to the Pubky directory at:
-  `/pub/paykit.app/v0/subscriptions/proposals/{recipientPubkey}/{proposalId}`
+  `/pub/paykit.app/v0/subscriptions/proposals/{subscriber_scope}/{proposalId}`
+
+  Where `{subscriber_scope}` = `hex(sha256(normalize(subscriber_pubkey_z32)))`.
 
 ### Scenario 2: Discover and Accept Proposal
 
@@ -76,7 +78,7 @@ adb shell am broadcast -a android.intent.action.RUN \
 
 **Expected Result:**
 - Subscription appears in "My Subscriptions" tab
-- Proposal is removed from Proposals tab
+- Proposal is hidden from Proposals tab (local-only; not deleted from provider storage)
 - If autopay enabled: AutoPayRule is created
 
 ### Scenario 3: Manage Subscription
@@ -113,18 +115,25 @@ adb shell am broadcast -a android.intent.action.RUN \
 
 ## Verifying Directory Operations
 
-Use the Pubky homeserver API to verify proposals are correctly stored:
+Use the Pubky homeserver API to verify proposals are correctly stored.
+
+**Important**: Proposals are stored on the **provider's** storage (the sender of the proposal), not the subscriber's.
 
 ```bash
-# List proposals for a recipient
-curl "https://homeserver.pubky.app/pub/paykit.app/v0/subscriptions/proposals/{recipientPubkey}/" \
-  -H "pubky-host: {recipientPubkey}"
+# Compute subscriber_scope (in practice, use the same hashing as the app):
+# subscriber_scope = hex(sha256(normalize(subscriber_pubkey_z32)))
+
+# List proposals addressed to a subscriber (query provider's storage)
+curl "https://homeserver.pubky.app/pub/paykit.app/v0/subscriptions/proposals/{subscriber_scope}/" \
+  -H "pubky-host: {providerPubkey}"
 
 # Fetch a specific proposal
-curl "https://homeserver.pubky.app/pub/paykit.app/v0/subscriptions/proposals/{recipientPubkey}/{proposalId}" \
-  -H "pubky-host: {recipientPubkey}"
+curl "https://homeserver.pubky.app/pub/paykit.app/v0/subscriptions/proposals/{subscriber_scope}/{proposalId}" \
+  -H "pubky-host: {providerPubkey}"
 ```
 
+**Note**: Proposals are encrypted with Sealed Blob v1. The response will be an encrypted envelope JSON.
+
 ## Troubleshooting
 
 ### Proposals Not Appearing