shadok-ai 0.2.70 → 0.2.72

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "shadok-ai",
-  "version": "0.2.70",
+  "version": "0.2.72",
   "main": "dist/session.js",
   "scripts": {
     "test": "node --import tsx --test test/*.ts .claude/skills/shadok-ai-agents/test/*.test.mjs",

package/public/index.html

@@ -4243,6 +4243,12 @@
         // ended would come back to life against the *new* session and resend
         // yesterday's text forced. A new session answers no old question.
         retirePaceConfirm(t);
+        // A reload broadcasts a transient "working" (restart in progress) that is
+        // closed by this "ready" — the fresh process is idle again. Drop that
+        // highlight here (setTabMood repaints the favicon too); a real turn
+        // re-asserts it with its own "working". Without this the channel stayed
+        // lit "working" after every reload.
+        if (t.btnEl.classList.contains("working")) setTabMood(t, null);
         setTabState(t, "ready", "ready");
         persistChannels();
         // Reattaching between turns: restore the last turn's time rather than

package/public/tour-steps.js

@@ -41,13 +41,27 @@ export const TOUR_STEPS = [
       "rename it, change its profile, mirror it to Telegram, or close it.",
     target: ".tab.active",
   },
+  {
+    // Deliberately its own stop, against this file's own "group landmarks"
+    // rule: a schedule is not a landmark, it is the reason to open the cockpit
+    // again tomorrow. It used to be the last clause of the toolbar step, sixth
+    // in a list of six — so the one capability no other tool has was the least
+    // prominent thing in the tour, and a first-time visitor never met it.
+    id: "schedule",
+    title: "They can work while you're away",
+    body:
+      "“Schedule”, in that same ⋯ menu, pairs a recurring prompt with a shell check that runs " +
+      "without the model. Silent check → nothing happened, the agent stays asleep at zero " +
+      "tokens. Otherwise it wakes up holding the finding, and tells you here or on Telegram.",
+    target: ".tab.active",
+  },
   {
     id: "tools",
     title: "The toolbar",
     body:
       "🔑 secrets injected into agents that need them · 👤 profiles (role, guardrails, model) · " +
       "Telegram settings · 🔔 notifications · ⋯ for the diff of what an agent changed " +
-      "and to replay this tour. Scheduled prompts live in each agent's own ⋯ menu.",
+      "and to replay this tour.",
     // NOT `.hdr-tools`, which is `display: contents` on desktop and therefore
     // generates no box at all — its rect is all zeros, so the step would have
     // been dropped as "not visible" on the very layout where the toolbar is