sealkeep 0.6.2 → 0.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -3,6 +3,27 @@
3
3
  Notable changes, by published version. Sealkeep is pre-1.0: minor versions
4
4
  may change behavior, and say so here when they do.
5
5
 
6
+ ## 0.7.0 — 2026-08-20
7
+
8
+ Two reviews — does each section deserve to exist, and can a person finish the
9
+ job it promises — and the answers, applied.
10
+
11
+ - **Setup no longer argues for the unrecoverable mistake.** The password path
12
+ said skipping the recovery phrase was "fine". Your password opens the vault on
13
+ that machine only; the screen now says so, names the day it matters, and shows
14
+ the 24 words as what survives it.
15
+ - The account panel leads with the Recovery key card instead of burying it ninth
16
+ of eleven, merges Plan into Your package (they answered the same question),
17
+ makes the package tiers actually start a change instead of looking clickable
18
+ and doing nothing, warns "Delete forever?" with the stake named, puts
19
+ connecting a machine above the list of machines, and stops calling an
20
+ account-wide upload rule "what leaves this machine".
21
+ - Revoked machines fold into one line — they are kept as the record, never
22
+ deleted, but no longer bury the machines that can actually write.
23
+ - `sealkeep doctor` warns when a routing rule pins a project this machine has
24
+ never sealed. The panel cannot check that — project names never reach us —
25
+ so the machine that knows does.
26
+
6
27
  ## 0.6.2 — 2026-08-20
7
28
 
8
29
  - New: `sealkeep projects` lists the project names this vault knows, with how
@@ -216,6 +216,10 @@
216
216
  .acct-nav{display:flex;gap:.35rem;flex-wrap:wrap;position:sticky;top:0;z-index:5;background:var(--paper);padding:.65rem 0;margin:.4rem 0 .2rem;border-bottom:1px solid var(--rule)}
217
217
  .acct-nav a{font-family:var(--mono);font-size:.74rem;color:var(--soft);text-decoration:none;border:1px solid var(--rule);border-radius:999px;padding:.4rem .85rem;min-height:26px;display:inline-flex;align-items:center}
218
218
  .acct-nav a:hover{color:var(--ink);border-color:var(--ink)}
219
+ #d-retired details{margin:.5rem 0 .2rem}
220
+ #d-retired summary{font-family:var(--mono);font-size:.76rem;color:var(--soft);cursor:pointer;padding:.35rem 0}
221
+ #d-retired summary:hover{color:var(--ink)}
222
+ #d-retired .lines li{opacity:.75}
219
223
  .acct-hero{font-family:var(--mono);font-size:1.55rem;font-weight:700;letter-spacing:-.03em;margin:.9rem 0 0;line-height:1.3}
220
224
  h1.acct-hero:empty{display:none}
221
225
  .ruleslist{margin:.3rem 0 .9rem;padding-left:1.1rem}
@@ -611,6 +615,12 @@ sealkeep open 08424eb6… ./session.jsonl \
611
615
  <span class="saved" id="a-verify-msg" role="status" aria-live="polite"></span>
612
616
  </div>
613
617
 
618
+ <div class="card" id="c-recovery"><span id="anchor-recovery"></span>
619
+ <span class="eyebrow">Recovery key</span>
620
+ <h2 id="e-head">Loading…</h2>
621
+ <p id="e-text"></p>
622
+ </div>
623
+
614
624
  <div class="card" id="anchor-storage">
615
625
  <span class="eyebrow">Storage</span>
616
626
  <div id="a-store-free" style="display:none">
@@ -662,7 +672,9 @@ sealkeep open 08424eb6… ./session.jsonl \
662
672
  <span class="eyebrow">Machines</span>
663
673
  <h2>Connected machines</h2>
664
674
  <p>Each connected machine signs its own uploads. Revoking one stops it writing here; the archives it already stored are untouched.</p>
675
+ <div id="pair-top"></div>
665
676
  <ul class="lines" id="d-list"></ul>
677
+ <div id="d-retired"></div>
666
678
  <p class="empty" id="d-msg">Loading…</p>
667
679
 
668
680
  <!-- One pairing block exists on the page. It leads the panel while no
@@ -700,44 +712,36 @@ sealkeep open 08424eb6… ./session.jsonl \
700
712
  <p class="msg" id="s-msg">Loading…</p>
701
713
  <div id="s-wrap" style="display:none;overflow-x:auto">
702
714
  <table>
703
- <thead><tr><th>Archive</th><th>Contents</th><th>State</th><th>Added</th><th></th></tr></thead>
715
+ <thead><tr><th>Archive</th><th>Size</th><th>State</th><th>Added</th><th></th></tr></thead>
704
716
  <tbody id="s-body"></tbody>
705
717
  </table>
706
718
  <p class="msg" id="s-foot"></p>
707
719
  </div>
708
720
  </div>
709
721
 
710
- <div class="card" id="c-plan"><span id="anchor-plan"></span>
711
- <span class="eyebrow">Plan</span>
712
- <div id="a-plan-free" style="display:none">
713
- <h2>Free — your bucket, your bill</h2>
714
- <p>Unlimited archives with the same encryption. You supply the storage credentials and pay your provider directly.</p>
715
- <p class="empty">Want us to run storage instead? Pricing is in Your package, below. Write to <span id="a-sales">hello@spala.ai</span> from this address and we will switch it on.</p>
716
- </div>
717
- <div id="a-plan-paid" style="display:none">
718
- <h2>Managed storage</h2>
719
- <p>We run the bucket and meter what you store. We still hold no key that opens any of it — the only difference from your own bucket is who pays the storage bill and who can delete it.</p>
720
- <div class="kv" style="margin-top:1rem">
721
- <div><span class="k">Subscription</span><b id="a-sub-state">—</b></div>
722
- <div><span class="k">Renews</span><b id="a-sub-end">—</b></div>
723
- <div><span class="k">Billed through</span><b id="a-sub-prov">—</b></div>
724
- </div>
725
- <p class="empty" id="a-sub-note"></p>
726
- </div>
727
- </div>
722
+
728
723
 
729
724
  <div class="card" id="a-pack-card">
725
+ <span id="anchor-plan"></span>
730
726
  <span class="eyebrow">Your package</span>
731
727
  <h2 id="a-pack-current">—</h2>
732
728
  <p class="msg" id="a-pack-context" style="margin:0 0 .8rem"></p>
733
729
  <div class="packrow" id="a-packs"></div>
730
+ <p class="empty" id="a-plan-free-note"></p>
734
731
  <p class="empty" id="a-pack-alt">Not storing with us? Your own bucket is free with the same encryption, and Pro Lite keeps key escrow and machine sign-in with no metered storage.</p>
732
+ <div class="kv" id="a-sub-facts" style="margin-top:1rem">
733
+ <div><span class="k">Subscription</span><b id="a-sub-state">—</b></div>
734
+ <div><span class="k">Renews</span><b id="a-sub-end">—</b></div>
735
+ <div><span class="k">Billed through</span><b id="a-sub-prov">—</b></div>
736
+ </div>
737
+ <p class="empty" id="a-sub-note"></p>
735
738
  <p class="why" id="a-pack-note">Changing your package is handled by hand today. Email hello@spala.ai from this address and we will move you within one business day — your archives keep uploading throughout.</p>
736
739
  </div>
737
740
 
738
741
  <div class="card">
739
- <span class="eyebrow">What leaves this machine</span>
742
+ <span class="eyebrow">What gets uploaded</span>
740
743
  <h2>Your upload rules</h2>
744
+ <p class="msg" style="margin:.1rem 0 .6rem">Saved to your account — every machine you connect follows these, the same way routing rules do.</p>
741
745
  <p>Everything you do not choose here stays local and is never uploaded.</p>
742
746
  <p class="empty" id="r-note" style="margin-bottom:.9rem">Enforced on your machine, before a session is read or sealed. Anything held back is never uploaded, so this is a rule about what leaves — not a filter we apply after it arrives.</p>
743
747
  <div class="rules">
@@ -764,11 +768,7 @@ sealkeep open 08424eb6… ./session.jsonl \
764
768
  </div>
765
769
  </div>
766
770
 
767
- <div class="card" id="c-recovery"><span id="anchor-recovery"></span>
768
- <span class="eyebrow">Recovery key</span>
769
- <h2 id="e-head">Loading…</h2>
770
- <p id="e-text"></p>
771
- </div>
771
+
772
772
 
773
773
  <div class="card">
774
774
  <span class="eyebrow">Activity</span>
@@ -1051,7 +1051,7 @@ sealkeep open 08424eb6… ./session.jsonl \
1051
1051
  $("a-name").value = user.label || "";
1052
1052
  $("a-plan").textContent = paid ? "Managed storage" : "Free";
1053
1053
  $("a-plan").className = "chip" + (paid ? " pro" : "");
1054
- $("a-plan").onclick = () => goTo($("c-plan"));
1054
+ $("a-plan").onclick = () => goTo($("anchor-plan"));
1055
1055
  $("a-who").textContent = [
1056
1056
  user.email,
1057
1057
  "joined " + day(user.created_at),
@@ -1069,8 +1069,13 @@ sealkeep open 08424eb6… ./session.jsonl \
1069
1069
  lastPaid = paid;
1070
1070
  applyStorageView();
1071
1071
  on("anchor-archives", paid); on("nav-archives", paid);
1072
- on("a-plan-free", !paid);
1073
- on("a-plan-paid", paid);
1072
+ // One card carries billing now. A free account is told what managed
1073
+ // storage would give it; a paying one is told the state of what it bought.
1074
+ $("a-plan-free-note").textContent = paid
1075
+ ? ""
1076
+ : "You are on your own storage: unlimited archives, same encryption, your provider's bill. Managed storage means we run the bucket and meter what you store — we still hold no key that opens any of it.";
1077
+ on("a-sub-facts", paid);
1078
+ on("a-plan-free-note", !paid);
1074
1079
 
1075
1080
  if (paid) {
1076
1081
  const quota = Number(user.quota_bytes) || 0, used = Number(user.used_bytes) || 0;
@@ -1117,7 +1122,37 @@ sealkeep open 08424eb6… ./session.jsonl \
1117
1122
  return deviceCount;
1118
1123
  }
1119
1124
  $("d-msg").textContent = "";
1120
- for (const d of devices) {
1125
+ // Revocation never deletes a machine — the row stays as the record that
1126
+ // it once had access. On an account that has re-paired a few times that
1127
+ // buries the two machines actually running under a wall of history: 29
1128
+ // rows, 1666 px, nearly two screens, all looking alike. Active machines
1129
+ // are the answer to "what can write to my account right now"; the rest
1130
+ // fold away, counted and reachable, deleted by nobody.
1131
+ const active = devices.filter((d) => d.state !== "revoked");
1132
+ const retired = devices.filter((d) => d.state === "revoked");
1133
+ const foldHost = $("d-retired");
1134
+ foldHost.replaceChildren();
1135
+ if (retired.length) {
1136
+ const fold = document.createElement("details");
1137
+ const summary = document.createElement("summary");
1138
+ summary.textContent = `${retired.length} revoked machine${retired.length === 1 ? "" : "s"} — kept as the record, none can write`;
1139
+ const inner = document.createElement("ul");
1140
+ inner.className = "lines";
1141
+ for (const d of retired) {
1142
+ const li = document.createElement("li");
1143
+ const name = document.createElement("span");
1144
+ name.className = "grow";
1145
+ name.textContent = d.label || "Unnamed machine";
1146
+ const when = document.createElement("span");
1147
+ when.className = "when";
1148
+ when.textContent = "revoked " + ago(d.revoked_at);
1149
+ li.append(name, when);
1150
+ inner.append(li);
1151
+ }
1152
+ fold.append(summary, inner);
1153
+ foldHost.append(fold);
1154
+ }
1155
+ for (const d of active) {
1121
1156
  const li = document.createElement("li");
1122
1157
  const name = document.createElement("span");
1123
1158
  name.className = "grow";
@@ -1138,7 +1173,13 @@ sealkeep open 08424eb6… ./session.jsonl \
1138
1173
  // Two-step, like archive deletion: revoking locks a machine out of
1139
1174
  // its own backups, so a stray click must not do it.
1140
1175
  if (btn.dataset.armed !== "yes") {
1141
- btn.dataset.armed = "yes"; btn.textContent = "Confirm";
1176
+ btn.dataset.armed = "yes";
1177
+ // The local dashboard escalates to "Destroy forever?" when it can
1178
+ // prove a copy is the last one. This page cannot see the customer's
1179
+ // disk, so it must not claim either way — it names the stake and
1180
+ // lets them decide.
1181
+ btn.textContent = "Delete forever?";
1182
+ btn.title = "If your machine already reclaimed the source, this is the only copy";
1142
1183
  setTimeout(() => {
1143
1184
  if (btn.dataset.armed === "yes") { btn.dataset.armed = "no"; btn.textContent = "Revoke"; }
1144
1185
  }, 4000);
@@ -1489,7 +1530,7 @@ sealkeep open 08424eb6… ./session.jsonl \
1489
1530
  : paidPlan ? "Sealkeep cloud" : "the bucket each machine is configured with");
1490
1531
  const nothingYet = devices === 0 && Number(user.used_bytes) === 0;
1491
1532
  on("a-firstrun", nothingYet);
1492
- $(nothingYet ? "pair-home-first" : "pair-home-more").append($("pair"));
1533
+ $(nothingYet ? "pair-home-first" : "pair-top").append($("pair"));
1493
1534
  $("pair-side").textContent = nothingYet ? "Your pairing code" : "Pairing code";
1494
1535
  if (devices === 0)
1495
1536
  $("d-msg").textContent = nothingYet
@@ -1742,8 +1783,16 @@ sealkeep open 08424eb6… ./session.jsonl \
1742
1783
  const host = $("a-packs");
1743
1784
  while (host.firstChild) host.removeChild(host.firstChild);
1744
1785
  for (const pack of PACKAGES.filter((p) => p.managed)) {
1745
- const chip = document.createElement("span");
1786
+ const chip = document.createElement(pack.id === current ? "span" : "a");
1746
1787
  chip.className = "packchip" + (pack.id === current ? " now" : "");
1788
+ if (pack.id !== current) {
1789
+ // It looked like a picker and did nothing when clicked. Changing a
1790
+ // package is handled by a person today, so the chip starts that
1791
+ // message rather than pretending to be a checkout.
1792
+ chip.href = "mailto:hello@spala.ai?subject=" + encodeURIComponent(`Move me to ${pack.name}`)
1793
+ + "&body=" + encodeURIComponent(`Please move my account to ${pack.name}${pack.managed ? ` ($${pack.monthly} a month)` : ""}.`);
1794
+ chip.title = `Ask us to move you to ${pack.name}`;
1795
+ }
1747
1796
  const name = document.createElement("b"); name.textContent = pack.name;
1748
1797
  const price = document.createElement("span"); price.textContent = `$${pack.monthly}/mo`;
1749
1798
  chip.append(name, price);
@@ -169,6 +169,44 @@ export async function runDoctor(dataDir, env = process.env) {
169
169
  }
170
170
  }
171
171
  catch { /* coverage is advisory; a broken sidecar must not fail doctor */ }
172
+ // A routing rule can pin a project to a destination, and the account panel
173
+ // cannot check the name: project names never reach the cloud. So a typo is
174
+ // saved happily and silently routes nothing, forever. This machine knows the
175
+ // real names, so it is the one that can say.
176
+ try {
177
+ const { resolveTargets } = await import("./storage-targets.js");
178
+ const targets = await resolveTargets(dataDir);
179
+ const pinned = [...new Set(targets.flatMap((target) => target.projects ?? []))];
180
+ if (pinned.length > 0) {
181
+ const { listArchives } = await import("./vault.js");
182
+ const { claudeProjectFromPath, codexProjectFromRollout } = await import("./adapters.js");
183
+ const records = await listArchives(dataDir).catch(() => []);
184
+ const known = new Set();
185
+ for (const record of records) {
186
+ try {
187
+ const name = record.source.agent === "claude"
188
+ ? claudeProjectFromPath(record.source.path).project
189
+ : record.source.agent === "codex"
190
+ ? (await codexProjectFromRollout(record.source.path, record.createdAt)).project
191
+ : null;
192
+ if (name)
193
+ known.add(name);
194
+ }
195
+ catch { /* a project we cannot read is not evidence of a bad pin */ }
196
+ }
197
+ const unmatched = pinned.filter((name) => !known.has(name));
198
+ if (unmatched.length === 0) {
199
+ checks.push({ name: "routing-pins", status: "pass", detail: `${pinned.length} pinned project${pinned.length === 1 ? "" : "s"} match sessions on this machine.` });
200
+ }
201
+ else {
202
+ checks.push({
203
+ name: "routing-pins", status: "warn",
204
+ detail: `${unmatched.length === pinned.length ? "No" : unmatched.length} pinned project${unmatched.length === 1 ? "" : "s"} match anything sealed here: ${unmatched.slice(0, 3).join(", ")}. Those rules route nothing. Run \`sealkeep projects\` for the names this vault actually knows${known.size ? `, such as ${[...known].slice(0, 2).join(", ")}` : ""}.`
205
+ });
206
+ }
207
+ }
208
+ }
209
+ catch { /* routing rules are advisory here; never fail doctor over them */ }
172
210
  // Where the daemon actually looks: an explicit env var, or the phrase the
173
211
  // wizard put in this machine's keystore. This used to test only the env var,
174
212
  // so a machine set up correctly through the window — phrase in the keystore,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "sealkeep",
3
- "version": "0.6.2",
3
+ "version": "0.7.0",
4
4
  "type": "module",
5
5
  "description": "Sealkeep by SPALA AI \u2014 your AI coding-agent history, sealed, searchable, and shared across your machines.",
6
6
  "license": "SEE LICENSE IN LICENSE",
package/web/setup.html CHANGED
@@ -267,12 +267,12 @@
267
267
  <p>It unlocks with your password on this machine. If you ever lose the password, the phrase below is the only other way in — which is a good reason to spend a minute on it now.</p>
268
268
  </div>
269
269
  <details class="panel pad explain" id="phrase-fold">
270
- <summary>Prefer a recovery phrase too?</summary>
270
+ <summary>Show the 24 words that survive this machine</summary>
271
271
  <p id="fold-note"></p>
272
272
  <ol class="phrase" id="fold-phrase-words"></ol>
273
273
  </details>
274
274
  <div class="wizfoot">
275
- <p class="note">Skipping the phrase is fine — your password already opens this vault.</p>
275
+ <p class="note warn"><b>Your password opens this vault on this machine only.</b> It is kept in this machine's keystore — it does not travel. If this machine is lost or wiped, the 24 words above are the only thing that opens the archives, and nobody, including us, can recreate them. Take them now, or accept that this vault dies with this machine.</p>
276
276
  <div class="actions"><button type="button" class="action primary" id="finish-password">Finish setup</button></div>
277
277
  </div>
278
278
  </div>
package/web/style.css CHANGED
@@ -674,6 +674,16 @@ nav.steps .step.locked.current:hover { background: var(--ink-2); color: #fff; }
674
674
  .callout h3 { margin: 0; }
675
675
  .callout h3 + p { margin-top: -6px; }
676
676
  .callout.warn { border-left: 3px solid var(--alert); }
677
+ /* A note that carries a consequence reads like one. Used where setup asks
678
+ whether to keep the 24 words: the copy there used to call skipping them
679
+ "fine", which is true until the machine is lost and then permanently false. */
680
+ .note.warn {
681
+ border-left: 3px solid var(--alert);
682
+ padding: 10px 12px;
683
+ background: color-mix(in srgb, var(--alert) 7%, transparent);
684
+ color: var(--ink);
685
+ }
686
+ .note.warn b { color: var(--alert); }
677
687
  .callout.warn p { color: var(--text); }
678
688
  ul.plain { margin: 0; padding-left: 19px; display: grid; gap: 8px; color: var(--text-2); max-width: 72ch; }
679
689
  ul.plain b { color: var(--text); }