@datarails-ai/dr-cli 1.6.120 → 1.6.121

package/dist/cli.js

@@ -8,7 +8,7 @@ import { fileURLToPath as fileURLToPath3 } from "url";
 // package.json
 var package_default = {
   name: "@datarails-ai/dr-cli",
-  version: "1.6.120",
+  version: "1.6.121",
   description: "Datarails CLI",
   type: "module",
   engines: {
@@ -69,7 +69,7 @@ var package_default = {
 };
 
 // src/buildInfo.ts
-var BUILD_TIME = "2026-10-12T10:19:56.130Z";
+var BUILD_TIME = "2026-10-12T10:41:54.439Z";
 function formatBuildTime(iso) {
   if (iso === "") return "";
   const d = new Date(iso);
@@ -37590,6 +37590,34 @@ function requireTagPermission(details, perm, docId, action) {
     );
   }
 }
+var TagWriteRefusedError = class extends Error {
+  constructor(message, reason) {
+    super(message);
+    this.reason = reason;
+    this.name = "TagWriteRefusedError";
+  }
+  reason;
+};
+function fullTagSetWith(stored, write) {
+  const kept = [];
+  for (const raw of stored ?? []) {
+    if (typeof raw !== "object" || raw === null) {
+      continue;
+    }
+    const t = raw;
+    const id = typeof t.id === "string" && t.id.trim() !== "" ? Number(t.id) : t.id;
+    if (typeof id !== "number" || !Number.isInteger(id) || id === write.id || kept.some((k) => k.id === id) || t.value === void 0 || t.value === null) {
+      continue;
+    }
+    kept.push({
+      id,
+      value: t.value,
+      ...typeof t.name === "string" ? { name: t.name } : {},
+      ...typeof t.label === "string" ? { label: t.label } : {}
+    });
+  }
+  return [...kept, write].sort((a, b) => a.id - b.id);
+}
 async function runFileboxSetVersionFileStatus(cfg) {
   if (cfg.docId <= 0) {
     throw new Error("document id must be positive");
@@ -37644,6 +37672,8 @@ async function runFileboxSetVersionFileStatus(cfg) {
         changed: false,
         verified: true,
         reapplied: false,
+        date_tag_value: target.date_tag_value ?? null,
+        date_tag_value_preserved: true,
         demoted_version_ids: [],
         rescan_queued: false
       });
@@ -37675,19 +37705,31 @@ async function runFileboxSetVersionFileStatus(cfg) {
       );
     }
   }
-  const tagsToUpdate = JSON.stringify([
-    { id: tag.id, value: cfg.status, name: tag.name, label: cfg.status }
-  ]);
+  const statusWrite = {
+    id: tag.id,
+    value: cfg.status,
+    name: tag.name,
+    label: cfg.status
+  };
+  let base = target.tags ?? [];
+  const refreshBase = (v) => {
+    if (v !== null && v.tags.length > 0) {
+      base = v.tags;
+    }
+  };
   const write = async () => {
     const res = await setVersionTagsAndLabel(
       cfg.client,
       cfg.versionId,
-      { tags_to_update: tagsToUpdate },
+      { tags_to_update: JSON.stringify(fullTagSetWith(base, statusWrite)) },
       { signal: cfg.signal }
     );
     if (res.status < 200 || res.status >= 300) {
       const body = await res.text();
-      throw new Error(`set version file status refused (HTTP ${res.status}): ${body.trim()}`);
+      throw new TagWriteRefusedError(
+        `set version file status refused (HTTP ${res.status}): ${body.trim()}`,
+        `(HTTP ${res.status}): ${body.trim()}`
+      );
     }
   };
   const readBack = async () => {
@@ -37699,6 +37741,7 @@ async function runFileboxSetVersionFileStatus(cfg) {
   let seen = await readBack();
   if (seen !== null && tagValueOf(seen.tags, tag.id) !== cfg.status) {
     reapplied = true;
+    refreshBase(seen);
     await write();
     seen = await readBack();
     const now = seen === null ? void 0 : tagValueOf(seen.tags, tag.id);
@@ -37708,6 +37751,53 @@ async function runFileboxSetVersionFileStatus(cfg) {
       );
     }
   }
+  const dateBefore = target.date_tag_value;
+  const dateMoved = (v) => v !== null && typeof dateBefore === "number" && v.row.date_tag_value !== void 0 && v.row.date_tag_value !== dateBefore;
+  let dateUnknown = false;
+  if (dateMoved(seen)) {
+    err.write(
+      `warning: date_tag_value on version ${cfg.versionId} changed (${JSON.stringify(dateBefore)} -> ${JSON.stringify(seen.row.date_tag_value ?? null)}) when its File Status was set; re-applying the full tag set once
+`
+    );
+    reapplied = true;
+    refreshBase(seen);
+    let refused = false;
+    try {
+      await write();
+    } catch (e) {
+      if (cfg.signal.aborted) {
+        throw e;
+      }
+      if (e instanceof TagWriteRefusedError) {
+        refused = true;
+        err.write(`warning: re-applying the full tag set was refused ${e.reason}
+`);
+      } else {
+        err.write(
+          `warning: re-applying the full tag set failed (${e instanceof Error ? e.message : String(e)}); its outcome is unknown, reading the version again
+`
+        );
+      }
+    }
+    const after = refused ? seen : await readBack();
+    if (after === null) {
+      dateUnknown = true;
+      err.write(
+        `warning: could not read version ${cfg.versionId} back to confirm its date_tag_value after re-applying the full tag set \u2014 check it with \`dr filebox versions ${cfg.docId} --json\`
+`
+      );
+    } else {
+      seen = after;
+    }
+  }
+  const dateAfter = dateUnknown || seen === null || seen.row.date_tag_value === void 0 ? null : seen.row.date_tag_value;
+  const datePreserved = dateUnknown || seen === null || dateBefore === void 0 || seen.row.date_tag_value === void 0 ? null : !dateMoved(seen);
+  if (datePreserved === false) {
+    err.write(
+      `warning: date_tag_value on version ${cfg.versionId} is still ${JSON.stringify(dateAfter)} (was ${JSON.stringify(dateBefore)}) after one re-apply; its tags still carry the date. Restore it with \`dr filebox set-version-date-tag ${cfg.versionId} --doc ${cfg.docId} --<dimension> <date>\` (it sends the date tag alone; on a planning filebox use \`dr filebox set-version-cycle ${cfg.versionId} --doc ${cfg.docId} --date <date> --scenario <name>\` instead, which keeps the cycle), then check \`dr filebox versions ${cfg.docId} --json\`
+`
+    );
+  }
   if (seen === null) {
     err.write(
       `warning: could not read version ${cfg.versionId} back to verify its File Status \u2014 confirm with \`dr filebox versions ${cfg.docId}\`
@@ -37733,6 +37823,8 @@ async function runFileboxSetVersionFileStatus(cfg) {
       changed: true,
       verified,
       reapplied,
+      date_tag_value: dateAfter,
+      date_tag_value_preserved: datePreserved,
       demoted_version_ids: demotedIds,
       rescan_queued: true
     });
@@ -37743,6 +37835,12 @@ async function runFileboxSetVersionFileStatus(cfg) {
     `Set File Status on version ${cfg.versionId}: ${JSON.stringify(previous ?? "(unset)")} -> "${cfg.status}" (${verdict}).
 `
   );
+  if (datePreserved === false) {
+    cfg.out.write(
+      `date_tag_value NOT preserved: it reads ${JSON.stringify(dateAfter)}, was ${JSON.stringify(dateBefore)} (see the warning above).
+`
+    );
+  }
   if (demotedIds.length > 0) {
     cfg.out.write(
       `Only one version per period can be ${cfg.status}: ${plural2(demotedIds.length, "version", "versions")} ${demotedIds.join(", ")} ${plural2(demotedIds.length, "was", "were")} moved to Draft by the server.

package/dist/scopes-map.json

@@ -1,6 +1,6 @@
 {
   "version": 1,
-  "cliVersion": "1.6.120",
+  "cliVersion": "1.6.121",
   "_contract": "Resolve a command path through `aliases` (canonical prefix + alias segment -> canonical path) before any lookup. A path listed in `pendingCommands`, or whose first segment is a key of `pending`, is UNDECIDED, not unrestricted: fail closed or skip it, and never read a path's absence from `commands` as 'no requirement'. An entry carrying `denied` is UNAVAILABLE to any AGENT-SCOPED credential — one whose `scopes` claim carries at least one `resource:action` entry; a claim that is absent, empty, capability-only or wholly unparseable is UNRESTRICTED, and this mark does not apply to it — whatever else that entry says: it is not a ceiling and it is not always-available, its `denied.reason` says why and `denied.until` names the ticket that lifts it, and the absence of `requires` on it must NEVER be read as 'no requirement'. Only an entry in `commands` with an empty `requires` means always-available.",
   "commands": {
     "login": {

package/dist/skills/dr-cli/reference/filebox-documents.md

@@ -154,7 +154,11 @@ set-version-include` (below).
 
 - `filebox set-version-date-tag <vid> --doc <id> --month|--quarter|--day|--year|--week …
   [--json]` — set the date tag on one version (resolves the tag id from the doc's
-  config; other tags untouched).
+  config; other tags untouched in `tags`). It sends the date tag alone, and the
+  server rebuilds the version's dimension value from the submitted tags, so on
+  a filebox with a second dimension tag (a cycle or plan LIST tag) that tag
+  drops out of the dimension. On a planning filebox use `set-version-cycle`,
+  which sends the date and the cycle together.
 - `filebox set-version-label <vid> --label "<text>" | --clear [--json]` — set or
   remove a version's free-text label; name, date and dimension tags are
   untouched, and a locked date tag does not block it. No confirm step. Address it
@@ -176,6 +180,27 @@ set-version-include` (below).
   moves that version to Draft (the output names it). The status is read back and
   re-applied once if it did not stick. The write queues a rescan of the version,
   so mapped tables show the new `File Status` only after it finishes.
+  Like the UI, it sends the version's **full tag set** with File Status
+  replaced, not File Status alone. The server merges the submitted tags into
+  `tags` but rebuilds the version's dimension value, and with it the
+  `date_tag_value` that `filebox versions --json` shows, from the submitted tags
+  only. A File Status-only body (CLI releases before DR-54157) therefore left
+  `date_tag_value` null while `tags` still held the month. That is not harmless:
+  the server uses the dimension value to pick the latest version per period, to
+  apply date locks and in rescan events. The command reads `date_tag_value` back,
+  re-applies the full set once if it changed, and otherwise reports it: a stderr
+  warning, a `date_tag_value NOT preserved` line, and
+  `date_tag_value_preserved: false` in `--json`. `--json` also returns
+  `date_tag_value`, and `date_tag_value_preserved: null` when the server does
+  not serve it. **To repair a version left with a null date**, run
+  `set-version-date-tag` with the period its `tags` hold. That writes the date
+  tag, and the server rebuilds the dimension from it. It sends the date tag
+  alone, so use it only when the date is the filebox's only dimension tag. On a
+  planning filebox, run `set-version-cycle` with the version's existing date
+  and scenario instead, which sends both. Re-running
+  `set-version-file-status` with the same status does not repair it, because
+  it writes nothing. A real status change does restore it, because it re-sends
+  the date tag.
 - `filebox set-version-cycle <vid> --doc <id> --date <date> --scenario <name>
   [--date-tag-name <n>] [--json]` — **forecast/budget (planning) fileboxes only.**
   Sets the cycle date tag and the scenario LIST-tag together (both flags

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@datarails-ai/dr-cli",
-  "version": "1.6.120",
+  "version": "1.6.121",
   "description": "Datarails CLI",
   "type": "module",
   "engines": {