shadok-ai 0.17.17 → 0.17.19

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "shadok-ai",
-  "version": "0.17.17",
+  "version": "0.17.19",
   "main": "dist/session.js",
   "scripts": {
     "test": "node --import tsx --test --test-timeout=120000 test/*.ts context/*/test/*.test.mjs",

package/public/index.html

@@ -1564,7 +1564,10 @@
   /* ── Activity block ──────────────────────────────────────
      A run of tool calls between two pieces of assistant text. Folds at three
      levels — output, same-tool run, whole block — each driven by data-folded.
-     Anything containing an error carries .has-err and never folds. */
+     A whole block always folds to its summary line at turn end (even on an
+     error — the count says "· N errors" and the head is flagged .has-err); the
+     errored output and run INSIDE it stay open, so expanding reveals the
+     failure at once rather than hiding it. */
   .turn.activity { max-width: 82%; gap: 0; }
   .act-body, .run-body, .item-out { display: flex; flex-direction: column; }
   [data-folded="true"] > .act-body,
@@ -1611,7 +1614,8 @@
   /* Inside a run the tool name is already in the header — don't repeat it. */
   .act-run:not([data-count="1"]) .item-head .tool { display: none; }
   .item-head .err-flag { flex: none; color: var(--err); }
-  .has-err > .item-head, .has-err > .run-head { border-left-color: var(--err); }
+  /* A folded block hides its runs, so flag the error on the summary line too. */
+  .has-err > .item-head, .has-err > .run-head, .has-err > .act-head { border-left-color: var(--err); }
 
   /* Tool output. */
   .result-body {
@@ -7476,10 +7480,14 @@
     tab.act = null;
   }
 
-  /** Folds every block of the finished turn that saw no error. */
+  /** Folds every block of the finished turn down to its one-line summary.
+      An errored block folds too — the count line still reads "· N errors" and
+      the head carries .has-err, so the failure is flagged, not hidden. Inside,
+      its errored run and output stay unfolded (addToolLine / addResult), so
+      expanding the block lands straight on what failed. */
   function sealTurn(tab) {
     for (const block of tab.turnBlocks || []) {
-      if (!block.el.classList.contains("has-err")) setFolded(block.el, true);
+      setFolded(block.el, true);
     }
     tab.turnBlocks = [];
     tab.pendingCalls?.clear();

package/public/secrets-panel.js

@@ -97,10 +97,16 @@ export function keyGroups(groups) {
   return others.length ? others : list.filter((g) => String(g.id) === MAIN_ID);
 }
 
-/** Groups a secret can be lent to: not its owner, not Main (Main is already read by all). */
+/** Groups a secret can be lent to: not its owner, and nothing already in the
+ *  commons — not Main, and not a PUBLIC group. A public non-Main group is
+ *  "public = commun" (operator decision 2026-11-03): every agent already
+ *  resolves its tier, so offering to share a secret WITH it is as meaningless as
+ *  offering Main. Only restricted/private groups are real sealed vaults to lend
+ *  to. (Server-side resolution is unchanged; this is the UI's offer only.) */
 export function shareTargets(groups, ownerGroupId) {
   return (Array.isArray(groups) ? groups : []).filter(
-    (g) => g && g.id != null && String(g.id) !== MAIN_ID && String(g.id) !== String(ownerGroupId),
+    (g) =>
+      g && g.id != null && String(g.id) !== MAIN_ID && String(g.id) !== String(ownerGroupId) && g.nature !== "public",
   );
 }