Document and test share note events

docs/nostr-event-schemas.md

@@ -174,6 +174,22 @@ import { updateWatchHistoryListWithDefaultClient } from "./nostrWatchHistoryFaca
 | Zap request (`NOTE_TYPES.ZAP_REQUEST`) | `9734` | `['p', <recipient pubkey>]` plus optional `['e', <event id>]`, `['a', <coordinate>]`, `['amount', <msats>]`, `['lnurl', <bech32>]`, and `['relays', ...]` for receipt publishing | Optional plaintext zap note |
 | Zap receipt (`NOTE_TYPES.ZAP_RECEIPT`) | `9735` | `['bolt11', <invoice>]`, `['description', <zap request JSON>]`, `['p', <recipient pubkey>]` plus optional `['e', <event id>]` and `['a', <coordinate>]` | Empty content; receipts are published by the recipient's LNURL server |
 
+### Share notes (kind `1`)
+
+Share notes are plain text `kind:1` events generated by the Share modal. The
+`content` field is preserved verbatim (after UTF-8 sanitization) and can contain
+any short message or commentary accompanying the share.
+
+The builder attaches the following tags:
+
+* `['e', <event id>, '', 'mention']` — the shared video’s event id, normalized to
+  lowercase hex.
+* `['p', <pubkey>, '', 'mention']` — the shared video’s author pubkey,
+  normalized to lowercase hex.
+* `['r', <relay url>, <read/write?>]` — optional relay hints. Relay URLs are
+  trimmed, duplicates are removed, and the optional marker is normalized to
+  `read` or `write` when provided.
+
 Subscription lists therefore match the
 [NIP-51 follow-set specification](./nips/51.md#sets) by emitting kind `30000`
 events with the shared `['d','subscriptions']` identifier. Builders continue to