@retasc/cli 1.51.0 → 1.52.0

package/CHANGELOG.md

@@ -6,10 +6,28 @@ release commits and the issues they reference.
 
 Dates are the npm publish date. Each entry names the RTSC issue behind it.
 
-## 1.51.0 (2026-09-13)
+## 1.52.0 (2026-09-14)
 
 - TODO: describe this release, and name the RTSC issue behind it.
 
+## 1.51.0 (2026-09-13)
+
+- **RTSC-962** — the proxy now reports git worktrees nobody claimed, so Retasc can see
+  work an agent started without saying so. Retasc fenced the END of work and nothing at
+  the START: `done` rejects on a claim mismatch, `review` demands a handoff, but the
+  server never sees an agent edit a file — so an agent could build thousands of lines
+  against an issue the queue still showed as free, and a second agent would read it as
+  untouched and duplicate or decompose it.
+  The server still reads no git. This process does: a `rtsc-NN/<slug>` worktree with no
+  live claim behind it is reported, and the issue gets a **provisional hold** — visible
+  on `get_issue`, withheld from `next_issue` / `next_batch`, lapsing after an hour.
+  A hold is not a lease and never refuses an explicit `claim_issue`, so the agent that
+  forgot to claim always gets its own work back.
+  Only ACTIVE worktrees count (uncommitted changes, or a commit in the last day), so an
+  abandoned directory cannot park an issue; git runs asynchronously and off the critical
+  path, so the census never delays a tool call; and each unclaimed worktree is announced
+  once, not on every call. A server without the tool simply produces no holds.
+
 ## 1.50.0 (2026-09-11)
 
 - **RTSC-901** — `retasc plan`: which subscription pays for each of your agents, listed

package/dist/commands/bind.js

@@ -513,7 +513,6 @@ export async function completeWorkspaceSetup(args) {
         : (await api.mintKey({
             orgId,
             projectId: projectId,
-            agentName: opts.agent,
             runtime: opts.runtime ?? "claude-code",
             // RTSC-859 — bind is the folder door, so this is a workspace key, and the row
             // says so rather than leaving it to the server's default.

package/dist/commands/plan.js

@@ -4,8 +4,10 @@ import { ask, isInteractive, select } from "../lib/prompt.js";
 // for that: an agent name or a plan label carrying \x1b[ can move the cursor, clear
 // the line and rewrite the rows above it. That matters most HERE, because this
 // command prints a list and then asks a question the reader answers by number, and
-// `mintKey` stores `agentName` and `runtime` verbatim — so any member of the org can
-// choose what lands on an owner's terminal.
+// `mintKey` stores `runtime` verbatim — so any member of the org can choose what lands
+// on an owner's terminal. Since RTSC-958 the NAME is no longer one of those values: it
+// is generated server-side. `clean` still covers it, because every name typed before
+// that change is still stored, and `runtime` is caller-supplied either way.
 import { clean } from "../lib/text.js";
 // Nothing about plans is compiled in here — not the list, and not the two terminal
 // answers either. `cli/src/lib/outcome.ts` records why the CLI cannot import

package/dist/index.js

@@ -146,7 +146,6 @@ program
     .option("--org-id <id>", "Use an existing org id instead of creating one")
     .requiredOption("--project <name>", "Project name")
     .requiredOption("--prefix <PREFIX>", "Project prefix, e.g. XEN")
-    .option("--agent <name>", "Agent member name (default: auto, \"{you}'s {runtime}\")")
     .option("--runtime <runtime>", "Label for this agent in the Dash (claude-code | codex | grok | …). Does NOT choose where MCP config is written — `retasc setup` wires every harness on the machine.", "claude-code")
     .option("-y, --yes", "Don't prompt to confirm replacing an existing binding")
     .option("--no-install", "Don't install `retasc` on this machine; wire the pinned npx launcher instead")
@@ -190,7 +189,6 @@ program
             opts: {
                 project: opts.project,
                 prefix: opts.prefix,
-                agent: opts.agent,
                 runtime: opts.runtime,
                 install: opts.install,
                 yes: opts.yes,
@@ -214,7 +212,6 @@ program
     .option("--project-id <id>", "Use an existing project id")
     .option("--project <name>", "Create a new project with this name (with --prefix)")
     .option("--prefix <PREFIX>", "Prefix for a new project, e.g. ACME")
-    .option("--agent <name>", "Agent member name (default: auto)")
     .option("--runtime <runtime>", "Label for this agent in the Dash (claude-code | codex | grok | …). Does NOT choose where MCP config is written — `retasc setup` wires every harness on the machine.", "claude-code")
     .option("-y, --yes", "Don't prompt to confirm replacing an existing binding")
     // RTSC-523 — decline the global install without a TTY. `bind`/`join` ask when a human
@@ -371,7 +368,6 @@ key
     .command("mint")
     .requiredOption("--org-id <id>")
     .requiredOption("--project-id <id>")
-    .option("--agent <name>", "Agent member name (default: auto, \"{you}'s {runtime}\")")
     .option("--runtime <runtime>", "Label for this agent in the Dash (claude-code | codex | grok | …). Does NOT choose where MCP config is written — `retasc setup` wires every harness on the machine.", "claude-code")
     .option("--name <label>", "Key label")
     // RTSC-859 — say at mint that this key will never have a local runner. Without it
@@ -394,7 +390,6 @@ key
         const res = (await api.mintKey({
             orgId: opts.orgId,
             projectId: opts.projectId,
-            agentName: opts.agent,
             runtime: opts.runtime,
             keyName: opts.name,
             // RTSC-859 — said only when the caller actually said something. `--hosted` is
@@ -553,7 +548,6 @@ program
     .argument("<link>", "The invite link you were given (or just the rtscinv_… code)")
     .option("--no-bind", "Redeem only — don't set this folder up")
     .option("--project-id <id>", "Which project to bind to (skips the picker)")
-    .option("--agent <name>", "Agent member name (default: auto)")
     .option("--runtime <runtime>", "Label for this agent in the Dash (claude-code | codex | grok | …). Does NOT choose where MCP config is written — `retasc setup` wires every harness on the machine.", "claude-code")
     // RTSC-477 — name the way back. `--yes` skips the identity question and must never answer
     // it, so the flag that causes the gap is the right place to say how to close it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@retasc/cli",
-  "version": "1.51.0",
+  "version": "1.52.0",
   "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": {