@retasc/cli 1.34.0 → 1.34.1

package/CHANGELOG.md

@@ -6,6 +6,19 @@ release commits and the issues they reference.
 
 Dates are the npm publish date. Each entry names the RTSC issue behind it.
 
+## 1.34.1 (2026-08-25)
+
+- **RTSC-741** — a rejected write no longer costs you the lease. The watchdog decided
+  when to stop heartbeating an issue by looking at the request you sent, never at whether
+  the server accepted it. So a `save_issue` that came back an error still dropped the
+  issue from the heartbeat map while you were still holding it. Nothing renewed it after
+  that, it ran out its half hour, and the reclaimer handed your work to another agent
+  while you were in the middle of it, with no sign anything had gone wrong. Every drop
+  now requires the call to have actually succeeded. The trigger is the new server-side
+  rule that moving an issue into `review` must carry a handoff: a rejection on that write
+  is the expected first attempt for any agent that has not learned the field yet, so a
+  rare edge became a common one.
+
 ## 1.34.0 (2026-08-24)
 
 - **RTSC-731** — `bind` stops asking whether you want to join an org you are already in.

package/dist/lib/watchdog.js

@@ -18,6 +18,9 @@ function idOf(issue) {
  * - next_batch(claim) response → { issues:[{id, claimToken}] } → register each
  * - release_issue request → drop that issue's lease
  * - save_issue(status: done|canceled) request → drop that issue's lease
+ *
+ * Every drop requires the call to have SUCCEEDED (RTSC-741) — a rejected write leaves
+ * the lease in place, because the agent still holds the issue server-side.
  */
 export function applyObservation(leases, o) {
     const r = o.result;
@@ -37,7 +40,24 @@ export function applyObservation(leases, o) {
         }
     }
     // Releases / terminal status drop the lease — the issue is named in the REQUEST.
-    const id = typeof o.args?.identifier === "string" ? o.args.identifier : undefined;
+    //
+    // RTSC-741: but ONLY if the call actually succeeded. These branches read the REQUEST
+    // shape, so a REJECTED write used to drop the lease of an issue the agent still holds
+    // server-side. Nothing then renews it, it runs out the bare 30-minute TTL, and the
+    // reclaimer hands the issue to someone else while the agent is still working on it.
+    // `shouldReapOnClose` below already applies exactly this check for the same reason.
+    //
+    // It matters now because RTSC-741 made `save_issue status:"review"` REJECTABLE
+    // (HANDOFF_REQUIRED): a rejected review write is the expected first attempt for any
+    // agent that hasn't learned the field yet, and for every already-running session whose
+    // cached tool schema predates the deploy. What was a rare edge is briefly the norm.
+    //
+    // Erring toward KEEPING the lease is the safe direction, and the module already relies
+    // on it: a lease held after the server released it just fails its next heartbeat and
+    // self-heals (see the send-back note below), whereas a lease dropped too early is
+    // silent and costs the agent its work.
+    const succeeded = !!o.result && !isToolError(o.result);
+    const id = succeeded && typeof o.args?.identifier === "string" ? o.args.identifier : undefined;
     if (id && o.toolName === "release_issue")
         leases.delete(id);
     // RTSC-321: moving to `review` (RTSC-257) hands the lease back server-side (the
@@ -49,7 +69,7 @@ export function applyObservation(leases, o) {
     // failed-heartbeat path instead.)
     if (id && o.toolName === "save_issue" && o.args?.status === "review")
         leases.delete(id);
-    const closeId = terminalCloseId(o);
+    const closeId = succeeded ? terminalCloseId(o) : undefined;
     if (closeId)
         leases.delete(closeId);
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@retasc/cli",
-  "version": "1.34.0",
-  "description": "Retasc CLI \u2014 the issue tracker AI agents pull work from. Sign in with GitHub or Google, create projects, mint agent API keys, and wire your agent to the Retasc MCP server in one command.",
+  "version": "1.34.1",
+  "description": "Retasc CLI — the issue tracker AI agents pull work from. Sign in with GitHub or Google, create projects, mint agent API keys, and wire your agent to the Retasc MCP server in one command.",
   "type": "module",
   "bin": {
     "retasc": "dist/index.js"