@retasc/cli 1.33.0 → 1.34.0

package/CHANGELOG.md

@@ -6,6 +6,22 @@ release commits and the issues they reference.
 
 Dates are the npm publish date. Each entry names the RTSC issue behind it.
 
+## 1.34.0 (2026-08-24)
+
+- **RTSC-731** — `bind` stops asking whether you want to join an org you are already in.
+  A teammate given access to a second project was shown "Join Retasc, or start your own
+  workspace?", with the second option one keystroke away from creating a duplicate
+  organization that cannot be deleted from the terminal. Invites that only add projects
+  to a membership you already have are no longer treated as onboarding, and no longer
+  suppress the single-org shortcut. Your agent still hears about them, and
+  `setup_status` now asks about them in its own words, naming the project and the
+  organization so "Retasc the org" and "Retasc the project" can't be confused.
+- **RTSC-731** — the invite questions hand back a value your agent can actually use.
+  Both onboarding questions told the agent to pass the chosen answer to `accept_invite`'s
+  `org` flag, then offered "join" as that answer — so an agent doing exactly what it was
+  told got "no invite to join is waiting for you", while one that ignored the instruction
+  and read the prose succeeded. The accept option now carries the organization itself.
+
 ## 1.33.0 (2026-08-23)
 
 - **RTSC-722** — the setup questions arrive as a matrix your agent can actually render.

package/dist/commands/bind.js

@@ -728,7 +728,17 @@ export async function bindAction(opts) {
     if (!orgId) {
         const me = (await api.me());
         const orgs = me.orgs ?? [];
-        const pendingInvites = me.pendingInvites ?? [];
+        // RTSC-731 — JOIN invites only. RTSC-730 widened what `me.pendingInvites` returns to
+        // include invites that merely add projects to a membership somebody already has, and
+        // this block asks "join this org, or start your own workspace?" — a question whose
+        // premise is false for an existing member, and whose second option creates a SECOND
+        // org on the billing rail with no CLI-callable delete (RTSC-297). A widening also
+        // must not suppress the single-org shortcut below.
+        //
+        // Widenings are NOT dropped from the product, only from THIS question: the notice
+        // rider still relays them, `whoami` still lists them, `setup_status` asks about them
+        // with its own wording, and `accept_invite` still takes them.
+        const pendingInvites = (me.pendingInvites ?? []).filter((i) => !i.widensExisting);
         if (isInteractive()) {
             const chosen = await pick("Select an org", orgs, (o) => `${o.name} (${o.slug})`);
             if (chosen) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@retasc/cli",
-  "version": "1.33.0",
+  "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.",
   "type": "module",
   "bin": {