@ai-matrx/sharing 0.1.10 → 0.1.12

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.1.12
+
+- **`/react` no longer pulls the whole Vault** (build-cost lane, 2026-10-22). The share sheet's secure-link gate imported `createSupabaseIdentity`, `IdentityGate`, `useConfirmed` and `wasCancelled` from the `@ai-matrx/vault` root, so every host that mounts the share sheet (the web app does, in its root providers) compiled every Vault screen and `@zip.js/zip.js`. It now imports them from `@ai-matrx/vault/identity`. Needs `@ai-matrx/vault` with the `/identity` entry (published in the same release train, lower DAG level). Consumer action: none.
+
+## 0.1.11
+
+- **One manual-copy dialog: `useShare` asks the host (2026-10-22, summon adoption X11).** A refused clipboard no longer opens a `ClipboardFallbackDialog` that `useShare` mounted itself; it calls the share sheet's new `manualCopy` port (`configureShareSheetUi({ manualCopy })`, also exported as `manualCopy` from the sheet host), whose default is kit `openClipboardFallback`, i.e. the host's ONE manual-copy dialog (the web app's summon overlay through its kit bridge, `<ClipboardFallbackHost />` anywhere else). `copy`/`share` still resolve `"manual"` and never flip `copied`. `UseShareResult.fallbackDialog` is now always `null` and `@deprecated`; `ShareLinkPanel` no longer renders it. Sharing's bundle no longer imports `ClipboardFallbackDialog`. Test: `src/react/__tests__/manual-copy-goes-through-the-host.test.tsx` (port, kit default, no-own-dialog scan; red on the old `useShare`). **Consumer action:** remove `{fallbackDialog}` from JSX when convenient (it renders nothing now; removal of the field comes later). A host must have a manual-copy host registered (the web app's `ClipboardFallbackBridge`, or `<ClipboardFallbackHost />`), or pass `manualCopy`. matrx-frontend: `features/sharing/hooks/__tests__/useShare.test.tsx` and `scripts/__tests__/clipboard-success-gating.behavior.test.ts` ("useShare copy fallback") assert the old hand-mounted dialog and must be updated (builder-X11.md).
+
 ## 0.1.10
 
 - **The access screens' stand-ins announce themselves (2026-10-22, round 3).** Every default of `configureAccessUi` the host did not replace (`Link`, `router`, `searchParam`, `confirm`, `Textarea`, `renderUserIdentity`, `renderEntityRef`, `renderErrorMenu`, and the quiet app features `entityRegistry`, `recordUnavailableCapture`, `settingRequestActions`, `resourceActionRequests`, `presentOrganizationRefusal`, `overlays`' close) now says so: one console notice per field naming `configureAccessUi({ <field> })`, the field in `data-access-ui-ports` on `<html>`, and `data-access-ui-host="unconfigured"` + `data-access-ui-port` on what the default draws (the same pattern as the share sheet). New test seam `resetAccessUiStandInNotices`. Guard: `src/access/react/env.stand-ins.test.tsx`. **Consumer action:** none; a host that sees a notice supplies the named field.