@retasc/cli 1.15.0 → 1.16.0

package/CHANGELOG.md

@@ -6,6 +6,28 @@ release commits and the issues they reference.
 
 Dates are the npm publish date. Each entry names the RTSC issue behind it.
 
+## 1.16.0 (2026-08-02)
+
+- **RTSC-526** — `retasc import` catches up with the Dash on four things.
+
+  **It warns before a second import.** Re-importing does not duplicate anything, but it
+  does re-sync: status, labels, title and body are replaced with whatever the source says
+  now. Import from Jira, spend two weeks moving issues along in Retasc, re-import to pick up
+  new tickets, and those two weeks of changes snap back. You now get told, with the date of
+  the last import, before the confirmation.
+
+  **The run shows progress**, as a bar that fills while it works, rather than a silent wait
+  that looks like it has hung. The run is server-side, so pressing Ctrl-C out of boredom
+  never stopped it anyway.
+
+  **The column list is grouped** under your own tool's sections (Not started, Active, Done,
+  Closed) instead of arriving flat. On a twenty-column board that is the difference between
+  scannable and a wall.
+
+  **Columns that were not mapped are named.** If a column appears between the moment you set
+  the mapping and the moment the import runs, its issues land in `todo`. They used to show
+  as a number; now they are listed, with what to do about it.
+
 ## 1.15.0 (2026-08-02)
 
 - **RTSC-524** — new command: `retasc import`. Bring a Linear, Jira, Asana, ClickUp or

package/dist/api.js

@@ -35,6 +35,11 @@ const fns = {
     listImportStatuses: makeFunctionReference("import:listImportStatuses"),
     listReviewCandidates: makeFunctionReference("import:listReviewCandidates"),
     runImport: makeFunctionReference("import:runImport"),
+    // RTSC-526: `latestImport` is LIVE progress and is swept after 24h; `importHistory` is
+    // permanent and per source, so it is the only thing that can answer "has this org
+    // imported from X before?" once the progress row is gone.
+    latestImport: makeFunctionReference("import:latestImport"),
+    importHistory: makeFunctionReference("import:importHistory"),
     claimableGhosts: makeFunctionReference("ghosts:claimableGhosts"),
     claimGhost: makeFunctionReference("ghosts:claimGhost"),
     dismissGhostPrompt: makeFunctionReference("ghosts:dismissGhostPrompt"),
@@ -171,6 +176,8 @@ export const api = {
     listImportStatuses: (args) => withAuth(() => client().action(fns.listImportStatuses, args)),
     listReviewCandidates: (args) => withAuth(() => client().query(fns.listReviewCandidates, args)),
     runImport: (args) => withAuth(() => client().action(fns.runImport, args)),
+    latestImport: (args) => withAuth(() => client().query(fns.latestImport, args)),
+    importHistory: (args) => withAuth(() => client().query(fns.importHistory, args)),
     claimableGhosts: (args) => withAuth(() => client().query(fns.claimableGhosts, args)),
     claimGhost: (args) => withAuth(() => client().mutation(fns.claimGhost, args)),
     dismissGhostPrompt: (args) => withAuth(() => client().mutation(fns.dismissGhostPrompt, args)),

package/dist/commands/import.js

@@ -6,6 +6,91 @@ import { ask, confirm, isInteractive } from "../lib/prompt.js";
 import { pickExisting } from "./bind.js";
 /** The five destinations a column can be mapped to. Mirrors `MappedStatus`. */
 const MAPPED = ["todo", "doing", "review", "done", "canceled"];
+/**
+ * The source's own section names, so the list reads as the shape the human already knows
+ * from their tool. Mirrors `GROUP_LABEL` in `dash/src/lib/statusMapping.ts` (RTSC-436).
+ */
+const GROUP_LABEL = {
+    not_started: "Not started",
+    active: "Active",
+    done: "Done",
+    closed: "Closed",
+};
+/** Section order, matching the Dash. */
+const GROUP_ORDER = ["not_started", "active", "done", "closed"];
+/**
+ * What to say before a SECOND import into the same org (RTSC-526).
+ *
+ * Not a formality. `convex/importWrite.ts` upserts by `sourceIssueId` and patches the match,
+ * so a re-import does not duplicate — the identifier and number survive even a rename — but
+ * it DOES replace status, labels, title and body with whatever the source says now. Two
+ * weeks of moving issues along in Retasc snap back to the source's version.
+ *
+ * Read from `importHistory`, NOT `latestImport`. The latter is live progress and is swept
+ * after 24h, so gating on it means the warning stops firing for exactly the person most at
+ * risk: the one who imported last week and has been working in Retasc since.
+ *
+ * Null when this source has never been imported, so a first run says nothing.
+ */
+export function reimportWarning(history, source, label) {
+    const prior = history.find((h) => h.source === source);
+    if (!prior)
+        return null;
+    const when = prior.lastImportedAt
+        ? ` (last on ${new Date(prior.lastImportedAt).toISOString().slice(0, 10)})`
+        : "";
+    return (`\n! You've imported from ${clean(label)} into this org before${when}.\n` +
+        `  Re-importing re-syncs those issues, so any edits you made in Retasc to them\n` +
+        `  (status, labels, and so on) will be replaced by ${clean(label)}'s version.`);
+}
+/**
+ * The summary after a run, with the one field that needs words rather than a number.
+ *
+ * `unmappedStatuses` holds columns that appeared BETWEEN the mapping being set and the run;
+ * their issues landed in `todo`. As a count it is a silent slice of work in the wrong place,
+ * which is the whole reason the Dash names them.
+ */
+export function summaryLines(summary, label) {
+    const out = [];
+    const unmapped = [];
+    for (const [k, v] of Object.entries(summary ?? {})) {
+        if (k === "unmappedStatuses") {
+            if (Array.isArray(v))
+                unmapped.push(...v.map(String));
+            continue;
+        }
+        if (typeof v === "number" || typeof v === "string")
+            out.push(`  ${k.padEnd(20)}${clean(v)}`);
+    }
+    if (unmapped.length) {
+        out.push("", `! These ${clean(label)} statuses weren't mapped, so their issues landed in todo:`, `    ${unmapped.map((u) => clean(u)).join(", ")}`, "  They appeared after you set the mapping. Re-import to place them.");
+    }
+    return out;
+}
+// --- the progress bar --------------------------------------------------------
+/** Lime, in 256-colour. Bright enough to read on both a light and a dark terminal. */
+const LIME = "\x1b[38;5;154m";
+const DIM = "\x1b[38;5;240m";
+const RESET = "\x1b[0m";
+/**
+ * One line of progress bar.
+ *
+ * Pure, so the shape can be tested without a terminal. Colour is opt-out via `color`, which
+ * the caller ties to a TTY and to `NO_COLOR` — a bar full of escape sequences in a piped log
+ * is worse than no bar.
+ */
+export function progressBar(done, total, width = 24, color = true) {
+    const known = typeof total === "number" && total > 0;
+    // Clamp: a server that reports more done than total must not print a bar wider than the
+    // terminal, or a negative one.
+    const frac = known ? Math.max(0, Math.min(1, done / total)) : 0;
+    const filled = Math.round(frac * width);
+    const bar = known
+        ? `${color ? LIME : ""}${"█".repeat(filled)}${color ? DIM : ""}${"░".repeat(width - filled)}${color ? RESET : ""}`
+        : `${color ? DIM : ""}${"░".repeat(width)}${color ? RESET : ""}`;
+    const count = known ? `${Math.round(frac * 100)}%  ${done}/${total}` : `${done} so far`;
+    return `  ${bar}  ${count}`;
+}
 /**
  * May this column be mapped to `review`?
  *
@@ -83,8 +168,16 @@ export async function mapStatuses(statuses, reviewers, askFn) {
     const reviewerByStatus = {};
     console.log(`\nWhat does each column mean? ${statuses.length} to confirm.\n` +
         "  Enter keeps the suggestion. It comes from the column's type in your tool, not its name.");
-    // The source's own order, so the list reads the way it does in the tool they know.
-    for (const s of [...statuses].sort((a, b) => a.order - b.order)) {
+    // Grouped under the source's own section names, in the source's own order within each
+    // (RTSC-436/526). On a twenty-column Jira board a flat list is a wall; the sections are
+    // the shape the human already has in front of them in their tool.
+    const ordered = GROUP_ORDER.flatMap((g) => {
+        const rows = statuses.filter((s) => s.group === g).sort((a, b) => a.order - b.order);
+        return rows.map((s, i) => ({ s, heading: i === 0 ? GROUP_LABEL[g] : null }));
+    });
+    for (const { s, heading } of ordered) {
+        if (heading)
+            console.log(`\n  ${heading}`);
         const allowed = MAPPED.filter((m) => m !== "review" || (reviewAllowed(s.group) && reviewers.length > 0));
         const suggested = allowed.includes(s.suggested)
             ? s.suggested
@@ -119,6 +212,43 @@ export async function mapStatuses(statuses, reviewers, askFn) {
     }
     return { statusMap, reviewerByStatus };
 }
+/**
+ * Poll `latestImport` and redraw one line until told to stop. Returns the stopper.
+ *
+ * One LINE, rewritten in place, rather than a scrolling log: the interesting number is the
+ * current one. Silent without a TTY — a progress bar in a piped log is noise, and the
+ * escape codes would end up in whatever reads it.
+ *
+ * Every failure here is swallowed. This is decoration on top of a run that is happening
+ * server-side regardless; a hiccup in the progress query must never be what surfaces as an
+ * import failure.
+ */
+function followProgress(orgId) {
+    const tty = Boolean(stdout.isTTY) && !process.env.NO_COLOR;
+    if (!stdout.isTTY)
+        return () => { };
+    let stopped = false;
+    const tick = async () => {
+        while (!stopped) {
+            try {
+                const p = (await api.latestImport({ orgId }));
+                if (!stopped && p && p.status === "running") {
+                    stdout.write(`\r\x1b[2K${progressBar(p.issuesDone ?? 0, p.issuesTotal ?? null, 24, tty)}`);
+                }
+            }
+            catch {
+                /* progress is decoration; never let it speak for the run */
+            }
+            await new Promise((r) => setTimeout(r, 1200));
+        }
+    };
+    void tick();
+    return () => {
+        stopped = true;
+        // Clear the line so the summary does not land on top of a half-drawn bar.
+        stdout.write("\r\x1b[2K");
+    };
+}
 export async function importAction(opts) {
     if (!isInteractive() && !opts.yes) {
         cliError("NEEDS_TERMINAL", "Importing asks what each of your columns means, so it needs a terminal.", "Run it interactively, or use the Dash.");
@@ -182,12 +312,24 @@ export async function importAction(opts) {
     // undoing a mistake means an org-level cleanup.
     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
+    // gets re-run casually. Read from `importHistory` (permanent) rather than `latestImport`
+    // (live progress, swept after 24h), so this still fires for someone who imported last
+    // week and has been working in Retasc since — the person with the most to lose.
+    const history = (await api.importHistory({ orgId: orgId }));
+    const warning = reimportWarning(history, src.source, src.label);
+    if (warning)
+        console.log(warning);
     if (!opts.yes && !(await confirm("This can't be undone. Go ahead?"))) {
         console.log("Nothing imported.");
         return;
     }
     // --- run -------------------------------------------------------------------
-    console.log("\nImporting. This can take a few minutes on a big project…");
+    console.log("\nImporting…\n");
+    // RTSC-526 — show it moving. The run is server-side and can take minutes on a big
+    // project; a silent wait is exactly when someone decides it has hung and presses Ctrl-C,
+    // which is the worst moment to do it because the server keeps going regardless.
+    const stop = followProgress(orgId);
     let res;
     try {
         res = (await api.runImport({
@@ -200,6 +342,7 @@ export async function importAction(opts) {
         }));
     }
     catch (e) {
+        stop();
         // The run is server-side, so a dead connection here does NOT mean a dead import.
         // Saying "failed" would be a guess, and the wrong one sends someone re-importing on
         // top of a run that is still writing.
@@ -211,10 +354,10 @@ export async function importAction(opts) {
         console.error("  Check the Dash before running it again.");
         throw e;
     }
+    stop();
     console.log("\n✓ Imported.");
-    for (const [k, v] of Object.entries(res.summary ?? {})) {
-        if (typeof v === "number" || typeof v === "string")
-            console.log(`  ${k.padEnd(18)}${clean(v)}`);
+    for (const line of summaryLines(res.summary, src.label)) {
+        console.log(line);
     }
     // The import just minted a placeholder for whoever authored that work, and the person
     // who ran it is very often one of them. `identityLoop` is the same prompt `join` uses and

package/package.json

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