@retasc/cli 1.41.0 → 1.41.1

package/CHANGELOG.md

@@ -6,6 +6,14 @@ release commits and the issues they reference.
 
 Dates are the npm publish date. Each entry names the RTSC issue behind it.
 
+## 1.41.1 (2026-09-04)
+
+- **RTSC-812** — no runtime change. Two comments in `cli/src` said project deletion did
+  not exist: `bind` called an unwanted empty project something "that cannot be deleted
+  (org-granularity delete only)", and the `import` confirm said "there is no per-project
+  delete". An owner can delete a project from the Dash now, so both were wrong, and the
+  import one sat on the last screen before an irreversible write.
+
 ## 1.41.0 (2026-09-04)
 
 - **RTSC-825** — every workspace now carries the name of the folder it is bound to. The
@@ -13,7 +21,7 @@ Dates are the npm publish date. Each entry names the RTSC issue behind it.
   `retasc bind` sends it when the key is minted, and the watchdog proxy re-sends it at
   every session start, so a folder bound before this existed is named the next time an
   agent runs there. Only the folder's own name travels, never the path above it, and it
-  is the folder the BINDING names — a session opened in a subdirectory still reports the
+  is the folder the BINDING names, so a session opened in a subdirectory still reports the
   bound folder rather than renaming the row to whatever directory it started in. The
   Dash shows it as `workspace` on the Agents page and on the Connect page, and shows
   nothing at all where a workspace has not reported one; a key retired before this

package/dist/commands/bind.js

@@ -427,7 +427,7 @@ export async function completeWorkspaceSetup(args) {
             // act: it is one of the ways a first project comes into existence. The CLI used to
             // ask only "New project name:", so someone arriving from Jira had to invent a project
             // they did not want, run `retasc import` afterwards, and leave an empty one behind
-            // that cannot be deleted (org-granularity delete only).
+            // (deletable by an owner from the Dash since RTSC-812, but still a chore).
             const made = await firstProject(orgId, org);
             projectId = made.projectId;
             prefix = made.prefix;

package/dist/commands/import.js

@@ -413,8 +413,8 @@ export async function runImportFlow(opts) {
     }
     // --- confirm ---------------------------------------------------------------
     // Named in full before anything is written. An import creates a project's worth of
-    // issues and mints a placeholder per source author, and there is no per-project delete —
-    // undoing a mistake means an org-level cleanup.
+    // issues and mints a placeholder per source author; undoing a mistake means an owner
+    // deleting the whole project from the Dash (RTSC-812), placeholders and all.
     console.log(`\nAbout to import ${clean(target.name)} from ${clean(src.label)} into org ${orgLabel},\n` +
         `as a new project. Issues, comments and their authors come across.`);
     // RTSC-526 — the second run is the dangerous one, and the terminal is where a command

package/package.json

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