chat-recall 0.5.26 → 0.5.28

package/dist/watch.js

@@ -18883,7 +18883,7 @@ function pruneLedgerTargets(configuredServers) {
     return 0;
   }
   const rows = names.reduce((n, s) => n + Object.keys(orphans[s]).length, 0);
-  console.error(`[sync] ledger: parked ${rows} row(s) for ${names.length} server(s) no longer configured (${names.join(", ")}) in ${side}`);
+  console.error(`[sync] tidied local bookkeeping: ${rows} already-synced marker(s) for ${names.length} server(s) you no longer sync to (${names.join(", ")}) moved to ${side}. Nothing was uploaded there; the file is kept so logging back in re-ships nothing.`);
   persistNow(data);
   return names.length;
 }
@@ -19213,7 +19213,7 @@ var init_http = __esm({
       CLI_VERSION = JSON.parse(readFileSync33(new URL("../package.json", import.meta.url), "utf-8")).version || CLI_VERSION;
     } catch {
       try {
-        if (true) CLI_VERSION = "0.5.26";
+        if (true) CLI_VERSION = "0.5.28";
       } catch {
       }
     }
@@ -19721,7 +19721,7 @@ var init_telemetry = __esm({
     init_sync_client();
     cliVersion = () => {
       try {
-        return true ? "0.5.26" : "dev";
+        return true ? "0.5.28" : "dev";
       } catch {
         return "dev";
       }
@@ -21586,7 +21586,7 @@ var init_sync_client = __esm({
       ownVersion = JSON.parse(readFileSync37(join44(dir, "../package.json"), "utf-8")).version || ownVersion;
     } catch {
       try {
-        if (true) ownVersion = "0.5.26";
+        if (true) ownVersion = "0.5.28";
       } catch {
       }
     }
@@ -24374,7 +24374,7 @@ try {
   ownVersion2 = JSON.parse(readFileSync41(join50(dir, "../package.json"), "utf-8")).version || ownVersion2;
 } catch {
   try {
-    if (true) ownVersion2 = "0.5.26";
+    if (true) ownVersion2 = "0.5.28";
   } catch {
   }
 }
@@ -24718,7 +24718,7 @@ async function runCollectorMigration(opts) {
 init_sync_ledger();
 init_collector_health();
 import { existsSync as existsSync50, readFileSync as readFileSync46 } from "fs";
-var CLI_VERSION3 = true ? "0.5.26" : "0.0.0";
+var CLI_VERSION3 = true ? "0.5.28" : "0.0.0";
 var DEBOUNCE_MS = 5e3;
 var CLAUDE_DIR = claudeBackend.projectsDir();
 var PLANS_DIR = claudeBackend.plansDir();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chat-recall",
-  "version": "0.5.26",
+  "version": "0.5.28",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/munhq/chat-recall.git"

package/skills/chat-recall/SKILL.md

@@ -32,6 +32,7 @@ and apply the test in `chat-recall-memory` before calling one:
 `recall_kg_add`, `recall_kg_invalidate`, `recall_decision_record`,
 `recall_diary_write`, `recall_set`, `recall_task_create`, `recall_task_update`,
 `recall_task_comment`,
+`recall_task_policy`,
 `recall_security_dismiss`, `recall_rename_session`, `recall_regenerate_summary`,
 `recall_reclassify`, `recall_index`, `recall_code_index`.
 
@@ -85,7 +86,7 @@ CLAUDE.md rule is additive and reversible, so take it; ask first before setting
 **Findings, ranked** — `recall_claude_suggestions` (every finding that becomes an agent-instruction change — the CLAUDE.md rules and skill installs — merged across account scope and every indexed project) and `recall_improvements` (everything else, most urgent first; `create_tasks: true` opens one team task per item). They split the same engines, so an item never appears in both. Neither needs the codeindex binary: without it you still get the account-level half.
 **What changed** — `recall_edits_timeline` (cross-tool edits), `recall_diff` (per-session diffs), `recall_commits` (did it actually land), `recall_markers` (where a session went sideways).
 **Durable memory / KG** — `recall_kg_query` / `recall_kg_add` / `recall_kg_invalidate` / `recall_kg_timeline` / `recall_kg_stats`, `recall_decision_record`, `recall_diary_write` / `recall_diary_read`, `recall_set` / `recall_get`.
-**Team** — `recall_tasks` (the shared task board), `recall_task_create`, `recall_task_update` (status, assignee, linked session; task ids look like `t_…`; when you start work on a task, set it `in_progress` and pass your session id as `linked_session_id` so the board can verify the work shipped), `recall_task_comment` (leave a progress note on a card), `recall_team_activity` (per-teammate × per-project rollup), `recall_shares` (which projects are shared — private by default, nothing is visible to teammates until shared).
+**Team** — `recall_tasks` (the shared task board), `recall_task_create`, `recall_task_update` (status, assignee, linked session; task ids look like `t_…`; when you start work on a task, set it `in_progress` and pass your session id as `linked_session_id` so the board can verify the work shipped), `recall_task_comment` (leave a progress note on a card), `recall_task_policy` (read or change WHAT the board files — severity floor, open-card ceiling, cards per run, categories, and the projects that never file at all via `exclude_project` — reach for that one when the user says "do not put work on my board for this repo", e.g. a client's codebase they keep separate; call it with no arguments to read, and reach for it when the user says "only security", "high and critical for now", or asks why a full board has stopped filing), `recall_team_activity` (per-teammate × per-project rollup), `recall_shares` (which projects are shared — private by default, nothing is visible to teammates until shared).
 **Toolkit sync across tools and devices** — `recall_toolkit_status` (which MCP servers, skills, commands and agents exist, on which tool, on which device — and which of them can be installed elsewhere at all), `recall_toolkit_sync` (queue an install: everything or one type, every device or one machine, or fan a machine's own artifacts across its own tools). Reach for these on "set up my other laptop", "get my MCPs everywhere", "why does this tool not have my skill".
 
 **Security** — `recall_security_summary` (leaked secrets that still need action — start here for "did I paste a key somewhere"), `recall_security_session` (findings for one session), `recall_security_dismiss` (mark rotated / false positive — do this only when the user confirms which), `recall_security_rules` (tenant detection rules; also tests a regex).