# Direct native sharing

One Instagram or WhatsApp tap prepares the message on the clipboard and immediately opens the system sharing flow. The target app decides destination.

## Sub-features

- Instagram copies the former Post caption, including the link, and sends files only.
- WhatsApp copies its message and sends files plus text when supported, otherwise files only.
- A pending or denied clipboard must not delay sharing; no title is sent.
- Cancel is silent; a native error shows a short error toast without a download.

## How to get to it (user POV)

Expand the share row from a result, or use the already expanded WordPress gallery row, then tap Instagram or WhatsApp.

## Driving it with Playwright

Preconditions: run the skill's doctor and helper with an output directory.

- Click Instagram/WhatsApp: the native-boundary recorder sees `copy` then `share` with transient user activation still active, despite an unresolved clipboard promise.
- Inspect recorded payloads: one real 1080×1920 PNG, no title, Instagram files only, WhatsApp text only in file_text mode. Message includes the selected variant link ending in `atx=1`.
- Cancel: no status toast or implicit download. Native failure: short failure toast, no implicit download.
- Inspect telemetry: only `instagram_feed`/`whatsapp_message` and existing keys/enums; no message/URL.

## Gotchas

Playwright replaces the OS share boundary. It cannot prove app receipt, publishing or native-phone clipboard permissions. The app can only observe share-sheet closure, not delivery.