@meddleware/seal-ui 0.0.29 → 0.0.31

package/CHANGELOG.md

@@ -3,6 +3,20 @@
 All notable changes to `@meddleware/seal-ui` are documented here.
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versioning follows [Semantic Versioning](https://semver.org/).
 
+## [0.0.31] - 2026-10-03
+
+### Changed
+
+- seal-client 0.0.15, walrus-client 0.0.25, access-gate-client 0.0.4, ui 0.1.30, design-tokens 0.1.8.
+
+## [0.0.30] - 2026-10-02
+
+- **What you should know before sealing** (always shown): the key-server threshold, that the
+  `seal_policies` package can still be upgraded until it is made immutable (changing access to sealed
+  content), that released keys cannot be taken back, and that labels and gates are public.
+- `@meddleware/seal-client` 0.0.14 (every policy verifies its identity layout; approve PTBs hold only
+  `seal_approve*` calls) and `@meddleware/walrus-client` 0.0.24 (blob reads capped at 100 MiB).
+
 ## [0.0.29] - 2026-10-02
 
 - `@meddleware/access-gate-client` 0.0.3 and `@meddleware/seal-client` 0.0.13: gate reads fail closed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meddleware/seal-ui",
-  "version": "0.0.29",
+  "version": "0.0.31",
   "homepage": "https://docs.meddleware.co.uk/blockchain/sui/sealed-storage/",
   "description": "Standalone Vue 3 SPA for Sealed Storage — client-side Seal encryption + access-gated, decentralised Walrus storage on Sui.",
   "author": "MeddleWare <dev@meddleware.co.uk>",
@@ -44,11 +44,11 @@
     "access": "public"
   },
   "dependencies": {
-    "@meddleware/access-gate-client": "^0.0.3",
-    "@meddleware/design-tokens": "^0.1.7",
-    "@meddleware/seal-client": "^0.0.13",
-    "@meddleware/ui": "^0.1.28",
-    "@meddleware/walrus-client": "^0.0.22",
+    "@meddleware/access-gate-client": "^0.0.4",
+    "@meddleware/design-tokens": "^0.1.8",
+    "@meddleware/seal-client": "^0.0.15",
+    "@meddleware/ui": "^0.1.30",
+    "@meddleware/walrus-client": "^0.0.25",
     "@mysten/sui": "^2.33.1",
     "@mysten/wallet-standard": "^0.21.0",
     "vue": "^3.5.43"
@@ -57,7 +57,7 @@
     "@meddleware/wallet-adapter": ">=0.0.12 <0.2.0"
   },
   "devDependencies": {
-    "@meddleware/wallet-adapter": "^0.0.12",
+    "@meddleware/wallet-adapter": "^0.0.13",
     "@types/node": "~24.12.2",
     "@vitejs/plugin-vue": "^6.0.9",
     "@vue/eslint-config-typescript": "^14.9.0",

package/src/components/SealView.vue

@@ -460,6 +460,22 @@ async function performUnlock(item: SealedContentPointer): Promise<void> {
       who could therefore decrypt it. Do not seal anything you would not share with the operator.
     </p>
 
+    <details class="seal-trust">
+      <summary>What you should know before sealing</summary>
+      <ul>
+        <li>
+          Decryption needs {{ activeConfig.threshold }} of the configured key servers; that many servers together
+          could decrypt, and if fewer are online nobody can.
+        </li>
+        <li>
+          Who may decrypt is decided by the <code>seal_policies</code> package. Until its publisher makes it
+          immutable, an upgrade could change access to content already sealed.
+        </li>
+        <li>Once someone has decrypted an item, losing their pass does not take that access back.</li>
+        <li>Labels and the gate an item is sealed to are public; only the content is encrypted.</li>
+      </ul>
+    </details>
+
     <!-- The tab list and every panel always render (each tab controls a live panel); the wallet
          prompt replaces only a panel's content until a wallet is connected. Panels stay mounted
          (v-show) so each tab keeps its state. -->
@@ -816,4 +832,12 @@ pre.manifest {
 .discovered__blob { word-break: break-all; }
 .status { font-size: 0.85rem; margin-top: 0.5rem; }
 .disclaimer { margin-top: 2rem; }
+
+.seal-trust {
+  margin: 0 0 1rem;
+}
+.seal-trust ul {
+  margin: 0.5rem 0 0;
+  padding-left: 1.25rem;
+}
 </style>