@integrity-labs/agt-cli 0.28.775 → 0.28.777

package/dist/mcp/index.js

@@ -46672,7 +46672,7 @@ ${lines}` }
 );
 server.tool(
   "rule_add",
-  'Turn a repeated instruction into a STANDING RULE that applies on every turn. Use when someone asks for the same thing more than once, or phrases it as a standing instruction ("always...", "every time...", "from now on..."). Propose it in plain language first and get a yes \u2014 never create one silently, and never make the person learn the word "skill" or "rule" to get it. Keep it SHORT: a rule is resident in your instructions on every single request, so if it needs more than a sentence it is really a skill (skill_create), which costs nothing until the task comes up. If you are already at the limit, pass replace_id with the id of the rule this one supersedes (rule_list shows the ids) \u2014 and tell the person what you dropped, in the same message. There is deliberately no way to remove a rule without adding one in its place: a rule that quietly stops applying is worse than one that was never made, because nobody notices.',
+  'Turn a repeated instruction into a STANDING RULE that applies on every turn. Use when someone asks for the same thing more than once, or phrases it as a standing instruction ("always...", "every time...", "from now on..."). Propose it in plain language first and get a yes \u2014 never create one silently, and never make the person learn the word "skill" or "rule" to get it. Keep it SHORT: a rule is resident in your instructions on every single request, so if it needs more than a sentence it is really a skill (skill_create), which costs nothing until the task comes up. If you are already at the limit, pass replace_id with the id of the rule this one supersedes (rule_list shows the ids) \u2014 and tell the person what you dropped, in the same message. Do NOT use replace_id merely to get rid of a rule you no longer want - that swaps in a rule nobody asked for. If a rule is simply WRONG, use rule_remove, which requires a reason. Replacing is for "I want this instead"; removing is for "this should never have been made". Either way the person MUST be told what stopped applying, in the same message: a rule that quietly stops applying is worse than one that was never made, because nobody notices.',
   {
     text: external_exports.string().describe("The rule, in the person's own words where possible. One sentence. It applies on every turn, so write it as a standing instruction rather than a task."),
     replace_id: external_exports.string().optional().describe("The id of an existing rule this one replaces (from rule_list). Required once you are at the limit. The person MUST be told which rule was dropped, in the same reply.")
@@ -46693,6 +46693,40 @@ server.tool(
     return { content: [{ type: "text", text: said }] };
   }
 );
+server.tool(
+  "rule_remove",
+  "Retire a standing rule that is WRONG - factually incorrect, harmful, or written for a workflow that has since changed. Use this instead of rule_add+replace_id when there is no replacement rule you actually want: swapping in a rule nobody asked for to evict a bad one leaves two problems instead of one, both resident on every turn. A wrong rule is not inert, it steers every single request until it is gone. You MUST tell the person which rule stopped applying, in the same reply - that obligation is the whole reason removal is allowed at all. `reason` is required: a removal with nothing recorded is the silent disappearance this design exists to prevent. Removing your last rule is fine; zero rules is a normal state.",
+  {
+    rule_id: external_exports.string().describe("The id of the rule to retire, from rule_list."),
+    // Trimmed and length-checked HERE as well as in planAgentRuleRemove.
+    // Not redundant: the schema refusal reaches the agent immediately and
+    // without a round trip, whereas the server check is the one that actually
+    // guarantees the invariant for every caller. The server check stays because
+    // it also carries the credential-shape refusal, which a schema cannot do.
+    reason: external_exports.string().trim().min(1, "A reason is required \u2014 a rule that disappears with nothing recorded is what this design prevents.").describe('Why it is being removed, in one short phrase ("factually wrong", "workflow changed", "superseded by policy"). Required and non-blank. It is recorded in the audit trail so the removal stays answerable after the rule is gone.')
+  },
+  async (params) => {
+    const data = await apiPost("/host/agent-rules/remove", {
+      agent_id: AGT_AGENT_ID,
+      rule_id: params.rule_id,
+      reason: params.reason
+    });
+    if (!data.ok) {
+      return {
+        content: [{ type: "text", text: data.message ?? "Could not remove that rule." }],
+        isError: true
+      };
+    }
+    return {
+      content: [
+        {
+          type: "text",
+          text: `Removed the rule: "${data.removed?.text}". It no longer applies. TELL THE PERSON this rule stopped applying, in this same reply - do not let it disappear silently.`
+        }
+      ]
+    };
+  }
+);
 server.tool(
   "knowledge_add",
   'Save a new durable fact or learning to the knowledge base. Use when the user explicitly asks you to save/remember something, or when you discover information that will be useful on future runs (e.g. a tenant id, an API key name, a company policy). Do NOT use for tasks (use kanban_add) or trivial one-off answers. Defaults to TEAM scope; pass scope:"org" only when the user asks for organization/company-wide knowledge (visible to every team in the org). Returns the new entry id so you can target it with knowledge_update / knowledge_delete.',
@@ -47207,11 +47241,19 @@ var LOCAL_TOOL_NAMES = /* @__PURE__ */ new Set([
   "kanban_reopen",
   // ENG-9375: the READ path over a teammate's board (counts only).
   "kanban_peek",
-  // ENG-9789: per-agent standing rules. No rule_remove by design — see the
-  // registration below; an agent may only displace a rule by naming it while
-  // adding another.
+  // ENG-9789: per-agent standing rules. The ADD path is swap-only — an agent
+  // may not displace a rule except by naming it while adding another, so a full
+  // list can never be resolved by a silent delete.
+  //
+  // ENG-9860 added `rule_remove` as a separate exit for a rule that turned out
+  // to be WRONG, which swap-only left with no move that was not also bad
+  // (invent a replacement nobody wants, or leave a known-wrong instruction
+  // resident on every turn). It does NOT relax the above: removal is its own
+  // call, requires a non-blank reason, and obliges the agent to say what
+  // stopped applying in the same reply.
   "rule_list",
   "rule_add",
+  "rule_remove",
   // ENG-6953: agent + people directory lookup (always registered locally).
   "directory_lookup",
   "status_standup",

package/dist/{persistent-session-UEQ7A6QP.js → persistent-session-CGIB77UQ.js}

@@ -49,8 +49,8 @@ import {
   writeDirectChatSessionState,
   writeEgressAllowlist,
   writePersistentClaudeWrapper
-} from "./chunk-VCAWCBMT.js";
-import "./chunk-E33WDZNL.js";
+} from "./chunk-NRMBKDER.js";
+import "./chunk-N6DU2RYO.js";
 import "./chunk-XWVM4KPK.js";
 export {
   EGRESS_BASELINE_DOMAINS,
@@ -104,4 +104,4 @@ export {
   writeEgressAllowlist,
   writePersistentClaudeWrapper
 };
-//# sourceMappingURL=persistent-session-UEQ7A6QP.js.map
+//# sourceMappingURL=persistent-session-CGIB77UQ.js.map

package/dist/{responsiveness-probe-CKU7IQK6.js → responsiveness-probe-YINXZH3S.js}

@@ -1,7 +1,7 @@
 import {
   paneLogPath
-} from "./chunk-VCAWCBMT.js";
-import "./chunk-E33WDZNL.js";
+} from "./chunk-NRMBKDER.js";
+import "./chunk-N6DU2RYO.js";
 import "./chunk-XWVM4KPK.js";
 
 // src/lib/responsiveness-probe.ts
@@ -745,4 +745,4 @@ export {
   readAndResetSlackReplyBindingClassifications,
   readAndResetSlackReplyTargetClassifications
 };
-//# sourceMappingURL=responsiveness-probe-CKU7IQK6.js.map
+//# sourceMappingURL=responsiveness-probe-YINXZH3S.js.map

package/dist/{session-auth-dead-ZP5YGGW3.js → session-auth-dead-OZBNHFPN.js}

@@ -1,6 +1,6 @@
 import {
   sessionTranscriptDir
-} from "./chunk-E33WDZNL.js";
+} from "./chunk-N6DU2RYO.js";
 
 // src/lib/session-auth-dead.ts
 import { closeSync, openSync, readSync, readdirSync, statSync } from "fs";
@@ -203,4 +203,4 @@ export {
   decideSessionAuthState,
   probeSessionAuth
 };
-//# sourceMappingURL=session-auth-dead-ZP5YGGW3.js.map
+//# sourceMappingURL=session-auth-dead-OZBNHFPN.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@integrity-labs/agt-cli",
-  "version": "0.28.775",
+  "version": "0.28.777",
   "description": "Augmented Team CLI — agent provisioning and management",
   "type": "module",
   "engines": {