@retasc/cli 1.20.0 → 1.21.0

package/CHANGELOG.md

@@ -6,6 +6,15 @@ release commits and the issues they reference.
 
 Dates are the npm publish date. Each entry names the RTSC issue behind it.
 
+## 1.21.0 (2026-08-07)
+
+- **RTSC-527** — the re-import warning dates the last import in **your** timezone. The day
+  was formatted from `toISOString()`, which rolls back one east of Greenwich: at UTC+7 an
+  import made five hours ago read as yesterday's, which is the opposite of useful for a line
+  whose job is to say how long ago it was. The Dash gained the same date in the same shape
+  in this release, and moved onto the same durable per-source history the CLI already read,
+  so the two surfaces now describe one import the same way.
+
 ## 1.20.0 (2026-08-04)
 
 - **RTSC-561** — the org gained an **admin** role, and the CLI stopped refusing it.
@@ -536,7 +545,7 @@ there is no TTY to run one in.
 
 - **RTSC-263** — owner/member permission denials now print a readable reason and the
   next step instead of an opaque `Server Error`. Hitting an owner-only command as a
-  member reports "Owner role required." with "Ask <owner> to create a project." on its
+  member reports "Owner role required." with "Ask `<owner>` to create a project." on its
   own line. The backend change does the work; the CLI already read the structured
   payload (1.5.0), so this release carries only the hardening below.
 - **RTSC-263** — `formatError` now strips U+0085, U+2028 and U+2029 in addition to the

package/README.md

@@ -1,6 +1,6 @@
 # retasc
 
-**The issue tracker AI agents pull work from.**
+**The issue tracker that hands your backlog to AI agents.**
 
 Over [MCP](https://modelcontextprotocol.io), a heterogeneous fleet of agents atomically
 claims unblocked, prioritized tasks and runs in parallel — server-enforced, no collisions.

package/dist/commands/import.js

@@ -18,6 +18,11 @@ const GROUP_LABEL = {
 };
 /** Section order, matching the Dash. */
 const GROUP_ORDER = ["not_started", "active", "done", "closed"];
+/** `YYYY-MM-DD` in the local zone. Mirrored in `dash/src/lib/importGating.ts`. */
+function localDay(d) {
+    const pad = (n) => String(n).padStart(2, "0");
+    return `${d.getFullYear()}-${pad(d.getMonth() + 1)}-${pad(d.getDate())}`;
+}
 /**
  * What to say before a SECOND import into the same org (RTSC-526).
  *
@@ -36,9 +41,11 @@ 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)})`
-        : "";
+    // The reader's day, not UTC (RTSC-527). `toISOString().slice(0, 10)` was the original
+    // and it misdates by one: at UTC+7 an import made before 07:00 local prints as
+    // yesterday, which is the opposite of useful for a line whose whole job is "how long
+    // ago". The Dash's `importDay` formats identically, so one import still gets one date.
+    const when = prior.lastImportedAt ? ` (last on ${localDay(new Date(prior.lastImportedAt))})` : "";
     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.`);

package/package.json

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